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

Re[2]: <key> problems.

From: Kevin Burges <xmldude@burieddreams.com>
Date: Mon, 19 Nov 2001 12:03:51 +0000
Message-ID: <913166537.20011119120351@burieddreams.com>
To: ht@cogsci.ed.ac.uk ((Henry S. Thompson))
CC: xmlschema-dev@w3.org

HST> Your first <field> is not allowed -- you can't use '..' in the xpaths
HST> for fields or selectors.  If what you're trying to say is that fields
HST> are unique within forms, and forms are unique within IDs, you need two 
HST> keys.  XML Schema won't support two-stage keys until a subsequent
HST> version.

Yeah, I've just realised that in terms of making things unique, even
if that key had done what I expected, it wouldn't actually have been
what I wanted - it should as you say be two keys because the FormID
must be unique.

However I also need to be able to reference the key as it was
originally written ie:

<Check FormIDRef="FORM_2" FieldIDRef="FIELD_1"/>

I need to check in this case that FIELD_1 exists within FORM_2.

Are you saying I cannot do this at present? I thought that was the
point of having multiple <field xpath=""> elements?




HST> XML Spy should have bounced your xpath.

I've already mailed then a couple of times about similar issues with
their selector xpath subset. I'll mail them again about that.

-- 
groovy baby,
 Kevin                    mailto:xmldude@burieddreams.com

++++++++++++ Cool music - http://burieddreams.com/marshan
++++++ Attitude Webzine - http://burieddreams.com/attitude
Received on Monday, 19 November 2001 07:04:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 6 December 2009 18:13:35 GMT