Lists Home |
Date Index |
>if Element orders are enforced (at least in
>W3C XML Schemas), why are Attribute orders not?
Because attributes are conventionally used to hold metadata, as opposed
to data; that is, they express properties of an element. For instance,
if one were to state that they would like a car that is "red, 2-door,
and 6 cylinder" (without implying priority), they could just as well say
"2-door, 6 cylinder, and red" and not sacrifice the meaning.
Booz | Allen | Hamilton
"Bryce K. Nielsen" wrote:
> > Highly application-dependent.
> > <procedure><name>Replace Part#13316 in Boeing 777 Wing</name>
> > <steps>
> > <step>Ensure electrical systems are inactive per testID 32297</step>
> > <step>Ensure no fuel vapor concentrations per testID 35151</step>
> > <step>Open hatch and stick your head inside</step>
> > </steps>
> > </procedure>
> > Sometimes order matters -Tim
> I'm not saying that explicit ordering should be removed, I'm just saying
> that schema languages should allow both. It gives me a bad taste in my mouth
> to tell my partners that while the ordering of the nodes doesn't really
> matter, in order for the document to validate against my schema it has to be
> in tell-tell order.
> In the above case, it's a good thing those are elements, not attributes,
> which brings the next question if Element orders are enforced (at least in
> W3C XML Schemas), why are Attribute orders not?
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
fn:Joseph M. Chiusano