Lists Home |
Date Index |
- From: <email@example.com>
- To: <firstname.lastname@example.org>
- Date: Tue, 27 Oct 1998 06:32:23 -0500 (EST)
Don Park writes:
> In other words, why not treat attributes as a specific type of
> child element: unique and childless?
Actually, that might complicate processing far more than you think:
1. Attributes are inherently unordered and have no position relative
to the element children; for any kind of iteration, you would have
to provide fake positions for them and develop a rule to make those
positions consistent across different processors (if you're
thinking of specifying that they be sorted in alphabetical order,
remember the L10N issues).
2. Attributes are often meant to be ignored unless needed. For
example, if I have
html NMTOKEN #FIXED "div"
id ID #REQUIRED
security (public|confidential) "public"
status (draft|released) "draft">
<para>This is a small section.</para>
do I really want to have to iterate through 'html', 'id',
'security', and 'status' as well as 'title' and 'para' as my
All the best,
David Megginson email@example.com
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)