Altova Mailing List Archives

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

From: Gavin Thomas Nicol <gtn@---.--->
To: xml-dev@-----.---.---
Date: 3/30/2001 1:38:00 AM
> My view is that fixing any order where none is required is
> gratuitous, taxing and goes against the
> spoonful-of-sugar-helps-the-medicine-go-down principle; with this view,
> allowing arbitrary order is good because it does not require generators to
> (have to worry about code to) sort the attributes in ways redundant for
> naming purposes.

Right, but if you view attributes at "attributes of a type", and
content as "attributes of a type" (syntactic sugar), we get into
a funky world where one asks why you can't specify the ordering
of attributes as you can content. This is kind of where the
SML folk were coming from.

FWIW. I think it would be perfectly reasonable to have a schema
language that had provision for attribute ordering validation,
but I agree that this will almost always be *way* overkill.

I'm actually amazed that SGML is as *usable* as it
is (really!)... when you think of all the alternatives
to unordered attributes, none is anywhere nearly as appealing.


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.