Entities in XSchema

Paul Prescod papresco at technologist.com
Thu Jun 11 08:32:21 BST 1998

John Cowan wrote:
> Do you have inside information on this?  The published XPointer draft
> encourages the use of ID, because it provides an unambiguous
> set of anchors; indeed, ID is supported directly, whereas other
> attribute values are supported only through the general attribute
> machinery.

I have no information on this. IDREF is ignored by XLink. You can't use an
element with an IDREF attribute as an XLink.

The use of ID is indeed encouraged, but I will be very curious to see how
it will be managed with parsers that can optionally skip attribute
declarations. Depending on your parser, your XLinks could start breaking
because IDs may or may not be flagged as such. XML processing would be
much simpler if we had stuck strictly to the "no options" rule.

Of course XPointer would also support my proposed variant of ID, but would
do so through the general attribute mechanism. This is not a burden,
because the whole point of my ID variant is to allow the author to specify
which IDSpace she is interested in.

 Paul Prescod  - http://itrc.uwaterloo.ca/~papresco

Three things are most perilous: Connectors that corrode
Unproven algorithms, and self-modifying code

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)

More information about the Xml-dev mailing list