Forgive me if I have posted this in the wrong place I see federation working in terms of data, however I can think of one key idea disrupting the true potential of federation. That is differences in client interfaces.
This is because conceivably one particular solution say an enterprise solution, might want to represent things differently for a particular application. There is no reason why a wave has to be represented like wavelets and blips are now (conversation like). Obviously things like flat style waves are fairly trivial, but this is not necessarily sharing the wave as intended. I think it is natural that a conversation is attached to what you are doing. However if what you are doing is working on a specific thing, rather than just being a dialogue, I would want the specific thing and its interface to the focus of the wave and not the conversation (I still support the idea of having gadgets in blips). This is because if we want to work on a document we want to work on a document. I don’t want it remotely bridged it a haphazard way through robots, similarly I doesn’t make much sense to have it imbedded in a blip. So personally I would say lead by example. Instead of a fixed interface have the client environment with a default interface that gracefully erodes, and you get to choose your interface for a wave which would be a bit like a gadget. You would have access to the wave conversation Example would be working on google docs through wave, say on a spreadsheet. It is also a solution to the embed API. You wouldn’t need to duplicate data with robots, simply have an agent that acts a bridge, and style appropriately. The API would allow you to choose your interface, and which aspects of the environment you want exposed. Security concerns are the same as they are now, it comes down to education at the end of the day. -- 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.
