XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: [xml-dev] Six Reasons Not to use XML Attributes

> -----Original Message-----
> From: David Lee [mailto:dlee@calldei.com]
> Sent: Friday, March 02, 2012 3:30 PM
> To: Andrew Welch; Costello, Roger L.
> Cc: xml-dev@lists.xml.org
> Subject: RE: [xml-dev] Six Reasons Not to use XML Attributes
> 
> While I agree it makes it bulkier, I disagree with the argument
> specifics.
> That is "looking ahead" is only a side effect of a particular parser
> implementation.
> 
> i.e.
> if a parser reads
> 
> 
> <thing
> 
> 
> It has to look ahead in both cases
> A)   id="abc"
> B)  ><id>abc<
> 
> 
> It just happens that most XML parsers do this lookahead thing for you
> for attributes (and some do it for elements) ... but its not intrinsic
> in XML.

The difference that I see is that attributes are not structured and therefore the "look-ahead" is reasonably bounded - whereas in the case of elements, they can contain arbitrarily deep and nested structures (with additional nested "look-aheads").

Vojtech


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


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

Copyright 1993-2007 XML.org. This site is hosted by OASIS