Lists Home |
Date Index |
- From: Tyler Baker <firstname.lastname@example.org>
- To: email@example.com
- Date: Tue, 07 Apr 1998 10:21:50 -0400
I asked the same question about 4 months ago concerning using attributes vs.
elements on this list and got some interesting answers. In that time I have found
that for modeling objects a few principles come to mind.
If you are modeling an object which will never change at all (like a Rectangle)
then you would be best to do something like this:
<RECTANGLE x="0" y="0" width="0" height="0"/>
The rationale for this approach over using elements is that in most XML processors
you will get all of the attribute values at once that are necessary for generally
immutable objects like Rectangle's. In a particular application of mine I found
that I would call setBounds() in java.awt.Component 4 times using the element
approach vs. only once with the attributes approach.
If you are representing something whose type may evolve over time like a user
profile in a database, then the element approach I feel works better in the long
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)