Change from "sealed" to "protected".

Author: davidlehn

index.html

@@ -3311,7 +3311,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 Term Definitions</h2>
+<section class="informative changed"><h2>Protected 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.
@@ -3322,15 +3322,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 term definitions to be <em>sealed</em>.
+    JSON-LD 1.1 allows term definitions to be <em>protected</em>.
     </p>
-  <p>A <dfn>sealed term definition</dfn> is a term definition with a member <code>@sealed</code> set to <code>true</code>.
+  <p>A <dfn>protected term definition</dfn> is a term definition with a member <code>@protected</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 term definition can not be overridden">
+    title="A protected term definition can not be overridden">
     <div class="selectors">
         <button class="selected" data-selects="original">Original</button>
         <button data-selects="expanded">Expanded</button>
@@ -3348,7 +3348,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
             "knows": "http://schema.org/knows",
             "name": {
               "@id": "http://schema.org/name",
-              ****"@sealed": true****
+              ****"@protected": true****
             }
           },
           {
@@ -3368,7 +3368,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     </pre>
     <pre class="expanded nohighlight"
          data-transform="updateExample"
-         data-result-for="A sealed term definition can not be overridden-original">
+         data-result-for="A protected term definition can not be overridden-original">
     <!--
     [{
       "@type": ["http://schema.org/Person"],
@@ -3380,7 +3380,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     -->
     </pre>
     <table class="statements"
-           data-result-for="A sealed term definition can not be overridden-expanded"
+           data-result-for="A protected term definition can not be overridden-expanded"
            data-to-rdf>
       <thead><tr><th>Subject</th><th>Property</th><th>Value</th></tr></thead>
       <tbody>
@@ -3392,7 +3392,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 term definition can not be overridden-expanded"
+         data-result-for="A protected term definition can not be overridden-expanded"
          data-transform="updateExample"
          data-to-rdf>
       <!--
@@ -3409,16 +3409,16 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     </pre>
   </aside>
 
-  <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>
+  <p>When all or most term definitions of a context need to be protected,
+    it is possible to add a member <code>@protected</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>
+    It has the same effect as protecting each of its term definitions individually.
+    Exceptions can be made by adding a member <code>@protected</code> set to <code>false</code>
     in some term definitions.
     </p>
 
   <aside class="example ds-selector-tabs changed"
-    title="A sealed @context with an exception">
+    title="A protected @context with an exception">
     <div class="selectors">
         <button class="selected" data-selects="original">Original</button>
         <button data-selects="expanded">Expanded</button>
@@ -3432,12 +3432,12 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
         "@context": [
           {
             ****"@version": 1.1****,
-            ****"@sealed": true****,
+            ****"@protected": true****,
             "name": "http://schema.org/name",
             "member": "http://schema.org/member",
             "Person": {
               "@id": "http://schema.org/Person",
-              ****"@sealed": false****
+              ****"@protected": false****
             }
           }
         ],
@@ -3455,7 +3455,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 with an exception-original">
+         data-result-for="A protected @context with an exception-original">
     <!--
     [{
       "http://schema.org/name": [{"@value": "Digital Bazaar"}],
@@ -3469,7 +3469,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     -->
     </pre>
     <table class="statements"
-           data-result-for="A sealed @context with an exception-expanded"
+           data-result-for="A protected @context with an exception-expanded"
            data-to-rdf>
       <thead><tr><th>Subject</th><th>Property</th><th>Value</th></tr></thead>
       <tbody>
@@ -3481,7 +3481,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 with an exception-expanded"
+         data-result-for="A protected @context with an exception-expanded"
          data-transform="updateExample"
          data-to-rdf>
       <!--
@@ -3499,14 +3499,14 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     </pre>
   </aside>
 
-  <p>While sealed term definitions can not be directly overridden,
+  <p>While protected 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.
+      <em>including</em> protected term definitions.
       </p>
 
   <aside class="example ds-selector-tabs changed"
-    title="@context null erases sealed term definitions">
+    title="@context null erases protected term definitions">
     <div class="selectors">
         <button class="selected" data-selects="original">Original</button>
         <button data-selects="expanded">Expanded</button>
@@ -3520,7 +3520,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
         "@context": [
           {
             ****"@version": 1.1****,
-            ****"@sealed": true****,
+            ****"@protected": true****,
             "Organization": "http://schema.org/Organization",
             "name": "http://schema.org/name",
             "employee": {
@@ -3545,7 +3545,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     </pre>
     <pre class="expanded nohighlight"
          data-transform="updateExample"
-         data-result-for="@context null erases sealed term definitions-original">
+         data-result-for="@context null erases protected term definitions-original">
     <!--
     [{
       "@type": ["http://schema.org/Organization"],
@@ -3559,7 +3559,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     -->
     </pre>
     <table class="statements"
-           data-result-for="@context null erases sealed term definitions-expanded"
+           data-result-for="@context null erases protected term definitions-expanded"
            data-to-rdf>
       <thead><tr><th>Subject</th><th>Property</th><th>Value</th></tr></thead>
       <tbody>
@@ -3571,7 +3571,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     </table>
     <pre class="turtle"
          data-content-type="text/turtle"
-         data-result-for="@context null erases sealed term definitions-expanded"
+         data-result-for="@context null erases protected term definitions-expanded"
          data-transform="updateExample"
          data-to-rdf>
       <!--
@@ -3589,14 +3589,14 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     </pre>
   </aside>
   <p class="note">By preventing terms from being overridden,
-    sealing also prevents any adaptation of a term
+    protection also prevents any adaptation of a term
     (e.g., defining a more precise datatype, restricting the term's use to lists, etc.).
     This kind of adaptation is frequent with some general purpose contexts,
-    for which sealing would therefore hinder their usability.
+    for which protection would therefore hinder their usability.
     As a consequence, context publishers should use this feature with care.
     </p>
 
-  <p class="note">Sealed term definitions are a new feature in JSON-LD 1.1, requiring
+  <p class="note">Protected 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>