Lists Home |
Date Index |
- From: "John E. Simpson" <email@example.com>
- To: firstname.lastname@example.org
- Date: Fri, 21 May 1999 00:18:01 -0400
At 07:57 PM 05/20/1999 -0700, Winton Davies wrote:
>...I hope the problem is clear: Principled re-use of ID's, and
>ELEMENT TYPING of ID's.
I didn't really understand what you were trying to do. But now seems
perfectly natural to me to use attributes for IDs, although I was confused
about them myself at first. As I've come to understand it, an ID doesn't
uniquely identify content (that is, the "thing" that the document
represents). It uniquely identifies an occurrence of an *element* (that is,
a piece of the markup).
>It seems strange the only way to use IDREF's
>is in attributes (especially as there is no default "value" (c.f "id"
>for ID) ATTRIBUTE, nor a way to specify the ELEMENT TYPE of IDREF one
The idea of a default value for an ID attribute is attractive to me; my DTD
specifies numerous elements that can occur only once in the tree, and I
wanted to declare defaults for all of these. When I raised the "Why not?"
question on xml-dev a few months back, it was conceded that in a case like
this, defaults might be useful, but the general feeling was that this
wasn't a typical case. The point was moot anyhow: XML 1.0 just doesn't
>Also - how does one specify multiply IDREFS ? <tag attr1="1"
>attr1="2"> or something else ?
Separate them with spaces: <tag attr1="1 2">
John E. Simpson | The secret of eternal youth
email@example.com | is arrested development.
http://www.flixml.org | -- Alice Roosevelt Longworth
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/ and on CD-ROM/ISBN 981-02-3594-1
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)