Skip to content

Commit d3c4996

Browse files
committed
Update syntax for term definition as NCName, and use of Compact IRI or absolute IRI on the LHS of context.
1 parent 1dec2a1 commit d3c4996

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

spec/latest/json-ld-syntax/index.html

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -565,9 +565,8 @@ <h3>The Context</h3>
565565
<p>In JSON-LD, a <tdef>context</tdef> is used to map <tref>term</tref>s, i.e., keys with associated values
566566
in an JSON document, to <tref>IRI</tref>s. A <tdef>term</tdef> is a short word that MAY be expanded to an
567567
<tref>IRI</tref>. A <tref>term</tref> MUST have the lexical form of <cite><a
568-
href="http://www.w3.org/TR/2009/REC-xml-names-20091208/#NT-NCName">NCName</a></cite> (see [[XML-NAMES]]),
569-
an '@' followed by an NCName (other than <code>@context</code>), <tref>compact IRI</tref>, <tref>absolute IRI</tref>, or
570-
be an empty string.</p>
568+
href="http://www.w3.org/TR/2009/REC-xml-names-20091208/#NT-NCName">NCName</a></cite>
569+
(see [[XML-NAMES]]).</p>
571570
<p>The Web uses <tref title="IRI">IRIs</tref> for unambiguous identification. The
572571
idea is that these <tref>term</tref>s mean something that may be of use to other developers and that it is useful to
573572
give them an unambiguous identifier. That is, it is useful for <tref>term</tref>s to expand to IRIs so that
@@ -1798,7 +1797,7 @@ <h3>IRI Expansion Within a Context</h3>
17981797
</pre>
17991798

18001799
<p>
1801-
<tref>Term</tref>s MAY also be used on the left-hand side of a definition.
1800+
<tref>Term</tref>s, <tref title="compact iri">Compact IRIs</tref> and <tref title="iri">IRIs</tref> MAY also be used on the left-hand side of a definition.
18021801
</p>
18031802

18041803
<pre class="example" data-transform="updateExample">
@@ -1825,7 +1824,7 @@ <h3>IRI Expansion Within a Context</h3>
18251824
</pre>
18261825

18271826
<p>
1828-
Note that in this example, the <tref>compact IRI</tref> form is used in two different ways.
1827+
In this example, the <tref>compact IRI</tref> form is used in two different ways.
18291828
The first way, as shown with <code>foaf:age</code> declares both the
18301829
<tref>IRI</tref> for the term (using short-form) as well as the
18311830
<code>@type</code> associated with the <tref>term</tref>. The second way, only
@@ -1836,7 +1835,7 @@ <h3>IRI Expansion Within a Context</h3>
18361835
</p>
18371836

18381837
<p>
1839-
Full IRIs MAY also be used on the left-hand side of a <tref>context</tref>:
1838+
<tref title="absolute iri">Absolute IRIs</tref> MAY also be used on the left-hand side of a <tref>context</tref>:
18401839
</p>
18411840

18421841
<pre class="example" data-transform="updateExample">
@@ -1863,7 +1862,7 @@ <h3>IRI Expansion Within a Context</h3>
18631862
</pre>
18641863

18651864
<p>
1866-
Note that in order for the full IRI to match above, the full IRI MUST also
1865+
In order for the <tref>absolute IRI</tref> to match above, the <tref>absolute IRI</tref> MUST also
18671866
be used in the JSON-LD document. Also note that <code>foaf:homepage</code>
18681867
will not use the <code>{ "@type": "@id" }</code> declaration because
18691868
<code>foaf:homepage</code> is not the same as

0 commit comments

Comments
 (0)