W3C home > Mailing lists > Public > public-rdf-comments@w3.org > November 2011

Re: Request for clarifications re XMLLiteral in RDFa (was: Re: XML Literals poll)

From: Richard Cyganiak <richard@cyganiak.de>
Date: Thu, 24 Nov 2011 14:33:10 +0000
Cc: "public-rdf-comments@w3.org" <public-rdf-comments@w3.org>
Message-Id: <7FFFEB2B-FAD7-41C0-AB74-942319F7023C@cyganiak.de>
To: Gregg Kellogg <gregg@kellogg-assoc.com>
Hi Gregg,

On 24 Nov 2011, at 00:37, Gregg Kellogg wrote:
>> Namespace promotion isn't a feature of rdf:XMLLiterals – it's a feature of certain RDF syntaxes (RDF/XML for @parseType="literal", and RDFa). Changing this for RDFa is not something that the RDF WG can help with, I think.
> Good point, it's RDFa that says the XMLLiteral should be in Exclusive Canonical representation, not the datatype.

Well, not quite – the rdf:XMLLiteral datatype definition *does* say that the lexical space is in XC14N representation. But it doesn't say anything about how a concrete syntax has to handle namespaces.

>> What you're saying is that rdf:XMLLiteral is being abused to indicate the presence of general HTML markup. This abuse indicates the existence of an important unmet need. The response should be a call for meeting that need, and not necessarily a call for changing rdf:XMLLiteral to legalize the abuse.
> My takeaway is that the RDFWA WG might want to look more at the HTML Literal as being more appropriate for our purposes.

The RDF WG also has an open issue regarding the possibility of adding an HTML datatype:

This is for the same reasons that we discussed here – the original main purpose for rdf:XMLLiteral was to enable the inclusion of small snippets of “rich text” in literals in RDF graphs. In 2011, this requirement would perhaps be better met by an HTML datatype (my personal opinion – not necessarily RDF WG consensus). On the other hand, the RDF WG may not be the best place to define such a datatype. We might need some coordination across WGs here.

Received on Thursday, 24 November 2011 14:33:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:29:53 UTC