W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > October 2002

Re: rdfs:XMLLiteral related syntax changes

From: by way of <jjc@hpl.hp.com>
Date: Mon, 28 Oct 2002 16:29:46 -0500
Message-Id: <>
To: w3c-rdfcore-wg@w3.org

[caught in spam trap -rrs]

Date: Mon, 28 Oct 2002 15:46:43 -0500 (EST)
Message-Id: <200210282244.58618.jjc@hpl.hp.com>
From: Jeremy Carroll <jjc@hpl.hp.com>
To: w3c-rdfcore-wg@w3.org
Subject: Re: rdfs:XMLLiteral related syntax changes

 > 2) Remove the xml"<a>foo</a>" form in N-Triples


 > 1) Forbid rdf:datatype="&rdfs;XMLLiteral"

I don't really see this as necessary. If you wanted to say something peculiar
this would be a way to be clear.


   <ex:prop rdf:parseType="Literal"><a>blah</a></foo:prop>


   <ex:prop rdf:datatype="&rdfs;XMLLiteral">&lt;a&gt;blah&lt;/a&gt;</foo:prop>

entail one another (with knowledge of the datatype).

Yet whether or not they are identical is implementation dependent.

We know that:

   <ex:prop rdf:datatype="&rdfs;XMLLiteral">&lt;a &gt;blah&lt;/a&gt;</foo:prop>

is also entailed by and entails the other two, but is syntactically different
from the second.
(The extra whitespace is not significant).

Admittedly there aren't any reasons I can think of to want to be peculiar, but
it's less work to not define this special case - ummm, maybe not ...

For systems that read n-triple they really need to have an implemnetation of
rdfs:XMLLiteral mapping, then they can process the above XML correctly. For
systems that don't read n-triple, then just writing the SAX rules to
canonicalize the parseType="Literal" is probably the path of easiest
implementation. We make it easier for them by simply banning the datatype.

I am fairly neutral, weak preference agaisnt banning


Received on Monday, 28 October 2002 16:30:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:24:16 UTC