Content v. attribute

[Don Park]

I have just one question:

What do we have to treat them differently?

Given following XML fragment:

<address city="NY">
  <street>1234 Park Avenue.</street>
</address>

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?

Best,

Don Park
Docuverse



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;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)