> > I'm working on a document now that explains more (but not all) ofhow > wavelets and documents relate to each other to build up > a conversation view. Well announce it here when the document goes up. >
Great to hear. While you are at it, can you please elaborate on when to use tags and when to use annotations? The examples for annotations in http://www.waveprotocol.org/whitepapers/operational-transform do replicate HTML tag functionality, which is confusing at best. Same for elements. Why should I add an image element, when there is an HTML tag for that? Also, there must be a registry (read a public URI) of annotation names and there expected behavior, so that other implementation can behave the same way. Is this a fixed list? Or will people be allowed to add their own? How will you avoid name clashes? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
