You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<adata-cite="RDF12-CONCEPTS#section-Datatypes">Section 5</a> of [[!RDF12-CONCEPTS]]
809
-
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>
813
+
<em>are</em><a>recognized</a>, they MUST be interpreted as described there, and
814
+
when the IRI <code>rdf:PlainLiteral</code> is <a>recognized</a>,
815
+
it MUST be interpreted to denote the datatype defined in [[!RDF-PLAIN-LITERAL]].
816
+
RDF processors MAY recognize other datatype IRIs,
817
+
but when other datatype IRIs are <a>recognized</a>,
818
+
the mapping between the datatype IRI and the datatype it <a>denotes</a>
819
+
MUST be specified unambiguously,
820
+
and MUST be fixed during all RDF transformations or manipulations.
821
+
In practice, this can be achieved by the IRI linking
822
+
to an external specification of the datatype
823
+
which describes both the components of the datatype itself
824
+
and the fact that the IRI identifies the datatype,
825
+
thereby fixing a value of the <a>datatype map</a> of this IRI.</p>
810
826
811
827
<p>Literals with <adata-cite="RDF12-CONCEPTS#dfn-language-tagged-string"><code>rdf:langString</code></a>
812
-
as their datatype are an exceptional case which are given a special treatment.
813
-
The IRI <code>rdf:langString</code> is classified as a datatype IRI,
814
-
and interpreted to denote a datatype, even though no <a>L2V</a> mapping is defined for it.
815
-
The <a>value space</a> of <code>rdf:langString</code> is the set of all pairs of a string with a language tag.
816
-
The semantics of literals with this as their type are given below.</p>
828
+
or <adata-cite="RDF12-CONCEPTS#dfn-directional-language-tagged-string"><code>rdf:dirLangString</code></a>
829
+
as their datatype IRI are given special treatment.
830
+
The IRIs <code>rdf:langString</code> and <code>rdf:dirLangString</code>
831
+
are classified as datatype IRIs and interpreted to denote a datatype,
832
+
even though no <a>L2V</a> mapping is defined for them.
833
+
The <a>value space</a> of <code>rdf:langString</code>
834
+
is the set of all pairs of a string with a language tag.
835
+
The <a>value space</a> of <code>rdf:dirLangString</code>
836
+
is the set of all
837
+
3-tuples of a string, a language tag, and a base direction.
838
+
The semantics of literals with either of these as their datatype are given below.
839
+
</p>
817
840
818
841
<p>RDF allows any IRI to be used in a literal,
819
842
even when it is not <a>recognized</a> as referring to a datatype.
@@ -844,7 +867,10 @@ <h2>D-interpretations</h2>
844
867
<tr><tdclass="semantictable">If <code>rdf:langString</code> is in D,
845
868
then for every language-tagged string E with lexical form sss and language tag ttt,
846
869
IL(E)= < sss, ttt' >, where ttt' is ttt converted to lower case using US-ASCII rules</td></tr>
847
-
870
+
<tr><tdclass="semantictable">If <code>rdf:dirLangString</code> is in D,
871
+
then for every directional language-tagged string E with lexical form sss,
872
+
language tag ttt, and base direction bbb,
873
+
IL(E)= < sss, ttt', bbb >, where ttt' is ttt converted to lower case using US-ASCII rules</td></tr>
848
874
<tr><tdclass="semantictable">For every other IRI aaa in D,
849
875
I(aaa) is the datatype identified by aaa, and for every literal
<li>If no triples were added in step 2, add the RDF (and RDFS) axiomatic triples which contain <code>rdf:_1</code>.</li>
1754
1787
<li>For every IRI or literal <code>aaa</code> used in E, add <code>aaa rdf:type rdfs:Resource</code> to S.</li>
1755
1788
<li>Apply the rules <a>GrdfD1</a>, <a>rdfD1a</a>, and <a>rdfD2</a> (and the rules <a>rdfs1</a> through <a>rdfs13</a>),
1756
-
with D={<code>rdf:langString</code>, <code>xsd:string</code>}, to the set in all possible ways, to exhaustion.</li>
1789
+
with D={<code>rdf:langString</code>, <code>rdf:dirLangString</code>, <code>xsd:string</code>},
1790
+
to the set in all possible ways, to exhaustion.</li>
1757
1791
</ol>
1758
1792
1759
1793
<p>Then we have the completeness result:</p>
@@ -2233,7 +2267,12 @@ <h2>Acknowledgments</h2>
2233
2267
<h2>Substantive changes since RDF 1.1</h2>
2234
2268
2235
2269
<ul>
2236
-
<li> RDF entailment rule <a>rdfD1a</a> was added in RDF 1.2. This rule should have been included in RDF 1.1 when the two built-in datatypes (<code>xsd:string</code> and <code>rdf:langString</code>) were added to RDF entailment. </li>
2270
+
<li> RDF entailment rule <a>rdfD1a</a> was added in RDF 1.2.
2271
+
This rule should have been included in RDF 1.1 when the two built-in
2272
+
datatypes (<code>xsd:string</code> and <code>rdf:langString</code>)
2273
+
were added to RDF entailment.
2274
+
</li>
2275
+
<li><code>rdf:dirLangString</code> added to the built-in datatypes.</li>
0 commit comments