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

RE: key/keyref problem

From: Aung Aung <aaung@microsoft.com>
Date: Wed, 22 Aug 2001 10:17:58 -0700
Message-ID: <22AC3F532BE25849BF04BE95350FF91B032E337D@red-msg-08.redmond.corp.microsoft.com>
To: "Henry S. Thompson" <ht@cogsci.ed.ac.uk>
Cc: <xmlschema-dev@w3.org>
Thanks Henry, 

Now at least a few more things are clear to me. 
I will re-parse the spec further for the 'other details that my summary
doesn't cover'. I will post more on this issue if I am lost again.


-----Original Message-----
From: Henry S. Thompson [mailto:ht@cogsci.ed.ac.uk] 
Sent: Wednesday, August 22, 2001 8:35 AM
To: Aung Aung
Cc: xmlschema-dev@w3.org
Subject: Re: key/keyref problem

Sorry I've been on holiday.  I agree with everything Priscilla has said
in this thread.

Ignoring the mistaken Primer example, the spec. actually says exactly
what your Conclusion 3. says, but goes in to more detail wrt cases your
summary doesn't cover.

"Aung Aung" <aaung@microsoft.com> writes:

> 3. What I understand your interpretation:
> In short, we need following 2 rules.... with them the confusion above 
> will be clarified. (do I have it correctly)?
>     A <key A> is referable by all the <keyref A>s from only 
> ancestor-or-self of the element that host the <key A>.
>     A <keyref A> can only refer to one of the <key>s defined in the 
> decendent-or-self of the element that host the <keyref A>.

  Henry S. Thompson, HCRC Language Technology Group, University of
          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 Wednesday, 22 August 2001 13:20:03 UTC

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