W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > May 2003

Change in definition of RDF literals

From: Jeremy Carroll <jjc@hplb.hpl.hp.com>
Date: Tue, 13 May 2003 16:40:30 +0200
To: <w3c-i18n-ig@w3.org>
Cc: <w3c-rdfcore-wg@w3.org>


the RDF Core WG made a decision as part of its last call process that we
decided to formally communicate to the I18N WG.

Note, we are still looking forward to your review comments on our Last Call

The decision made on Friday [1] is to modify the definition of a literal to
exclude the possibility of typed literals having an associated language tag:

> Option 4:
> Language tag is simply dropped from all typed literals including
> rdf:XMLLiteral

  Concepts is changed to say that a literal can have either a datatype or a
language tag and not both.
  rdf:XMLLiteral datatype is changed to have the identity as its lexical
value mapping (no wrapping), with consequential change to the value space of
  Other editors to make consequential changes.
from [2]

We specifically draw your attention to this being at variance with the
decisions made at the inter-WG meeting at the Cannes Plenary in 2002
concerning the scope of language tags (xml:lang) and embedded XML within RDF
(the rdf:parseType="Literal" construct).

As an example:

<rdf:Description xml:lang="en">
   <eg:prop rdf:parseType="Literal"><b>chat</b></eg:prop>


<rdf:Description xml:lang="fr">
   <eg:prop rdf:parseType="Literal"><b>chat</b></eg:prop>

are given exactly the same representation as an RDF graph and exactly the
same meaning. (Which differs from the Last Call documents in which the
language tag is significant).

The intention in these examples is now expressed as:

   <eg:prop rdf:parseType="Literal"><span


   <eg:prop rdf:parseType="Literal"><span

I have produced a rationale [3] (not endorsed by the WG).

Jeremy, on behalf of RDF Core

[1] minutes (not yet approved)
RESOLVED: Typed literals option 4 from msg 0086
[2] proposal (#4)
[3] rationale (personal not WG)
Received on Tuesday, 13 May 2003 10:40:36 UTC

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