[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: genx - consensus items

• To: David Tolpin <dvd@d...>
• Subject: Re: genx - consensus items
• From: Bob Foster <bob@o...>
• Date: Fri, 23 Jan 2004 03:12:54 -0600
• Cc: xml-dev@l...
• In-reply-to: <200401230635.i0N6ZOHM025816@a...>
• References: <200401230635.i0N6ZOHM025816@a...>
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007

David Tolpin wrote:
 > David Tolpin:
 >
 >>Rich Salz:
 >>
 >>>>I'm inclined to agree.  A teeny bit more complexity in the
 >>>>implementation but probably worth it.  Anyone want to push back? -Tim
 >>>
 >>>asymnmetry is bad.  open-close, begin-end, etc.
 >>
 >>The idea was to improve asymmetry, not to defeat it, I think.
 >>
 >>startTag
 >>  attribute*
 >>  text
 >>endTag
 >>
 >>But in this case startTag is not start 'Tag', it is 
startElement/endElement.
 >>
 >>Not that I like this approach, just explaining. Simple logic is 
better than
 >>complex.
 >
 >
 > That is, startElement/endElement are good for building a tree, but 
inadequate
 > for serializing,
 >
 > startTagOpen
 >   attribute
 > startTagClose
 >
 >   Text
 >
 > endTag
 >
 > are simpler and more natural for serialization tasks. I'd keep the 
startTagClose

Conversely, James Clark has written several serializers, e.g., XmlWriter 
in trang, in which the convention is:

startElement*
   attribute*

   (text | startElement)*

endElement

No explicit end-start-tag is used or needed. The writer can tell when a 
start tag needs to end; in fact, the convention helps to produce empty 
element tags without backtracking. Use is simple and natural.

Bob Foster
http://xmlbuddy.com/

• Follow-Ups:
  • Re: genx - consensus items
    • From: David Tolpin <dvd@d...>
  • Re: genx - consensus items
    • From: David Tolpin <dvd@d...>

• References:
  • Re: genx - consensus items
    • From: David Tolpin <dvd@d...>

• Prev by Date: Re: genx - consensus items
• Next by Date: Re: genx - consensus items
• Previous by thread: Re: genx - consensus items
• Next by thread: Re: genx - consensus items
• Index(es):
  • Date
  • Thread