W3C home > Mailing lists > Public > www-webont-wg@w3.org > February 2003

XMLLiteral

From: Jeremy Carroll <jjc@hpl.hp.com>
Date: Thu, 13 Feb 2003 20:57:07 +0100
To: www-webont-wg@w3.org
Message-Id: <200302132057.07657.jjc@hpl.hp.com>

PROPOSAL: rdf:XMLLiteral is a builtin datatype in OWL Lite contingent on a 
satisfactory response from RDF Core WG on the following comment.

Draft msg to www-rdf-comments
=====================
This is a message from the WebOnt WG to RDF Core WG concerning
the Last Call design of rdf:XMLLiteral and rdf:parseType="Literal".

For the full integration of this feature of RDF into OWL we require that the 
denotation in the domain of discourse be fully defined by the source RDF/XML 
file. Please remove sufficient implementation variability to ensure that this 
is the case.

An example fix would be to require an RDF/XML parser to use a specific 
canonicalization on input.

We have resolved that rdf:XMLLiteral is a builtin datatype in OWL Lite, OWL DL 
and OWL Full contingent on a satisfactory response from RDF Core WG on this 
comment.

==========

Note to WebOnt - the phrasing leaves open that RDFCore stick with the aspect 
of the current design in which the parser is *not* required to canonicalize 
but is required to ensure that (later) canonicalization is possible.
With this design an OWL implementation would need to either:
- use a canonicalizing parser (a competitive market - all are free as far as I 
know)
- use any RDF/XML parser and a separate canonicalizing component.
Hence a different example fix would be to change all the documents to only 
ever use Exclusive Canonicalization with comments and with no special 
namespaces.
The initial motivation for this separation in the design was a desire to not 
alienate parser writers who did not need canonicalization because they were 
only doing some easier metadata processing.
Received on Thursday, 13 February 2003 14:56:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:57:57 GMT