typo fixed after comment Michael Scheider
authorGuus Schreiber <guus.schreiber@vu.nl>
Sun, 09 Feb 2014 10:36:28 +0100
changeset 1830 ea6e6d930bb3
parent 1829 38bd465afc08
child 1831 d7d793cb60ea
typo fixed after comment Michael Scheider
change log since PR added
rdf-mt/index.html
--- a/rdf-mt/index.html	Sun Feb 09 00:00:19 2014 +0100
+++ b/rdf-mt/index.html	Sun Feb 09 10:36:28 2014 +0100
@@ -510,7 +510,7 @@
 
 <p class="changenote">The previous version of this specification defined the parameter D as a <a>datatype map</a> from IRIs to datatypes, i.e. as a restricted kind of interpretation mapping. As the current semantics presumes that a recognized IRI identifies a unique datatype, this IRI-to-datatype mapping is globally unique and externally specified, so we can think of D as either a set of IRIs or as a fixed <a>datatype map</a>. Formally, the <dfn>datatype map</dfn> corresponding to the set D is the restriction of a <a>D-interpretation</a> to the set D. Semantic extensions which are stated in terms of conditions on <a>datatype map</a>s can be interpreted as applying to this mapping. </p>
 
-<p>The exact mechanism by which an IRI <a title="identify">identifies</a> a datatype IRI is considered to be external to the semantics, but the semantics presumes that a recognized IRI <a title="identify">identifies</a> a unique datatype wherever it occurs. RDF processors which are not able to determine which datatype is identified by an IRI cannot <a>recognize</a> that IRI, and should treat any literals with that IRI as their datatype IRI as unknown names. </p>
+<p>The exact mechanism by which an IRI <a title="identify">identifies</a> a datatype is considered to be external to the semantics, but the semantics presumes that a recognized IRI <a title="identify">identifies</a> a unique datatype wherever it occurs. RDF processors which are not able to determine which datatype is identified by an IRI cannot <a>recognize</a> that IRI, and should treat any literals with that IRI as their datatype IRI as unknown names. </p>
 
 <p>RDF literals and datatypes are fully described in <a href="http://www.w3.org/TR/rdf11-concepts/#section-Datatypes"> Section 5</a> of [[!RDF11-CONCEPTS]]. In summary: with one exception, RDF literals combine a string and an IRI <a>identify</a>ing a datatype. The exception is <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-language-tagged-string">language-tagged strings</a>, which have two syntactic components, a string and a language tag, and are assigned the type <code>rdf:langString</code>. A datatype is understood to define a partial mapping, called the <dfn>lexical-to-value mapping</dfn>, from a lexical space (a set of character strings) to values. The function <dfn>L2V</dfn> maps datatypes to their lexical-to-value mapping. A literal with datatype d denotes the value obtained by applying this mapping to the character string sss: L2V(d)(sss). If the literal string is not in the lexical space, so that the lexical-to-value mapping gives no value for the literal string, then the literal has no referent. The <dfn>value space</dfn> of a datatype is the range of the <a>lexical-to-value mapping</a>. Every literal with that type either refers to a value in the value space of the type, or fails to refer at all. An  <dfn>ill-typed</dfn> literal is one whose datatype IRI is <a>recognize</a>d, but whose character string is assigned no value by the <a>lexical-to-value mapping</a> for that datatype. </p>
 
@@ -1540,6 +1540,12 @@
 
     <section class="informative appendix" >
       <h2 id="ChangeLog">Change Log (informative)</h2>
+
+<p>Changes since Proposed Recommendation:</p>
+<ul>
+<li> <a href="http://lists.w3.org/Archives/Public/public-rdf-comments/2014Feb/0012.html">Typo</a> fixed in Sec. 7.</li>
+</ul>
+
 <p>Changes since Candidate Recommendation:</p>
 <ul>
 <li> Minor typos corrected. Some text added to section 7 defining datatype maps.</li>