Changed text accordingly to the decisions taken during F2F

Author: pchampin

index.html

@@ -3105,7 +3105,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     <a>processing mode</a> set to <code>json-ld-1.1</code>.</p>
 </section>
 
-<section class="informative changed"><h2>Sealed Contexts</h2>
+<section class="informative changed"><h2>Sealed Term Definitions</h2>
   <p>JSON-LD is used in many specifications as the specified data format.
     However, there is also a desire to allow some JSON-LD contents to be processed as plain JSON,
     without using any of the JSON-LD algorithms.
@@ -3116,15 +3116,15 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     On the other hand, "plain JSON" implementations may not be able to interpret these embedded contexts,
     and hence will still interpret those terms with their original meaning.
     To prevent this divergence of interpretation,
-    JSON-LD 1.1 allows a context to be sealed.
+    JSON-LD 1.1 allows term definitions to be <em>sealed</em>.
     </p>
-  <p>A <dfn>sealed context</dfn> is a context with a member <code>@sealed</code> set to <code>true</code>.
-    It prevents further contexts to override its term definitions.
+  <p>A <dfn>sealed term definition</dfn> is a term definition with a member <code>@sealed</code> set to <code>true</code>.
+    It prevents further contexts to override this term definition.
     </p>
 
 
   <aside class="example ds-selector-tabs changed"
-    title="A sealed @context prevents its term definitions to be overridden">
+    title="A sealed term definition can not be overridden">
     <div class="selectors">
         <button class="selected" data-selects="original">Original</button>
         <button data-selects="expanded">Expanded</button>
@@ -3138,13 +3138,15 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
         "@context": [
           {
             ****"@version": 1.1****,
-            ****"@sealed": true****,
             "Person": "http://schema.org/Person",
-            "name": "http://schema.org/name",
-            "knows": "http://schema.org/knows"
+            "knows": "http://schema.org/knows",
+            "name": {
+              "@id": "http://schema.org/name",
+              ****"@sealed": true****
+            }
           },
           {
-            ****"Person": "this_attempt_to_override_Person_will_fail"****
+            ****"name": "this_attempt_to_override_name_will_fail"****
           }
         ],
         "@type": "Person",
@@ -3160,7 +3162,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     </pre>
     <pre class="expanded nohighlight"
          data-transform="updateExample"
-         data-result-for="A sealed @context prevents its term definitions to be overridden-original">
+         data-result-for="A sealed term definition can not be overridden-original">
     <!--
     [{
       "@type": ["http://schema.org/Person"],
@@ -3172,7 +3174,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     -->
     </pre>
     <table class="statements"
-           data-result-for="A sealed @context prevents its term definitions to be overridden-expanded"
+           data-result-for="A sealed term definition can not be overridden-expanded"
            data-to-rdf>
       <thead><tr><th>Subject</th><th>Property</th><th>Value</th></tr></thead>
       <tbody>
@@ -3184,7 +3186,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     </table>
     <pre class="turtle"
          data-content-type="text/turtle"
-         data-result-for="A sealed @context prevents its term definitions to be overridden-expanded"
+         data-result-for="A sealed term definition can not be overridden-expanded"
          data-transform="updateExample"
          data-to-rdf>
       <!--
@@ -3201,12 +3203,16 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     </pre>
   </aside>
 
-  <p>Terms defined by a sealed context may still be overridden by scoped contexts,
-    as long as those are defined <em>inside</em> the same sealed context as the original term definition.
+  <p>When all or most term definitions of a context need to be sealed,
+    it is possible to add a member <code>@sealed</code> set to <code>true</code>
+    to the context itself.
+    It has the same effect as sealing each of its term definitions individually.
+    Exceptions can be made by adding a member <code>@sealed</code> set to <code>false</code>
+    in some term definitions.
     </p>
 
   <aside class="example ds-selector-tabs changed"
-    title="A sealed @context can override its own terms">
+    title="A sealed @context with an exception">
     <div class="selectors">
         <button class="selected" data-selects="original">Original</button>
         <button data-selects="expanded">Expanded</button>
@@ -3225,79 +3231,76 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
             "member": "http://schema.org/member",
             "Person": {
               "@id": "http://schema.org/Person",
-              "@context": [null, {
-                "Person": "http://schema.org/Person",
-                "name": "http://schema.org/familyName"
-              }]
+              ****"@sealed": false****
             }
           }
         ],
         "name": "Digital Bazaar",
         "member": {
+          "@context": {
+            "Person": "http://xmlns.com/foaf/0.1/Person",
+            "name": "this_attempt_to_override_name_will_fail"
+          }
           "@type": "Person",
-          "name": "Sporny"
+          "name": "Manu Sporny"
         }
       }
       -->
     </pre>
     <pre class="expanded nohighlight"
          data-transform="updateExample"
