Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove 'recognized datatype IRI' in favor of RDF Semantics definition and use #124

Merged
merged 2 commits into from
Jan 9, 2025
Merged

Remove 'recognized datatype IRI' in favor of RDF Semantics definition and use #124

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7b117a3
Remove "recognized datatype iri" in favor of RDF Semantics definition…
afs Dec 21, 2024
55e77fa
'RDF processor' replaced by 'RDF implementation'
afs Jan 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
70 changes: 37 additions & 33 deletions spec/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -740,28 +740,25 @@ <h3>Literals</h3>
<li>If the literal is a <a>language-tagged string</a>,
then the literal value is a pair consisting of its <a>lexical form</a>
and its <a>language tag</a>, in that order.</li>
<li>if the literal is a <a>directional language-tagged string</a>, then the literal value is
<li>If the literal is a <a>directional language-tagged string</a>, then the literal value is
a tuple of its <a>lexical form</a>, its <a>language tag</a>, and its <a>base direction</a>,
likewise in that order.</li>

<li>If the literal's <a>datatype IRI</a> is in the set of
<a>recognized datatype IRIs</a>, let <var>d</var> be the
<a>referent</a> of the datatype IRI.
<li>If the literal's <a>datatype</a> is handled by an RDF implmentation,
<ul>
<li>If the literal's <a>lexical form</a> is in the <a>lexical space</a>
of <var>d</var>, then the literal value is the result of applying
the <a>lexical-to-value mapping</a> of <var>d</var> to the
<li>if the literal's <a>lexical form</a> is in the <a>lexical space</a>
of the <a>datatype</a>, then the literal value is the result of applying
the <a>lexical-to-value mapping</a> of the datatype to the
<a>lexical form</a>.</li>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<a>lexical form</a>.</li>
<a>lexical form</a>;</li>

Copy link
Contributor Author

@afs afs Jan 9, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For reasons unknown, most (not all) bulleted lists in the doc have . on each list item. It would be better to deal with this separately because this PR is growing in scope already and I think keeping it as focused as possible will help get it accepted.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#127

<li>Otherwise, the literal is ill-typed and no literal value can be
<li>otherwise, the literal is ill-typed and no literal value can be
associated with the literal. Such a case produces a semantic
inconsistency but is not <em>syntactically</em> ill-formed.
Implementations MUST accept ill-typed literals and produce RDF
Implementations SHOULD accept ill-typed literals and produce RDF
graphs from them. Implementations MAY produce warnings when
encountering ill-typed literals.</li>
</ul>
</li>
<li>If the literal's <a>datatype IRI</a> is <em>not</em> in the set of
<a>recognized datatype IRIs</a>, then the literal value is
<li>If the literal's <a>datatype IRI</a> is <em>not</em>
handled by an RDF implementation, then the literal value is
not defined by this specification.</li>
</ul>

Expand Down Expand Up @@ -1098,12 +1095,11 @@ <h2>Datatypes</h2>
in terms of XML Schema. RDF re-uses many of the XML Schema
built-in datatypes, and defines three additional datatypes,
<code><a>rdf:JSON</a></code>, <code><a>rdf:HTML</a></code>, and <code><a>rdf:XMLLiteral</a></code>.
The list of datatypes supported by an implementation is determined
by its <a>recognized datatype IRIs</a>.</p>
</p>

<p>A <dfn>datatype</dfn> consists of a <a>lexical space</a>,
a <a>value space</a> and a <a>lexical-to-value mapping</a>, and
is denoted by one or more <a>IRIs</a>.</p>
is identified by one or more <a>IRIs</a>.</p>

<p>The <dfn>lexical space</dfn> of a datatype is a set of <a>strings</a>.</p>

Expand Down Expand Up @@ -1295,13 +1291,10 @@ <h3>The XML Schema Built-in Datatypes</h3>
<section>
<h3>Datatype IRIs</h3>

