W3C home > Mailing lists > Public > www-rdf-comments@w3.org > July to September 2002

Dataypes, literals, syntax

From: Jonathan Borden <jonathan@openhealth.org>
Date: Fri, 19 Jul 2002 08:56:02 -0400
Message-ID: <049d01c22f23$a3ca9a40$0a2e249b@nemc.org>
To: <www-rdf-logic@w3.org>
Cc: <www-rdf-comments@w3.org>

I just noticed:

It got me thinking about literal datatypes (the above considers XML

Why not:

<rdf:Description rdf:about="foo://bar">
    <ex:property xsi:type="xsd:integer">10</ex:property>

being defined to parse to:

<foo://bar> ex:property xsd:integer"10" .

wouldn't this solve much of the datatypes debate -- it would _syntactically_
distinguish typed literals, as Drew McDermott correctly points out is the
way to go, and would avoid issues related to nonmonotonicity related to
interpreting a triple based on a schema that may or may not be present.

such a facility is compatible with XML Schema. This is how an XML Schema
compatible application -- xsi: stands for XML Schema Instance -- would
interpret explicit datatyping info for an XML document.

Suppose that RDF were defined 'on top of' the _post schema validation_
infoset (PSVI) or alternately a _type adorned infoset_ (TAI), rather than
the plain XML infoset. In that case, datatypes would be explicitly provided
to RDF applications.

Otherwise RDF is not really using XML Schema _datatypes_ which really means
that the PSVI/TAI is being used as the input for an application that defines
semantics, rather in the absense of the PSVI/TAI -- i.e. the current
situation -- RDF is merely trying to use the XML Schema _datatype qnames_
which for which I don't see a clear consensus on how to proceed.

Received on Friday, 19 July 2002 09:01:54 UTC

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