- From: Patrick Stickler <patrick.stickler@nokia.com>
- Date: Mon, 2 Dec 2002 09:47:39 +0200
- To: "Jeremy Carroll" <jjc@hplb.hpl.hp.com>, "ext pat hayes" <phayes@ai.uwf.edu>
- Cc: <w3c-rdfcore-wg@w3.org>
[Patrick Stickler, Nokia/Finland, (+358 40) 801 9690, patrick.stickler@nokia.com] > >Frankly worrying about these relationships is implicit in our charter. > > I disagree. Our charter requires us to track XSD as closely as > possible, not to rewrite or disambiguate it. If it (XSD) is unclear > or ambiguous, then tracking it may be impossible. I think we have > come to that point here. We will not go wrong by simply not > committing ourselves on some of these topics. I would like to add stress to this point from Pat. RDF datatyping provides a framework for talking about a certain class of things, rdfs:Datatype, which have particular characteristics, and which may have relationships with regards to subset relations of their value spaces which can be captured by rdfs:subClassOf. XML Schema defines numerous datatypes which may be talked about using this RDF datatyping framework insofar as they exhibit those characteristics embodied by all members of rdfs:Datatype. If, however, some of the relationships between those datatypes are unclear, insofar as the datatyping semantics of rdfs:subClassOf is concerned, then while it is to be expected that we would work with the XML Schema folks to help clarify those issues, it is not our responsibility to do so in the RDF specs or as part of the process in completing the RDF specs. Clarifying whether xsd:float and xsd:decimal are related or whether "10"^^xsd:byte == "10"^^xsd:double is *outside* the scope of our charter and should not in any way impact the work at hand of getting the RDF specs done. Yes, it's important, but it's not the job of the RDF Core WG. Patrick
Received on Monday, 2 December 2002 02:48:30 UTC