Skip to content

Describe that type-scoped contexts are only in affect on the node objects in which they're used #195

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.

Sign up for GitHub

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 2 commits into from
Jun 20, 2019
Merged

Describe that type-scoped contexts are only in affect on the node objects in which they're used #195

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c3c9592
Describe that type-scoped contexts are only in affect on the node obj…
gkellogg Jun 19, 2019
08b3a1c
Applied @dlongley's suggestion on noting that local contexts introduc…
gkellogg Jun 19, 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
10 changes: 9 additions & 1 deletion index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3405,7 +3405,13 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
relate things of different types, where the vocabularies in use within
different entities calls for different context scoping. For example,
<code>hasPart</code>/<code>partOf</code> may be common terms used in a document, but mean
different things depending on the context.</p>
different things depending on the context.
A <a>context</a> scoped on <code>@type</code> is only in effect for the <a>node object</a> on which
the type is used; the previous in-scope <a>contexts</a> are placed back into
effect when traversing into another <a>node object</a>.</p>

<p class="note">Any property-scoped or local contexts that were introduced in the <a>node object</a>
would still be in effect when traversing into another <a>node object</a>.</p>

<p>When expanding, each value of <code>@type</code> is considered
(ordering them lexicographically) where that value is also a <a>term</a> in
Expand Down Expand Up @@ -12835,6 +12841,8 @@ <h2>Changes since JSON-LD Community Group Final Report</h2>
using type <code>application/ld+json;profile=http://www.w3.org/ns/json-ld#frame</code>.</li>
<li>Term definitions can now be <a href="#protected-term-definitions">protected</a>,
to limit the ability of other contexts to override them.</li>
<li>A <a>context</a> defined in an <a>expanded term definition</a> may also be used for values
of <code>@type</code>, which defines a <a>context</a> to use for <a>node objects</a> including the associated type.</li>
</ul>
</section>

Expand Down