I understand your point. It's just that XML allows this shorthand syntax in it's unparsed form. XML parsers (SAX-based parsers, that is) will still read a self-closing tag as at least two events, the elementStart and elementEnd.
By the way, if there's anyone on this list who still has an extra invite for the sandbox, I'd really appreciate it. I can't count the number of Twitter accounts I'm re-tweeting and following just to get one :) I'm desperate to start building with this technology. Mark Adamcin (480) 201-4448 [email protected] On Thu, Oct 1, 2009 at 12:57 PM, Tad Glines <[email protected]> wrote: > > On Thu, Oct 1, 2009 at 12:07 PM, Mark Adamcin <[email protected]> wrote: > > 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. > > My point is that there is no way to represent "<line/>" directly in > wave. Only "<line></line>" can be represented. Each > "elementStart("line")" MUST be matched with an "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 -~----------~----~----~----~------~----~------~--~---
