- From: Brian McBride <bwm@hplb.hpl.hp.com>
- Date: Wed, 13 Nov 2002 00:38:22 +0000
- To: Dan Connolly <connolly@w3.org>, Pat Hayes <phayes@ai.uwf.edu>
- Cc: Jeremy Carroll <jjc@hplb.hpl.hp.com>, w3c-rdfcore-wg@w3.org
At 17:58 12/11/2002 -0600, Dan Connolly wrote: >On Mon, 2002-11-11 at 17:13, pat hayes wrote: >[...] > > >3.4 > > > > > >I found the following unintelligible, possibly because I don't have > > >access to the XSD example in your (or mayber Peter's) head. > > > > > >[[Users shoudl take care to distinghuish the value space ... > > >identical when viewed as class members.]] > > > > Yes, it is rather odd. The plain fact is that the XML schema specs > > are logically contradictory when one thinks of a value space as a > > set. Enquires have determined that XMLSchema value spaces are not > > sets, > >?!?!? > >yes, they are: > >"A value space is the set of values for a given datatype." > -- http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#value-space > > > but something like categories or algebras. The same thing, seen > > as a member of two different value spaces, is considered to be two > > different things. > >Inquiries may *suggest* otherwise, but only excerpts from >the text of the spec can *determine* what XML Schema >value spaces are. > >I'm interested in what leads you to think they're not >sets. Is the value space of xsd:anyURI a subset of the value space of xsd:string? yes or no? A reference to the spec would be useful. I couldn't find one, Henry Thompson hasn't provided one and has said that the spec is not clear on this point. Is "http://foo"^^xsd:string xsd.equal to "http://foo"^^xsd:anyURI (I'm talking denotations here, not syntax). Reconciling Henry's answers to these questions is what is causing the confusion. Actually Pat seemed to prefer the hex encoding datatypes, but I think that example is equivalent. Brian
Received on Tuesday, 12 November 2002 19:36:53 UTC