Lists Home |
Date Index |
- From: Lars Marius Garshol <email@example.com>
- To: firstname.lastname@example.org
- Date: Sat, 05 Sep 1998 13:12:19 +0200
* Michael Kay
| * A dangling IDREF is an error; a dangling XPointer is not
They are both errors, but at different levels, which IMHO makes
perfect sense. To check your XPointers you have to run an XPointer
checker, since XPointer is not part of XML (and IMHO shouldn't be).
| That is what I mean by saying the two facilities are
| incompatible. Or to put it another way, once I have made a design
| choice to use IDREF or to use XPointer for the links in my
| documents, I am stuck with my choice.
Definitely not. As Lisa Rein points out it's easy to convert from
IDREFs to XPointers. Going the other way may not be possible, since
XPointer can do much that IDREFs cannot, in which case I guess that's
not what you want anyway. :)
| This is one of several situations in the XML family of standards
| where there is more than one way of doing the same thing, and no
| obvious way to choose between them.
I've never felt that this was a difficult choice. For links inside the
document where you can count on IDs to be present, use IDREF, for
external links, links to arbitrary elements (or with even finer
granularity if required) use XPointer.
"These are, as I began, cumbersome ways / to kill a man. Simpler, direct,
and much more neat / is to see that he is living somewhere in the middle /
of the twentieth century, and leave him there." -- Edwin Brock
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)