Lists Home |
Date Index |
> The XML 1.0 well-formedness definition specifically states that
> attributes are unordered, but says nothing about elements.
> This means that technically speaking, a conforming XML parser
> might decide to report the child elements of memo in Listing 1
> in any order.
Uche Ogbuji wrote:
> Several times when a question on XML design has come up here, I've
> pointed to one of my articles in this series, and the feedback has been
> good, so I thought I'd make a more holistic mention. The latest
> installment is out: "When the order of XML elements matters"
> http://www-128.ibm.com/developerworks/xml/library/x-eleord.html. See
> Copia for more.
> The other articles are:
> "When to use elements versus attributes"
> "Use XML namespaces with care"
> "Element structures for names and addresses"
> "Considering container elements"
> Also worth mentioning my discussion of ERH's excellent book _Effective
> And speaking of ERH, I'm very happy to note that he also has a column
> now on IBM developerWorks:
> I hope folks find all this helpful.
>  http://copia.ogbuji.net/blog/2005-05-05/Principles