Re: Re[2]: <key> problems.

Kevin Burges <xmldude@burieddreams.com> writes:

> 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?

The point of that is to identify something that has a multipart key.

Your Field doesn't have it's own multipart key, it has a cascaded or
multi-stage key -- first find Form with this key, then find Field with 
_this_ key.  That's what's not supported yet, sorry.

ht
-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
          W3C Fellow 1999--2001, part-time member of W3C Team
     2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
	    Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk
		     URL: http://www.ltg.ed.ac.uk/~ht/

Received on Monday, 19 November 2001 07:26:58 UTC