Content v. attribute
donpark at quake.net
Tue Oct 27 05:12:10 GMT 1998
I have just one question:
What do we have to treat them differently?
Given following XML fragment:
<street>1234 Park Avenue.</street>
Why not treat both city attribute and street element the same so that both
of them can be accessed with following DOM script?
String city = address.getAttribute("city")
String street = address.getAttribute("street")
or even simpler in ECMAScript:
var city = address.city
var street = address.street
In other words, why not treat attributes as a specific type of child
element: unique and childless?
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
More information about the Xml-dev