Skip to content

Commit 1069c14

Browse files
committed
Add suggested restrictions on the form of a term to avoid conflict with a URI scheme or a Compact IRI.
Fixes #429.
1 parent e59d2b7 commit 1069c14

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

spec/latest/json-ld/index.html

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3152,7 +3152,16 @@ <h2>Terms</h2>
31523152
to an <a>IRI</a> or a <a>blank node identifier</a>.</p>
31533153

31543154
<p>A <a>term</a> MUST NOT equal any of the JSON-LD
3155-
<a>keyword</a>.</p>
3155+
<a>keywords</a>.</p>
3156+
3157+
<p class="changed">When used as the <a>prefix</a> in a <a>Compact IRI</a>, to avoid
3158+
the potential ambiguity of a <a>prefix</a> being confused with an IRI
3159+
scheme, <a>terms</a> SHOULD NOT come from the list of URI schemes as defined in
3160+
[[!IANA-URI-SCHEMES]]. Similarly, to avoid confusion between a
3161+
<a>Compact IRI</a> and a <a>term</a>, terms SHOULD NOT include a colon (<code>:</code>)
3162+
and SHOULD be restricted to the form of
3163+
<code><a data-cite="RFC3897#section-2.2">isegment-nz-nc</a></code>
3164+
as defined in [[!RFC3897]].</p>
31563165

31573166
<p>To avoid forward-compatibility issues, a <a>term</a> SHOULD NOT start
31583167
with an <code>@</code> character as future versions of JSON-LD may introduce

0 commit comments

Comments
 (0)