@@ -1315,15 +1315,17 @@ <h2>Compact IRIs</h2>
1315
1315
Instead of having to remember and type out the entire IRI, the developer
1316
1316
can instead use the prefix in their JSON-LD markup.
1317
1317
</ p >
1318
- < p > To generate an < tref > IRI</ tref > out of a < tref > compact IRI</ tref > ,
1319
- the value is first split into a < em > prefix</ em > and
1320
- < em > suffix</ em > at the first occurrence of a colon (< code > :</ code > ).
1321
- If the < tref > active context</ tref > contains a term mapping for
1322
- < em > prefix</ em > , an IRI is generated by prepending the mapped
1323
- < em > prefix</ em > to the (possibly empty) < em > suffix</ em > using textual
1324
- concatenation. If no prefix mapping is defined, the value is used
1325
- directly as an IRI. If the prefix is an underscore
1326
- (< code > _</ code > ), the IRI remains unchanged.
1318
+ < p > Terms are interpreted as < tref > compact IRI</ tref > s if they contain at least one
1319
+ colon and the first colon is not followed by two slashes (< code > //</ code > , as in
1320
+ < code > http://example.com</ code > ). To generate the full < tref > IRI</ tref > ,
1321
+ the value is first split into a < em > prefix</ em > and < em > suffix</ em > at the first
1322
+ occurrence of a colon (< code > :</ code > ). If the < tref > active context</ tref >
1323
+ contains a term mapping for < em > prefix</ em > , an IRI is generated by
1324
+ prepending the mapped < em > prefix</ em > to the (possibly empty) < em > suffix</ em >
1325
+ using textual concatenation. If no prefix mapping is defined, the value is used
1326
+ directly as an < tref > absolute IRI</ tref > . If the prefix is an underscore
1327
+ (< code > _</ code > ), the IRI remains unchanged. This effectively means that every term
1328
+ containing a colon will be interpreted by a JSON-LD processor as an IRI.
1327
1329
</ p >
1328
1330
< p >
1329
1331
The ability to use < tref title ="compact_iri "> compact IRIs</ tref > reduces the need for developers
0 commit comments