[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Content v. attribute

• From: "Don Park" <donpark@q...>
• To: <xml-dev@i...>
• Date: Mon, 26 Oct 1998 21:11:08 -0800

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@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...)

• Follow-Ups:
  • Re: Content v. attribute
    • From: <david@m...>
  • Re: Content v. attribute
    • From: Paul Prescod <papresco@t...>

• Prev by Date: RE: DTD for X12 or EDIFACT
• Next by Date: Re: Content v. attribute
• Previous by thread: Re: Content v. attribute
• Next by thread: Re: Content v. attribute
• Index(es):
  • Date
  • Thread