Hi Dave, you're right. (Sam was right too). The federation protocol specifies the structure and transform of operations but doesn't specify their meaning. In order to interact with a complex structured conversation model the documents making up a wave need semantics. The Fedone client/server use a very simple model and consequently support only very simple interactions. The federation protocols allow you to build whatever semantics you want on the basic documents. Two dumb *servers* will be able to interop just fine so long as they don't attach meaning to the documents. But you're correct, two wave *systems* won't play very well if they don't share a common interpretation of the wave documents.
The Google Wave service running in the sandbox has a more complex semantic model than Fedone (but still built on the fundamental documents and operations you already know about). Our models are still experiencing rapid change but we intend to publish the information you need to interpret them as soon as they settle down somewhat. For example, the structures that qMax uncovered (everyone was right!) will be obsolete real soon now: we've found better ways. HTH, Alex --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