-         data-result-for="A sealed @context can override its own terms-original">
+         data-result-for="A sealed @context with an exception-original">
     <!--
     [{
       "http://schema.org/name": [{"@value": "Digital Bazaar"}],
       "http://schema.org/member": [
         {
-          "@type": ["http://schema.org/Person"],
-          "http://schema.org/familyName": [{"@value": "Sporny"}]
+          "@type": ["http://xmlns.com/foaf/0.1/Person"],
+          "http://schema.org/name": [{"@value": "Manu Sporny"}]
         }
       ]
     }]
     -->
     </pre>
     <table class="statements"
-           data-result-for="A sealed @context can override its own terms-expanded"
+           data-result-for="A sealed @context with an exception-expanded"
            data-to-rdf>
       <thead><tr><th>Subject</th><th>Property</th><th>Value</th></tr></thead>
       <tbody>
         <tr><td>_:b0</td><td>schema:name</td><td>Digital Bazaar</td></tr>
         <tr><td>_:b0</td><td>schema:member</td><td>_:b1</td></tr>
-        <tr><td>_:b1</td><td>rdf:type</td><td>schema:Person</td></tr>
-        <tr><td>_:b1</td><td>schema:familyName</td><td>Sporny</td></tr>
+        <tr><td>_:b1</td><td>rdf:type</td><td>foaf:Person</td></tr>
+        <tr><td>_:b1</td><td>schema:name</td><td>Manu Sporny</td></tr>
       </tbody>
     </table>
     <pre class="turtle"
          data-content-type="text/turtle"
-         data-result-for="A sealed @context can override its own terms-expanded"
+         data-result-for="A sealed @context with an exception-expanded"
          data-transform="updateExample"
          data-to-rdf>
       <!--
+      @prefix foaf: <http://xmlns.com/foaf/0.1/> .
       @prefix schema: <http://schema.org/> .
 
       [
         schema:name "Digital Bazaar";
         schema:member [
-          a schema:Person;
-          schema:familyName "Sporny"
+          a foaf:Person;
+          schema:name "Manu Sporny"
         ]
       ] .
       -->
     </pre>
   </aside>
 
-  <p>A sealed context is not necessarily effective in the whole document.
-    Its effect starts in the node where it is referenced or embedded,
-    and propagates to deeper nodes only when traversing terms <em>that it defines</em>.
-    Traversing other terms stops the effect of the sealed context,
-    so in the remaining subtrees of the JSON document,
-    the terms from the sealed context are no longer protected against overridding.
-    The rationale is that "prose-based" implementations would generally ignore any term
-    <em>not</em> defined by the underlying specification,
-    and so the specification does apply to the parts of the documents beyond those unspecified terms.
-    </p>
+  <p>While sealed term definitions can not be directly overridden,
+      it is worth noting that setting <code>@context</code> to <code>null</code>
+      will erase everything from the active context,
+      <em>including</em> sealed term definitions.
+      </p>
 
   <aside class="example ds-selector-tabs changed"
-    title="Sealing does not extend beyond other terms">
+    title="@context null erases sealed term definitions">
     <div class="selectors">
         <button class="selected" data-selects="original">Original</button>
         <button data-selects="expanded">Expanded</button>
