Remove feature at risk markers that do not require document changes
authorMarkus Lanthaler <mark_lanthaler@gmx.net>
Thu, 17 Oct 2013 20:20:54 +0200
changeset 2031 32ce0c86c97d
parent 2030 029987f7f3bc
child 2032 9c8ec577075d
Remove feature at risk markers that do not require document changes
spec/latest/json-ld-api/index.html
spec/latest/json-ld/index.html
--- a/spec/latest/json-ld-api/index.html	Mon Oct 14 21:58:16 2013 -0400
+++ b/spec/latest/json-ld-api/index.html	Thu Oct 17 20:20:54 2013 +0200
@@ -174,15 +174,6 @@
       IRC channel is available for real-time discussion on irc.freenode.net.</li>
   </ul>
 
-  <p>The following features are at risk and may be removed:</p>
-
-  <ul>
-    <li><a href="#at-risk-10">Support for <code>@base: null</code></a></li>
-    <li><a href="#at-risk-3">Allow blank nodes to be used as properties</a></li>
-    <li><a href="#at-risk-8">Properly referencing the DOM Promises spec</a></li>
-    <li><a href="#at-risk-4">Lists of lists and partial list conversion from RDF</a></li>
-  </ul>
-
   <p>Changes since the
     <a href="http://www.w3.org/TR/2013/WD-json-ld-api-20130411/">11&nbsp;April&nbsp;2013 Last Call Working Draft</a>:</p>
 
@@ -940,23 +931,6 @@
         If <i>remote contexts</i> is not passed, it is initialized to an empty
         <tref>array</tref>.</p>
 
-      <div class="issue atrisk" id="at-risk-10" data-number="10" title="Support for @base: null ">
-        <p class="atrisk-head">Note: This feature is
-          <a href="http://www.w3.org/2005/10/Process-20051014/tr#cfi">"at risk"</a> and may
-          be removed from this specification based on feedback. Please send feedback to
-          <a href="mailto:[email protected]">[email protected]</a>.
-          For the current status see
-          <a href="http://www.w3.org/2011/rdf-wg/wiki/JSON-LD_Features_at_Risk">features "at risk" in JSON-LD 1.0</a></p>
-       <p>Unlike many other serialization formats, JSON-LD allows to specify that
-        there is no base IRI from within the document (by setting <code>@base</code> to
-        <tref>null</tref>). The result is that the algorithm for establishing a base IRI
-        as specified in <a href="http://tools.ietf.org/html/rfc3986#section-5.1">RFC3986 section 5.1</a>
-        is overridden so relative IRIs remain relative IRIs even in the case that an IRI
-        would be available in one of the outer layers (e.g., the IRI used to retrieve
-        the document or an application supplied base IRI). Based on implementer feedback,
-        the Working Group may decide to remove this feature from JSON-LD 1.0.</p>
-      </div>
-
       <ol class="algorithm">
         <li>Initialize <i>result</i> to the result of cloning
           <tref>active context</tref>.</li>
@@ -3183,19 +3157,6 @@
       RDF triples that would have contained blank nodes as properties are
       discarded when interpreting JSON-LD as RDF.</p>
 
-    <div class="issue atrisk" id="at-risk-3" data-number="3" title="Allow blank nodes to be used as properties">
-      <p class="atrisk-head">Note: This feature is
-        <a href="http://www.w3.org/2005/10/Process-20051014/tr#cfi">"at risk"</a> and
-        may be removed from this specification based on feedback. Please send feedback to
-        <a href="mailto:[email protected]">[email protected]</a>.
-        For the current status see
-        <a href="http://www.w3.org/2011/rdf-wg/wiki/JSON-LD_Features_at_Risk">features "at risk" in JSON-LD 1.0</a></p>
-      <p>RDF graphs do not allow <tref title="blank node">blank nodes</tref> to be used
-        as an <tref>RDF predicate</tref>, while JSON-LD does.
-        Unless the <i>produce generalized RDF</i> flag is set, this algorithm will exclude
-        triples including a <tref>blank node</tref> <tref>RDF predicate</tref>.</p>
-    </div>
-
     <section class="informative">
       <h3>Overview</h3>
 
