Lists Home |
Date Index |
On Sat, 2005-05-07 at 22:26 -0400, G. Ken Holman wrote:
> At 2005-05-07 09:31 +1000, Rick Marshall wrote:
> >i've read a lot on this list about attribute order and the related problem
> >of "how do i decide to make something an attribute or an element?"
> >surely one simple answer to both these questions is "if order matters then
> >it is an element. if order doesn't matter then consider other things -
> >white space significance, character encoding, etc."
> >in fact a short(?) list of the differences between entities and attributes
> >would make these decisions a lot easier.
> >perhaps we could build such a list (or advertise a link to one).
> I hope this helps.
Which is just one of the resources I drew upon (and linked) in my
article on the matter:
Principles of XML design: When to use elementsversus attributes
Which, over all, I think is broader and covers more of the "list of
differences" Rick mentions.
BTW, "if you need order use elements and if not, use attributes" is far
too simplistic. What about making the choice when there's only one data
element to model? What about consideration of internal structure in the
data item that might trump the order issue (we don't get all our data
tediously normalized). Again, I dig more deeply in the article.
Uche Ogbuji Fourthought, Inc.
Use CSS to display XML, part 2 - http://www-128.ibm.com/developerworks/edu/x-dw-x-xmlcss2-i.html
XML Output with 4Suite & Amara - http://www.xml.com/pub/a/2005/04/20/py-xml.html
Use XSLT to prepare XML for import into OpenOffice Calc - http://www.ibm.com/developerworks/xml/library/x-oocalc/
Schema standardization for top-down semantic transparency - http://www-128.ibm.com/developerworks/xml/library/x-think31.html