Re: Embedding Content as Element Content or As An Attribute Value
At 09:17 AM 30/09/97 -0400, Tyler Baker wrote: >...many people seem to embed what seemingly should >be element content as a REQUIRED element attribute. ... >Is this simply just a design preference, or else is there a concrete >reason why what seemingly is content should be embedded as an attribute. There is no automated decision procedure as to what should be an attribute and what an element. There are some things you can do with attributes but not with elements, and vice versa. But there are lots of places where either works. In these places, it is indeed, as you hypothesize, a design preference. Human document designers empirically seem to like having both elements & attributes available and find this increases their expressive power. There is a clear lesson; any software that needs to be able to fish data out of an XML document had better have the capability of extracting it either from an element or an attribute. -T. xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format