Skip to content

Commit f6d4f0a

Browse files
committed
concrete syntax allow to *associate* prefixes with IRIs
Bob DuCharme's 2nd comment https://www.w3.org/mid/[email protected] not exactly Bob's suggestion, but I think it addresses the core of the issue.
1 parent e98cc0c commit f6d4f0a

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

spec/index.html

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -295,11 +295,14 @@ <h3>RDF Vocabularies and Namespace IRIs</h3>
295295
</tr>
296296
</table>
297297

298-
<p>In some serialization formats it is common to abbreviate <a>IRIs</a>
299-
that start with <a>namespace IRIs</a> by using a
300-
<a>namespace prefix</a> in order to assist readability. For example, the IRI
298+
<p>In some serialization formats it is common
299+
to some [=namespace IRIs=] to arbitrary [=namespace prefixes=],
300+
and to abbreviate <a>IRIs</a> that start with one of those <a>namespace IRIs</a> by using the corresponding <a>namespace prefix</a>,
301+
in order to assist readability.
302+
For example, the IRI
301303
<code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code>
302-
would be abbreviated as <code>rdf:XMLLiteral</code>.
304+
would be abbreviated as <code>rdf:XMLLiteral</code>
305+
with the prefix mapping from <a href="#tab-vocab-ns"></a>.
303306
Note however that these abbreviations are <em>not</em> valid IRIs,
304307
and must not be used in contexts where IRIs are expected.
305308
Namespace IRIs and namespace prefixes are <em>not</em> a formal part of the

0 commit comments

Comments
 (0)