@@ -4212,27 +4173,6 @@
       <p>The <a>JsonLdErrorCode</a> represents the collection of valid JSON-LD error
         codes.</p>
 
-      <div class="issue atrisk" id="at-risk-4" data-number="4" title="Lists of lists and partial list conversion from RDF">
-        <p class="atrisk-head">Note: This feature is
-          <a href="http://www.w3.org/2005/10/Process-20051014/tr#cfi">"at risk"</a> and may
-          be removed from this specification based on feedback. Please send feedback to
-          <a href="mailto:[email protected]">[email protected]</a>.
-          For the current status see
-          <a href="http://www.w3.org/2011/rdf-wg/wiki/JSON-LD_Features_at_Risk">features "at risk" in JSON-LD 1.0</a></p>
-       <p>The JSON-LD algorithms have been updated to support conversion of lists
-          of lists to <tref title="list object">list objects</tref> by preserving
-          the blank node head of the inner list. Lists of lists can, however, not be
-          represented directly in JSON-LD using the <code>@list</code> construct;
-          they have to be represented as a set of interlinked node objects using
-          RDF's rdf:first and rdf:rest properties. Implementors are asked to pay
-          particular attention to the feature and provide feedback on lists of lists
-          and partial lists. The feature may remain in the specification, or it may
-          be removed after further implementation experience has been gathered.
-          Similarly, partial list conversion in the RDF algorithms have been marked
-          as a feature at risk and may be removed from the specification based
-          on implementation feedback.</p>
-      </div>
-
       <dl title="enum JsonLdErrorCode" class="idl">
         <dt>loading document failed</dt>
         <dd>The document could not be loaded or parsed as JSON.</dd>
--- a/spec/latest/json-ld/index.html	Mon Oct 14 21:58:16 2013 -0400
+++ b/spec/latest/json-ld/index.html	Thu Oct 17 20:20:54 2013 +0200
@@ -155,15 +155,6 @@
       IRC channel is available for real-time discussion on irc.freenode.net.</li>
   </ul>
 
-  <p>The following features are at risk and may be removed:</p>
-
-  <ul>
-    <li><a href="#at-risk-10">Support for <code>@base: null</code></a></li>
-    <li><a href="#at-risk-9">Confusion related to context-sensitivity of <code>@type</code></a></li>
-    <li><a href="#at-risk-4">Lists of lists and partial list conversion from RDF</a></li>
-    <li><a href="#at-risk-3">Allow blank nodes to be used as properties</a></li>
-  </ul>
-
   <p>Changes since the
     <a href="http://www.w3.org/TR/2013/WD-json-ld-20130411/">11&nbsp;April&nbsp;2013 Last Call Working Draft</a>:</p>
 
@@ -966,23 +957,6 @@
     <tref title="relative IRI">relative IRIs</tref> to be expanded to
     <tref title="absolute IRI">absolute IRIs</tref>.</p>
 
-  <div class="issue atrisk" id="at-risk-10" data-number="10" title="Support for @base: null">
-    <p class="atrisk-head">Note: This feature is
-      <a href="http://www.w3.org/2005/10/Process-20051014/tr#cfi">"at risk"</a> and may
-      be removed from this specification based on feedback. Please send feedback to
-      <a href="mailto:[email protected]">[email protected]</a>.
-      For the current status see
-      <a href="http://www.w3.org/2011/rdf-wg/wiki/JSON-LD_Features_at_Risk">features "at risk" in JSON-LD 1.0</a></p>
-   <p>Unlike many other serialization formats, JSON-LD allows to specify that
-    there is no base IRI from within the document (by setting <code>@base</code> to
-    <tref>null</tref>). The result is that the algorithm for establishing a base IRI
-    as specified in <a href="http://tools.ietf.org/html/rfc3986#section-5.1">RFC3986 section 5.1</a>
-    is overridden so relative IRIs remain relative IRIs even in the case that an IRI
-    would be available in one of the outer layers (e.g., the IRI used to retrieve
-    the document or an application supplied base IRI). Based on implementer feedback,
-    the Working Group may decide to remove this feature from JSON-LD 1.0.</p>
-  </div>
-
   <p>Please note that the <code>@base</code> will be ignored if used in
     external contexts.</p>
 </section>
