File tree Expand file tree Collapse file tree 1 file changed +5
-5
lines changed Expand file tree Collapse file tree 1 file changed +5
-5
lines changed Original file line number Diff line number Diff line change @@ -297,13 +297,13 @@ <h3>RDF Vocabularies and Namespace IRIs</h3>
297
297
</ table >
298
298
299
299
< p > In some serialization formats it is common
300
- to some [=namespace IRIs=] to arbitrary [=namespace prefixes=],
300
+ to associate some [=namespace IRIs=] to arbitrary [=namespace prefixes=],
301
301
and to abbreviate < a > IRIs</ a > that start with one of those < a > namespace IRIs</ a > by using the corresponding < a > namespace prefix</ a > ,
302
302
in order to assist readability.
303
- For example, the IRI
304
- < code > http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral </ code >
305
- would be abbreviated as < code > rdf: XMLLiteral</ code >
306
- with the prefix mapping from < a href =" #tab-vocab-ns " > </ a > .
303
+ For example,
304
+ based on the prefix mapping in < a href =" #tab-vocab-ns " > </ a > ,
305
+ the IRI < code > http://www.w3.org/1999/02/22-rdf-syntax-ns# XMLLiteral</ code >
306
+ would be abbreviated as < code > rdf:XMLLiteral </ code > .
307
307
Note however that these abbreviations are < em > not</ em > valid IRIs (or only coincidentally),
308
308
and must not be used in contexts where IRIs are expected.
309
309
Namespace IRIs and namespace prefixes are < em > not</ em > a formal part of the
You can’t perform that action at this time.
0 commit comments