Skip to content

Commit 677b466

Browse files
committed
applied @hartig's suggestion*
... with some slight adaptations *: #194 (comment)
1 parent d4197f4 commit 677b466

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

spec/index.html

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -301,14 +301,15 @@ <h3>RDF Vocabularies and Namespace IRIs</h3>
301301
and to improve readability by abbreviating <a>IRIs</a> that start with one of those <a>namespace IRIs</a>
302302
by using the corresponding <a>namespace prefix</a>.
303303
For example,
304-
based on the prefix mapping in <a href="#tab-vocab-ns"></a>,
304+
based on the prefix mapping in <a href="#tab-vocab-ns">the table above</a>,
305305
the IRI <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code>
306306
would be abbreviated as <code>rdf:XMLLiteral</code>.
307-
Note however that these abbreviations are <em>not</em> valid IRIs (or only coincidentally),
307+
Note however that such abbreviations are <em>not</em> meant to be processed directly as IRIs,
308308
and must not be used in syntactic contexts where IRIs are expected.
309-
Namespace IRIs and namespace prefixes are <em>not</em> a formal part of the
310-
RDF data model. They are merely a syntactic convenience for
311-
abbreviating IRIs.</p>
309+
Note also that [=namespace IRIs=] and [=namespace prefixes=] are not a formal part of the RDF data model.
310+
Instead, they are merely a syntactic convenience for abbreviating IRIs;
311+
for processing, the actual IRIs are reconstructed by replacing the namespace prefixes with the corresponding namespace IRIs.
312+
</p>
312313

313314
<p>The term “<dfn class="lint-ignore">namespace</dfn>” on its own does not have a
314315
well-defined meaning in the context of RDF, but is sometimes informally

0 commit comments

Comments
 (0)