• To: "Simon St.Laurent" <simonstl@s...>, xml-dev@l...
• Subject: Re: Attribute Order (Was: Create XML )
• From: Elliotte Rusty Harold <elharo@m...>
• Date: Sun, 22 Jun 2003 16:36:29 -0400
• In-reply-to: <r01050400-1026-6FA156D2A4E411D78EFB0003937A08C2@[192.168.124.11]>
• References: <r01050400-1026-6FA156D2A4E411D78EFB0003937A08C2@[192.168.124.11]>

At 3:05 PM -0400 6/22/03, Simon St.Laurent wrote:


>It's perverse because they've taken an extra step to throw away
>information that is useful in a wide variety of information contexts,
>and have done it at the level of the XML spec - thereby ensuring that
>this information would be lost pretty much across the board.


What contexts? How would having attribute order preserved help you? 
Even in the context of an XML editor I can't say that preserving 
attribute order is all that important. People get upset when editors 
screw with their entities. I don't remember anyone getting too peeved 
because an editor shuffled their attributes.

What would preserving attribute order let you do that you can't do 
now? What concrete use cases can you present for this functionality?
-- 

   Elliotte Rusty Harold
   elharo@m...
   Processing XML with Java (Addison-Wesley, 2002)
   http://www.cafeconleche.org/books/xmljava
   http://www.amazon.com/exec/obidos/ISBN%3D0201771861/cafeaulaitA

• Follow-Ups:
  • Re: Attribute Order (Was: Create XML )
    • From: "Bob Foster" <bob@o...>
  • Re: Attribute Order (Was: Create XML )
    • From: "Amelia A. Lewis" <amyzing@t...>
  • Re: Attribute Order (Was: Create XML )
    • From: "Simon St.Laurent" <simonstl@s...>

• References:
  • Re: Attribute Order (Was: Create XML )
    • From: "Simon St.Laurent" <simonstl@s...>

• Prev by Date: Re: Attribute Order (Was: Create XML )
• Next by Date: RE: xPath 2.0, XSLT 2.0 ... size increase over v1.0
• Previous by thread: Re: Attribute Order (Was: Create XML )
• Next by thread: Re: Attribute Order (Was: Create XML )
• Index(es):
  • Date
  • Thread