From c3c959227ff66894aa7a5246fbc5b69f2d0f5e77 Mon Sep 17 00:00:00 2001
From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Wed, 19 Jun 2019 11:43:39 -0700
Subject: [PATCH 1/2] Describe that type-scoped contexts are only in affect on
 the node objects in which they're used. Add changes for type-scoped contexts.

Fixes #174.
---
 index.html | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index aca1794b..6ec8ebf2 100644
--- a/index.html
+++ b/index.html
@@ -3405,7 +3405,10 @@ <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>When expanding, each value of <code>@type</code> is considered
     (ordering them lexicographically) where that value is also a <a>term</a> in
@@ -12835,6 +12838,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>
 

From 08b3a1c7a211f9c123b30f44b13dcfb795c79791 Mon Sep 17 00:00:00 2001
From: Gregg Kellogg <gregg@greggkellogg.net>
Date: Wed, 19 Jun 2019 16:13:58 -0700
Subject: [PATCH 2/2] Applied @dlongley's suggestion on noting that local
 contexts introduced when a type-scoped context is in effect remain in effect
 in descendant node objects.

---
 index.html | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/index.html b/index.html
index 6ec8ebf2..6e92b2cc 100644
--- a/index.html
+++ b/index.html
@@ -3410,6 +3410,9 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     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
     the <a>active context</a> having its own <a>scoped context</a>. If so, that