W3C home > Mailing lists > Public > xmlschema-dev@w3.org > September 2001

Re: key/keyref problem and XSV

From: Bob Schloss <rschloss@us.ibm.com>
Date: Mon, 24 Sep 2001 09:12:07 -0400
To: xmlschema-dev@w3.org, Eric van der Vlist <vdv@dyomedea.com>
Message-ID: <OFF70C6EB4.7814A7B2-ON85256AD1.00485D78@pok.ibm.com>

I think this example is messy because 'key' is both the name of an element
and the name of a 'unique'.  I wonder if the message from XSV is because
the refer in the keyref is expected to point to a <key>, but it points to a


Eric van der Vlist <vdv@dyomedea.com>@w3.org on 09/24/2001 08:58:01 AM

Sent by:  xmlschema-dev-request@w3.org

To:   "Henry S. Thompson" <ht@cogsci.ed.ac.uk>
cc:   xmlschema-dev@w3.org
Subject:  Re: key/keyref problem and XSV

Henry S. Thompson wrote:

> Eric van der Vlist <vdv@dyomedea.com> writes:
>>I am working on key/keyref and XSV (XSV 1.203/1.106 of 2001/09/03
>>doesn't seem to follow our conclusions:
> <snip/>
>>Is-it a XSV bug or anything else I have got wrong?
> It was a non-feature, now (1.203/1.108) implemented


Just a very minor comment, though :) ...the error message (no key) when
the key is duplicated such as in:

   <key id="1"/>
   <key id="2"/>
   <key id="3"/>
   <key id="2"/>
  <ref ref="1"/>
  <ref ref="2"/>

is misleading:

<invalid char='2' code='cvc-identity-constraint.2.3.2' line='11'
resource='key-keyref-wrong.xml'>no key in {None}:key for 2</invalid>

> --I'd missed it in my last trawl of 'TODO' items, sorry.

Thanks for this reference implementation, it's very useful.


> NOTE: this may cause other previously 'invalid' documents to become OK!
> ht

See you in Scottsdale, Arizona.
Eric van der Vlist       http://xmlfr.org            http://dyomedea.com
http://xsltunit.org      http://4xt.org           http://examplotron.org
Received on Monday, 24 September 2001 09:14:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:55:53 UTC