Skip to content

Commit 3be347c

Browse files
committed
Recognize rdf:dirLangString
1 parent a9d9890 commit 3be347c

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

spec/index.html

+3-2
Original file line numberDiff line numberDiff line change
@@ -774,8 +774,9 @@ <h2>Literals and datatypes</h2>
774774
for that datatype.</p>
775775

776776
<p>RDF processors are not required to <a>recognize</a> any datatype IRIs other than
777-
<a data-cite="RDF12-CONCEPTS#dfn-language-tagged-string"><code>rdf:langString</code></a>
778-
and <a data-cite="XMLSCHEMA11-2#string"><code>xsd:string</code></a>,
777+
<a data-cite="XMLSCHEMA11-2#string"><code>xsd:string</code></a>,
778+
<a data-cite="RDF12-CONCEPTS#dfn-language-tagged-string"><code>rdf:langString</code></a>, and
779+
<a data-cite="RDF12-CONCEPTS#dfn-dir-lang-string"><code>rdf:dirLangString</code></a>
779780
but when IRIs listed in
780781
<a data-cite="RDF12-CONCEPTS#section-Datatypes">Section 5</a> of [[!RDF12-CONCEPTS]]
781782
are <a>recognized</a>, they MUST be interpreted as described there, and when the IRI <code>rdf:PlainLiteral</code> is <a>recognized</a>, it MUST be interpreted to denote the datatype defined in [[!RDF-PLAIN-LITERAL]]. RDF processors MAY recognize other datatype IRIs, but when other datatype IRIs are <a>recognized</a>, the mapping between the datatype IRI and the datatype it <a>denotes</a> MUST be specified unambiguously, and MUST be fixed during all RDF transformations or manipulations. In practice, this can be achieved by the IRI linking to an external specification of the datatype which describes both the components of the datatype itself and the fact that the IRI identifies the datatype, thereby fixing a value of the <a>datatype map</a> of this IRI.</p>

0 commit comments

Comments
 (0)