Protocol requirements

Revision as of 22:14, 10 April 2004 by 142.177.74.77 (talk)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

See also performance requirements, software requirements and hardware requirements.

Protocol requirements for the healthy buying infrastructure seem to include at least:

DECT seems like the ideal way to provide both of these sets of services

Beyond that, the following are optional:

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 or DECT 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.