[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xml-dev] Re: determining ID-ness in XML
- From: Nikita Ogievetsky <firstname.lastname@example.org>
- To: email@example.com
- Date: Mon, 05 Nov 2001 09:04:05 -0800
I am not a specialist in XML Schemas, but as I understand,
XML Schema  introduces augmentation to XML's ID/IDREF mechanism
by providing mechanism for defining keys.
Unfortunately these keys were designed to be used only for validation
purposes and are not available in XPath.
XML Schema keys contribute to PSVI, so why not let them in XPath
Could be used:
<xs:selector xpath="person"/><!--from -->
Could be used:
As I very obscurely :-) mentioned in my earlier message 
this would tremendously facilitate XSLT transformations:
If key tables were cached along with DOM document,
XSLT processor would not have to recreate xsl key tables
every time a transformation to the same document is applied.
The only problems with xs:key-s are
1) They always imply uniqueness and referential constraints
2) They are defined in context of element definitions, not the document
(I think, both should be allowed)
So it should have actually been <xs:selector xpath=".//country"/>
and <xs:selector xpath=".//person"/> in the examples above.
Again, I am not a big specialist in XML Schemas, so please
correct me if I am wrong.
----- Original Message -----
From: "Rick Jelliffe" <firstname.lastname@example.org>
Sent: Monday, November 05, 2001 3:10 AM
Subject: Re: [xml-dev] Re: determining ID-ness in XML
> From: "Henry S. Thompson" <email@example.com>
> > It's precisely because IDness is orthogonal to type-validity that
> > xml:id is the _wrong_ solution -- it doesn't allow me to combine
> > IDness with e.g. being an NMToken or CDATA or in integer or . . .
> Well then what about
> where id is an ID and key can be any string?
> Then we can use our schema language to further constrain the datatype of
> the xml:key (or xml:id) for each element as required. Or we can
> constrain the datatype of the key according to the element which refers
> to it (we can do that, can't we?)
> No-one has ever demonstrated (that I have seen) that ID is not
> a really useful mechanism for many kinds of XML documents.
> In many cases it is trivial to munge a text key into a useful ID,
> and this separation of data values from IDs prevents potential
> problems with duplicate keys which could not occur in tables
> but could occur with trees (if the keys are also data values).
> Rick Jelliffe
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>