Skip to content
Merged
Changes from 5 commits
Commits
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
8 changes: 4 additions & 4 deletions spec/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -790,8 +790,8 @@ <h3>Literals</h3>

<p>Literals are used for values such as strings, numbers, and dates.</p>

<p>A <dfn data-local-lt="RDF literal">literal</dfn> in an <a>RDF graph</a> consists of
two, three, or four elements, as follow:</p>
<p>A <dfn data-local-lt="RDF literal">literal</dfn> consists of
two, three, or four component elements, as follows:</p>
Comment thread
pchampin marked this conversation as resolved.
Outdated

<ol>
<li>A <dfn>lexical form</dfn>, being an <a data-lt="string">RDF string</a>.
Expand All @@ -805,7 +805,7 @@ <h3>Literals</h3>
language tag MUST be well-formed according to
<a data-cite="bcp47#section-2.2.9">section 2.2.9</a>
of [[!BCP47]],
and MUST be treated accordingly, that is, in a case insensitive manner.
and MUST be treated accordingly, that is, in a case-insensitive manner.
Two [[!BCP47]]-complying strings that differ only by case represent the same [=language tag=].</li>
<li>If and only if the <a>datatype IRI</a> is
<code>http://www.w3.org/1999/02/22-rdf-syntax-ns#dirLangString</code>,
Expand Down Expand Up @@ -901,7 +901,7 @@ <h2>Literal value</h2>
<a>lexical form</a>.</li>
<li>Otherwise, the literal is <dfn data-lt-no-plural>ill-typed</dfn> and no literal value can be
associated with the literal. Such a case produces a semantic
inconsistency, but it is not <em>syntactically</em> ill-formed.
[=inconsistency=], but it is not <em>syntactically</em> ill-formed.
Implementations SHOULD accept [=ill-typed=] literals and produce RDF
graphs from them. Implementations MAY produce warnings when
encountering [=ill-typed=] literals.</li>
Expand Down
Loading