@@ -2123,30 +2097,9 @@
 -->
 </pre>
 
-<p class="note">List of lists are not allowed in this version of JSON-LD.
-  This decision was made due to the extreme amount of added complexity when
-  processing lists of lists.</p>
-
-<div class="issue atrisk" id="at-risk-4" data-number="4" title="Lists of lists and partial list conversion from RDF">
-  <p class="atrisk-head">Note: This feature is
-    <a href="http://www.w3.org/2005/10/Process-20051014/tr#cfi">"at risk"</a> and may
-    be removed from this specification based on feedback. Please send feedback to
-    <a href="mailto:[email protected]">[email protected]</a>.
-    For the current status see
-    <a href="http://www.w3.org/2011/rdf-wg/wiki/JSON-LD_Features_at_Risk">features "at risk" in JSON-LD 1.0</a></p>
- <p>The JSON-LD algorithms have been updated to support conversion of lists
-    of lists to <tref title="list object">list objects</tref> by preserving
-    the blank node head of the inner list. Lists of lists can, however, not be
-    represented directly in JSON-LD using the <code>@list</code> construct;
-    they have to be represented as a set of interlinked node objects using
-    RDF's rdf:first and rdf:rest properties. Implementors are asked to pay
-    particular attention to the feature and provide feedback on lists of lists
-    and partial lists. The feature may remain in the specification, or it may
-    be removed after further implementation experience has been gathered.
-    Similarly, partial list conversion in the RDF algorithms have been marked
-    as a feature at risk and may be removed from the specification based
-    on implementation feedback.</p>
-</div>
+<p class="note">List of lists in the form of <tref title="list object">list objects</tref>
+  are not allowed in this version of JSON-LD. This decision was made due to the
+  extreme amount of added complexity when processing lists of lists.</p>
 
 <p>While <code>@list</code> is used to describe <em>ordered lists</em>,
   the <code>@set</code> keyword is used to describe <em>unordered sets</em>.
@@ -2947,24 +2900,6 @@
       <a href="http://www.w3.org/TR/rdf11-mt/#rdf-collections" class="externalDFN">RDF list structures</a> [[RDF11-MT]].</li>
   </ul>
 
-  <div class="issue atrisk" id="at-risk-3" data-number="3" title="Allow blank nodes to be used as properties">
-    <p class="atrisk-head">Note: This feature is
-      <a href="http://www.w3.org/2005/10/Process-20051014/tr#cfi">"at risk"</a> and may
-      be removed from this specification based on feedback. Please send feedback to
-      <a href="mailto:[email protected]">[email protected]</a>.
-      For the current status see
-      <a href="http://www.w3.org/2011/rdf-wg/wiki/JSON-LD_Features_at_Risk">features "at risk" in JSON-LD 1.0</a></p>
-    <p>RDF does not currently allow a <tref>blank node</tref> to be
-      used as a <tref>property</tref>, while JSON-LD
-      does. JSON-LD to RDF deserializers can work around this restriction, when interpreting
-      JSON-LD as RDF, by transforming such <tref title="blank node">blank nodes</tref> to
-      <tref title="IRI">IRIs</tref>, by minting new "Skolem IRIs" as per
-      <cite><a href="http://www.w3.org/TR/rdf11-concepts/#section-skolemization">Replacing Blank Nodes with IRIs</a></cite>
-      of [[RDF11-CONCEPTS]]. Based on feedback from implementors, the
-      Working Group may decide to disallow blank node properties in JSON-LD.
-      If this change would affect you, be sure to send in a comment.</p>
-  </div>
-
   <p><tref title="JSON-LD document">JSON-LD documents</tref> MAY contain data
     that cannot be represented by the <tref title="data model">data model</tref>
     defined above. Unless otherwise specified, such data is ignored when a