[
Lists Home |
Date Index |
Thread Index
]
On Tue, 2003-01-21 at 18:29, Tim Bray wrote:
> Eric van der Vlist wrote:
>
> > I think that the additional complexity is overstated. SAX is my favorite
> > XML API and I find it much more robust (and only slightly more complex)
> > to never rely on the relative order of children elements.
>
> 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
Yes, indeed, but that's still a case where schema languages do not need
to enforce it which was my original point :-) ...
What I meant is that there is a tendancy to say that when the
application as no reason to specify that <foo/> is before <bar/> an
order should be imposed while I think that in most of the cases it's
better to accept the elements in any order.
Eric
--
Rendez-vous a Paris.
http://www.edifrance.org/ebd03/
------------------------------------------------------------------------
Eric van der Vlist http://xmlfr.org http://dyomedea.com
(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
------------------------------------------------------------------------
|
