OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: [xml-dev] genx - consensus items

[ Lists Home | Date Index | Thread Index ]


----- Original Message ----- 
From: "David Tolpin" <dvd@davidashen.net>
To: <xml-dev@lists.xml.org>
Sent: Friday, January 23, 2004 1:35 AM
Subject: Re: [xml-dev] genx - consensus items


> 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

Simpler than

startTag
  attribute
  text
endTag

?

Generally one should make an API as small as possible for a given set of features,
otherwise logical redundancy can creep in, with the need for additional state checking 
and preventing inconsistent/contradictory calls.

Karl




 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS