I would assume you are correct on the notation being a shortcut for
elementStart("line"); elementEnd(); in the same way a <br/> tag in XHTML is
used. When processed by a standard XML parser like Xerces, "<line></line>"
and "<line/>" are considered identical, and will produce the same DOM
Element model.Mark Adamcin (480) 201-4448 [email protected] On Thu, Oct 1, 2009 at 11:05 AM, Tad Glines <[email protected]> wrote: > > First let me say that it has been a long time since I was this excited > about a new technology. I ran across the Google IO 2006 presentation > on wave by accident, and was instantly hooked on the idea. I find > myself thinking about how e-mail conversations would be so much easier > in wave, and I don't even have a wave account yet :-) > > So, kodos to Google for thinking way outside the box on this one. I > really hope that wave becomes the new defacto communication model. It > has such huge potential. > > Now, I do have a question about the conversation model. In your link > is shows lines represented as "<line/>This is a line". But this cannot > be represented in wave. the only choices are "<line><line/>This is a > line." or "<line>This is a line.<line/>". Is "<line/>" intended to be > a shortcut for saying "elementStart("line"); elementEnd();"? > > -Tad > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