<p>Datatypes are identified by <a>IRIs</a>. If
<var>D</var> is a set of IRIs which are used to refer to
datatypes, then the elements of <var>D</var> are called
<span id="dfn-recognized-datatype-iris"><!-- obsolete term--></span><dfn data-lt="recognized datatype IRI">recognized datatype IRIs</dfn>.
Recognized IRIs have fixed
<a href="#referents">referents</a>. If any IRI of the form
<code>http://www.w3.org/2001/XMLSchema#xxx</code> is recognized, it
<p>Datatypes are identified by <a>IRIs</a>.</p>
<p>
If any IRI of the form
<code>http://www.w3.org/2001/XMLSchema#xxx</code> is handled by an RDF implementation, it
MUST refer to the RDF-compatible XSD type named <code>xsd:xxx</code> for
every XSD type listed in <a href="#xsd-datatypes">section 5.1</a>.</p>

Expand All @@ -1317,12 +1310,13 @@ <h3>Datatype IRIs</h3>
refers to the datatype <code><a>rdf:JSON</a></code>.</li>
</ul>

<p>RDF processors are not required to recognize datatype IRIs.
Any literal typed with an unrecognized IRI is treated just like
an unknown IRI, i.e. as referring to an unknown thing. Applications
MAY give a warning message if they are unable to determine the
referent of an IRI used in a typed literal, but they SHOULD NOT
reject such RDF as either a syntactic or semantic error.<p>
<p>RDF implementations are not required to handle all datatypes.
Any literal typed with a datatype not handled by an RDF implementation
is treated just like an unknown IRI, i.e., as referring to an unknown thing.
Applications MAY give a warning message if they are unable to determine the
referent of an IRI used in a typed literal. RDF implementations SHOULD
not reject a literal with an unknown datatype as either a syntactic or
semantic error.<p>

<p>Other specifications MAY impose additional constraints on
<a>datatype IRIs</a>, for example, require support
Expand All @@ -1343,6 +1337,14 @@ <h3>Datatype IRIs</h3>
user-defined simple XML Schema datatypes</a>
is suggested in [[SWBP-XSCH-DATATYPES]]. RDF implementations
are not required to support either of these facilities.</p>

<p class="note" id="note-recognized-datatype-iris">
In RDF 1.1, <em><span id="dfn-recognized-datatype-iris">Recognized datatype IRIs</span></em>
were defined in RDF Concepts, overlapping with
<a data-cite="RDF12-SEMANTICS#dfn-recognized">RDF Semantics, "recognizing"</a>
datatype IRIs for <a data-cite="RDF12-SEMANTICS#dfn-semantic-extension">semantic extensions</a>.
</p>

</section>
</section>

Expand Down Expand Up @@ -1465,7 +1467,7 @@ <h2>Generalizations of RDF Triples, Graphs, and Datasets</h2>

<section id="section-additional-datatypes" class="appendix">
<h2>Additional Datatypes</h2>
<p>This section defines additional <a>datatypes</a> that RDF processors MAY support.</p>
<p>This section defines additional <a>datatypes</a> that RDF implementations MAY support.</p>

<section id="section-html">
<h3>The <code>rdf:HTML</code> Datatype</h3>
Expand Down Expand Up @@ -1696,7 +1698,6 @@ <h3>The <code>rdf:JSON</code> Datatype</h3>

</section>


<section id="privacy" class="appendix informative">
<h2>Privacy Considerations</h2>
<p>RDF is used to express arbitrary application data,
Expand Down Expand Up @@ -1964,10 +1965,14 @@ <h2>Changes between RDF 1.1 and RDF 1.2</h2>
use the recommended BCP47 format,
or do something else, as long it is performed consistently.</li>
<li>Removed the section on the canonical mapping for the <a>rdf:XMLLiteral</a> datatype.</li>
<li>Refer to the definition and discussion of
<a data-cite="RDF12-SEMANTICS#dfn-recognized">RDF Semantics, "recognizing"</a>
datatype IRIs, instead of <em>Recognized datatype IRIs</em>.</li>
<li>The informal terminolgy "RDF processor" has been removed.</li>
</ul>

<p class="note">A detailed overview of the differences between RDF versions&nbsp;1.0
and 1.1 can be found in [[[RDF11-NEW]]] [[RDF11-NEW]].</p>
<p class="note">A detailed overview of the differences between RDF versions&nbsp;1.1
and 1.2 can be found in [[[RDF12-NEW]]] [[RDF12-NEW]].</p>
</section>

<section id="index"></section>
Expand All @@ -1978,4 +1983,3 @@ <h2>Changes between RDF 1.1 and RDF 1.2</h2>

</body>
</html>

Loading