W3C home > Mailing lists > Public > www-rdf-comments@w3.org > January to March 2003

problems with RDF datatyping

From: Peter F. Patel-Schneider <pfps@research.bell-labs.com>
Date: Thu, 16 Jan 2003 20:22:18 -0500 (EST)
Message-Id: <20030116.202218.03877976.pfps@research.bell-labs.com>
To: www-webont-wg@w3.org, www-rdf-comments@w3.org

In trying to make the OWL semantics correspond to the RDF semantics I came
up with the following problems in RDF datatyping:

1/ A datatype is an element of IR, because the RDF MT says that datatypes are
denoted by URI references.  However, rdf:XMLLiteral is said to be a
datatype, but rdf:XMLLiteral is a URI reference.  Something is wrong here.

2/ XSD-interpretations include in their datatypes the XML Schema datatypes
that are problematic when removed from XML documents or have other
problems.  XSD-interpretations also include, for example, the datatype
named FOO, which is not defined as an XML datatype.

3/ A datatype has to be more than is specified in the RDF MT.  Except for
XSD-interpretations, which explicitly mention the URI-reference to datatype
relationship, there is no way of tying the intended URI-reference for a
datatype to that datatype.  For example, if I have D containing a datatype
for integers and a datatype for strings, there is no way to require that a
particular URI reference, say ex:int, denotes the integer datatype.

It probably makes more sense to say that a datatype is a four-tuple,
consisting of a URI reference, a lexical space, a value space, and a
lexical-to-value mapping.  

Peter F. Patel-Schneider
Bell Labs Research
Lucent Technologies
Received on Thursday, 16 January 2003 20:22:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:44:01 UTC