Protocol requirements: Difference between revisions
(adding performance requirements) |
(people talking with each other is also a powerful medium/protocol ;) .) |
||
| Line 10: | Line 10: | ||
::[[Consumerium Service access]] should include access to other users, especially if [[brand management]] types can pay to promote [[green light]] products to users, making it all [[self-funding]]. | ::[[Consumerium Service access]] should include access to other users, especially if [[brand management]] types can pay to promote [[green light]] products to users, making it all [[self-funding]]. | ||
:::Ideally since we have drifted from syntactically strict data format into [[wiki code]] that is easier for human cognition we should try to offer the '''avantgarde consumerist''' information and then rely on people getting into discussions over/on the information thus the [[healthy signal infrastructure]] is extended by word-of-mouth. | |||
[[Hardware requirements]] and [[hardware standard]]s constrain the protocols: [[Bluetooth]] for instance is assumed to be required to get both secure communication and [[modular hardware]]. But if [[in-store radio]] and [[audio]] presentation becomes a more effective way to deliver the [[Consumerium buying signal]], and [[privacy risk]] is not a concern, i.e. most of what is delivered is [[green light ad]]s, then: | [[Hardware requirements]] and [[hardware standard]]s constrain the protocols: [[Bluetooth]] for instance is assumed to be required to get both secure communication and [[modular hardware]]. But if [[in-store radio]] and [[audio]] presentation becomes a more effective way to deliver the [[Consumerium buying signal]], and [[privacy risk]] is not a concern, i.e. most of what is delivered is [[green light ad]]s, then: | ||
Revision as of 12:36, 10 March 2004
See also performance requirements, software requirements and hardware requirements.
Protocol requirements for the healthy buying infrastructure seem to include at least:
- HTTP and REST to the web browser, as typical access to Development Wiki and Research Wiki.
- Each high-capability terminal device presenting a Consumerium buying signal probably has an IP number issued from a block someone controls. Every retail shelf might ultimately have one too, if friendly retail becomes the norm.
- Ideally, some integration with ICQ or another chat net that can support SecureIM - see interwiki identity standard for more on this, which suggests jabber.org protocol may play a role in authentication. Possibly SMS also for communication between mobile devices.
- Consumerium Service access should include access to other users, especially if brand management types can pay to promote green light products to users, making it all self-funding.
- Ideally since we have drifted from syntactically strict data format into wiki code that is easier for human cognition we should try to offer the avantgarde consumerist information and then rely on people getting into discussions over/on the information thus the healthy signal infrastructure is extended by word-of-mouth.
Hardware requirements and hardware standards constrain the protocols: Bluetooth for instance is assumed to be required to get both secure communication and modular hardware. But if in-store radio and audio presentation becomes a more effective way to deliver the Consumerium buying signal, and privacy risk is not a concern, i.e. most of what is delivered is green light ads, then:
- In-the-clear FM radio may well be the most important protocol, with analog cell perhaps augmenting it.
- Entirely different protocols such as walkie-talkie or cordless protocol applications that call the customer back with an audio presentation on the product they just barcode scanned, may also be more useful to support than anything based on an IP number, if more phones end up with these capabilities.