Proposed text for language-tagged strings (ISSUE-71)

Below is proposed text for RDF Concepts. Summary:

1. All literals are typed. “Typed literal” becomes redundant.
2. There's one exceptional datatype IRI, rdf:langString. Typed literals with that IRI have an additional language tag.
3. No formal datatype is defined for the IRI rdf:langString.
4. The value assignment for literals gets an exception for rdf:langString-typed literals.

Best,
Richard



6.5 RDF LITERALS

Replace first four paragraphs with:

[[
A literal consists of:

* a lexical form being a Unicode [UNICODE] string, which should be in Normal Form C [NFC],
* a datatype IRI being an IRI.

A language-tagged string is any literal whose datatype IRI is equal to rdf:langString. In addition to lexical form and datatype IRI, a language-tagged string also has:

* a non-empty language tag as defined by [BCP47]. The language tag must be well-formed according to section 2.2.9 of [BCP47], and must be normalized to lowercase.
]]


6.5.2 THE VALUE CORRESPONDING TO A TYPED LITERAL

Replace second paragraph with:

[[
The value associated with a literal whose datatype IRI is not equal to rdf:langString is found by applying the lexical-to-value mapping associated with the datatype IRI to the lexical form.

The value associated with a language-tagged string is a pair consisting of its lexical form and its language tag, in that order.
]]


5. DATATYPES

Add to end of section:

[[
NOTE: Language-tagged strings have the datatype IRI rdf:langString. No datatype is formally defined for this IRI because the definition of datatypes does not accommodate language tags.
]]


Replace “typed literal” with “literal” in various places.

Received on Tuesday, 13 September 2011 04:04:53 UTC