@@ -3312,44 +3315,35 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
           {
             ****"@version": 1.1****,
             ****"@sealed": true****,
-            "name": "http://schema.org/name",
-            "employee": "http://schema.org/employee",
             "Organization": "http://schema.org/Organization"
-          },
-          {
-            "member": "http://xmlns.com/foaf/0.1/member"
+            "name": "http://schema.org/name",
+            "employee": {
+              "@id": http://schema.org/employee",
+              ****"@context": null****
           }
         ],
         "@type": "Organization",
         "name": "Digital Bazaar",
         "employee" : {
+          #### -- because of "@context": null in the scoped context, ####
+          #### -- the active context at this point is empty; ####
+          #### -- so we can (and we must) redefine "name" below ####
           "@context": {
-            "name": "http://example.org/this_attempt_to_override_name_will_fail"
+            ****"name": "http://xmlns.com/foaf/0.1/name"****
           },
-          "name" : "Dave Longley"
-        },
-        "member": {
-          "@context": [null, {
-            "name": "http://xmlns.com/foaf/0.1/name"
-          }],
           "name": "Manu Sporny"
         }
       }
       -->
     </pre>
     <pre class="expanded nohighlight"
          data-transform="updateExample"
-         data-result-for="Sealing does not extend beyond other terms-original">
+         data-result-for="@context null erases sealed term definitions-original">
     <!--
     [{
       "@type": ["http://schema.org/Organization"],
       "http://schema.org/name": [{"@value": "Digital Bazaar"}],
       "http://schema.org/employee": [
-        {
-          "http://schema.org/name": [{"@value": "Dave Longley"}]
-        }
-      ],
-      "http://xmlns.com/foaf/0.1/member": [
         {
           "http://xmlns.com/foaf/0.1/name": [{"@value": "Manu Sporny"}]
         }
@@ -3358,42 +3352,37 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     -->
     </pre>
     <table class="statements"
-           data-result-for="Sealing does not extend beyond other terms-expanded"
+           data-result-for="@context null erases sealed term definitions-expanded"
            data-to-rdf>
       <thead><tr><th>Subject</th><th>Property</th><th>Value</th></tr></thead>
       <tbody>
         <tr><td>_:b0</td><td>rdf:type</td><td>schema:Organization</td></tr>
         <tr><td>_:b0</td><td>schema:name</td><td>Digital Bazaar</td></tr>
         <tr><td>_:b0</td><td>schema:employee</td><td>_:b1</td></tr>
-        <tr><td>_:b0</td><td>foaf:member</td><td>_:b2</td></tr>
-        <tr><td>_:b1</td><td>schema:name</td><td>Dave Longley</td></tr>
-        <tr><td>_:b2</td><td>foaf:name</td><td>Manu Sporny</td></tr>
+        <tr><td>_:b1</td><td>foaf:name</td><td>Manu Sporny</td></tr>
       </tbody>
     </table>
     <pre class="turtle"
          data-content-type="text/turtle"
-         data-result-for="Sealing does not extend beyond other terms-expanded"
+         data-result-for="@context null erases sealed term definitions-expanded"
          data-transform="updateExample"
          data-to-rdf>
       <!--
-      @prefix schema: <http://schema.org/>.
       @prefix foaf: <http://xmlns.com/foaf/0.1/>.
+      @prefix schema: <http://schema.org/>.
 
       [
         a schema:Organization;
         schema:name "Digital Bazaar";
         schema:employee [
-          schema:name "Dave Longley"
-        ];
-        foaf:member [
           foaf:name "Manu Sporny"
         ];
       ] .
       -->
     </pre>
   </aside>
 
-  <p class="note">Sealed Contexts are a new feature in JSON-LD 1.1, requiring
+  <p class="note">Sealed term definitions are a new feature in JSON-LD 1.1, requiring
     <a>processing mode</a> set to <code>json-ld-1.1</code>.</p>
 </section>
 </section>