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

Re: attribute order (RE: Syntax Sugar and XML information models)

• From: "Simon St.Laurent" <simonstl@s...>
• To: Justin Couch <justin@v...>, xml-dev@l...
• Date: Fri, 30 Mar 2001 09:04:54 -0500

At 12:01 AM 3/31/01 +1000, Justin Couch wrote:
>"Simon St.Laurent" wrote:
> >
> > Is there some kind of processing advantage for _parsers_ (not applications)
> > to report attribute values in any sequence other than their original 
> sequence?
>
>If we take the SAX like approach with some minor mods: The callback says
>"here is an element and here are a bunch of attributes". It is possible
>that the attribute collection gets returned as a HashMap of name/value
>pairs (SAX returns effectively an array). If you ask for a list of the
>keys in the hashmap it is pretty likely that the list order will not
>correspond to the declaration order.

It is possible, but is it optimal?  I suspect the HashMap takes more 
overhead than the array, though I could be wrong about that.

I don't see an advantage for the parser there.


Simon St.Laurent - Associate Editor, O'Reilly and Associates
XML Elements of Style / XML: A Primer, 2nd Ed.
XHTML: Migrating Toward XML
http://www.simonstl.com - XML essays and books

• Follow-Ups:
  • Re: attribute order (RE: Syntax Sugar and XML informationmodels)
    • From: Justin Couch <justin@v...>

• References:
  • Re: attribute order (RE: Syntax Sugar and XML information models)
    • From: Rick Jelliffe <ricko@a...>
  • RE: attribute order (RE: Syntax Sugar and XML information models)
    • From: "Simon St.Laurent" <simonstl@s...>
  • Re: attribute order (RE: Syntax Sugar and XML information models)
    • From: Justin Couch <justin@v...>

• Prev by Date: Re: attribute order (RE: Syntax Sugar and XML information models)
• Next by Date: Re: multiple types
• Previous by thread: Re: attribute order (RE: Syntax Sugar and XML information models)
• Next by thread: Re: attribute order (RE: Syntax Sugar and XML informationmodels)
• Index(es):
  • Date
  • Thread