Skip to content

Editorial issues #130

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 27 commits into from
Feb 15, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
27 commits
Select commit Hold shift + click to select a range
3fcd5d4
Add _scoped context_ and _embedded context_ definitions to terms, and…
gkellogg Feb 13, 2019
1f0e2e1
Clarify definition of _list objects_ and _set objects_, and that they…
gkellogg Feb 13, 2019
2cabc02
Remove redundant paragraph from conformance section.
gkellogg Feb 13, 2019
c9e4cc6
Clean up example comments so they don't wrap.
gkellogg Feb 13, 2019
210cbc6
Fix `@type` values not marked as code.
gkellogg Feb 13, 2019
fcf9261
Add a note on URLs and URNs in 3.2.
gkellogg Feb 13, 2019
38772eb
Move note on type coercion as distinct from specifying the type of a …
gkellogg Feb 13, 2019
ba3af21
Further describe the use of an outer array in 4.1, and introduce the …
gkellogg Feb 13, 2019
6e2ceb2
Fix example 19.
gkellogg Feb 13, 2019
07bda65
Add example showing how scoped contexts are processed along with embe…
gkellogg Feb 14, 2019
ac06138
Improve the description for the "Term expansion for values, not ident…
gkellogg Feb 14, 2019
b714efb
Better describe that `@container: @list` is recursively applied to ar…
gkellogg Feb 14, 2019
fb6b43e
Clarify that `obj.post.de` only applies to JavaScript access, or simi…
gkellogg Feb 14, 2019
5c48aec
misc typos
pchampin Feb 14, 2019
ca24cd0
Remove at-risk for issue #23.
gkellogg Feb 14, 2019
d043256
Clean up data model description of what a node is.
gkellogg Feb 14, 2019
d09d972
Section no Appendix.
gkellogg Feb 14, 2019
f578305
Cleanup open issues.
gkellogg Feb 14, 2019
01fc7e4
Address @iherman's comment on term selection for prefixes.
gkellogg Feb 15, 2019
ebfda77
Move description of using `@set` with `@type` to from Aliasing Keywor…
gkellogg Feb 15, 2019
2dd88d0
Address @iherman comment in PR.
gkellogg Feb 15, 2019
3e0b7b0
Implement @iherman's suggested change on retrieving contexts.
gkellogg Feb 15, 2019
5f0445f
Address @iherman's concern about nesting.
gkellogg Feb 15, 2019
cbd8024
Update references from HTML52 to just HTML for the living spec.
gkellogg Feb 15, 2019
b53e751
Use _MUST NOT_ instead of _SHOULD NOT_ for prefixes coming from IANA.
gkellogg Feb 15, 2019
6cb2b72
Distinguish between a graph object, and a node object that can also d…
gkellogg Feb 15, 2019
7031cc2
Clarify that index maps for named graphs do not name the graphs, but …
gkellogg Feb 15, 2019
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 16 additions & 3 deletions common/terms.html
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,16 @@
Whenever possible, an <a>edge</a> should be labeled with an <a>IRI</a>.
<div class="issue atrisk">The use of <a>blank node identifiers</a> to label properties is obsolete,
and may be removed in a future version of JSON-LD.</div></dd>
<dt><dfn>embedded context</dfn></dt><dd>
An embedded <a>context</a> is a <a>dictionary</a> composed of a combintation of
<a>term definitions</a>, a <a>vocabulary mapping</a>, a <a>base IRI</a> and <a>default language</a>.
An <a>embedded context</a> may appear as part of a <a>node object</a> or <a>value object</a> using the
<code>@context</code> <a>member</a>.
</dd>
<dt><dfn>scoped context</dfn></dt><dd>
A <a>scoped context</a> is part of an <a>expanded term definition</a> using the
<code>@context</code> <a>member</a>. It has the same form as an <a>embedded context</a>.
</dd>
<dt><dfn>expanded term definition</dfn></dt><dd>
An expanded term definition is a <a>term definition</a>
where the value is a <a>dictionary</a>
Expand Down Expand Up @@ -150,7 +160,8 @@
is a <a>graph object</a> which does not have an <code>@id</code> <a>member</a>.
Note that <a>node objects</a> may have a <code>@graph</code> member,
but are not considered <a>graph objects</a> if they include any other <a>members</a>.
A top-level object consisting of <code>@graph</code> is also not a <a>graph object</a>.</dd>
A top-level object consisting of <code>@graph</code> is also not a <a>graph object</a>.
Note that a <a>node object</a> may also represent a <a>named graph</a> it it includes other properties.</dd>
<dt><dfn>index map</dfn></dt><dd>
An <a>index map</a> is a <a>dictionary</a> value of a <a>term</a>
defined with <code>@container</code> set to <code>@index</code>,
Expand Down Expand Up @@ -212,7 +223,8 @@
A <a>list</a> is an ordered sequence of <a>IRIs</a>, <a>blank nodes</a>, and <a>JSON-LD values</a>.
See <dfn data-cite="RDF-SCHEMA#ch_collectionvocab" data-lt="collection" class="preserve">RDF collection</dfn> in [[RDF-SCHEMA]].</dd>
<dt><dfn>list object</dfn></dt><dd>
A <a>list object</a> is a <a>dictionary</a> that has a <code>@list</code> key.</dd>
A <a>list object</a> is a <a>dictionary</a> that has a <code>@list</code> key.
It may also have an <code>@index</code> key, but no other members.</dd>
<dt><dfn>literal</dfn></dt><dd>
An <a>object</a> expressed as a value such as a string, number or in expanded form.</dd>
<dt><dfn>local context</dfn></dt><dd>
Expand Down Expand Up @@ -294,7 +306,8 @@
are resolved relative to the <a>vocabulary mapping</a>,
not the <a>base IRI</a>.</dd>
<dt><dfn>set object</dfn></dt><dd>
A <a>set object</a> is a <a>dictionary</a> that has an <code>@set</code> <a>member</a>.</dd>
A <a>set object</a> is a <a>dictionary</a> that has an <code>@set</code> <a>member</a>.
It may also have an <code>@index</code> key, but no other members.</dd>
<dt><dfn>subject</dfn></dt><dd>
A <a data-cite="RDF11-CONCEPTS#dfn-subject" class="externalDFN">subject</a>
is a <a>node</a> in a <a>linked data graph</a>
Expand Down
Loading