--- a/ldp.html Mon Oct 20 13:58:18 2014 -0400
+++ b/ldp.html Mon Oct 20 14:00:15 2014 -0400
@@ -256,8 +256,6 @@
<li>The <a href="#header-accept-post">HTTP Accept-Post header</a>,
that allows clients to determine which media types a server accepts on POST requests.
</li>
- <li>Support for <a href="#atrisk-indirect-containers">indirect containers</a>.
- </li>
</ol>
</section>
@@ -1292,10 +1290,6 @@
and linked to the net-worth resource using the appropriate predicate. Similar ambiguities arise
if the client wishes to list the members and/or contained resources.
</p>
-
- <div class="atrisk" id="atrisk-indir-cont-ex"><p class="atrisktext">Feature At Risk</p>
- <p>The LDP Working Group proposes the REMOVAL of indirect containers, unless more implementation reports arrive shortly.</p>
- </div>
<p>Continuing in the multiple containers direction, we will now extend our net worth example to add a container for
advisors (people) that have managed the assets and liabilities. We have decided
@@ -1506,11 +1500,6 @@
<code>rdf:Seq</code> or <code>rdf:List</code>.
</h2></section><!-- Was 5.2.8 / #ldpc-5_2_8 -->
- <div class="atrisk" id="atrisk-indir-cont-ref1"><p class="atrisktext">Feature At Risk</p>
- <p>The LDP Working Group proposes the REMOVAL of indirect containers, unless more implementation reports arrive shortly,
- which would change the contents of the list below.</p>
- </div>
-
<section id="ldpc-linktypehdr"><h2 class="normal"><a title="LDP server">LDP servers</a>
exposing LDPCs
MUST advertise their LDP support by exposing a HTTP <code>Link</code> header
@@ -1892,12 +1881,6 @@
and whose object is the URI of <var>membership-predicate</var>.
</h2></section><!-- Was 5.2.5.2 / #ldpc-5_2_5_2 -->
</section>
-
- <div class="atrisk" id="atrisk-indir-cont-ref2"><p class="atrisktext">Feature At Risk</p>
- <p>The LDP Working Group proposes the REMOVAL of indirect containers, unless more implementation reports arrive shortly.</p>
- <p>If it is removed, ldp:insertedContentRelation will be removed as well; its only function currently is to distinguish
- creation behavior between direct and indirect containers.</p>
- </div>
<section id="ldpdc-indirectmbr-basic"><h2 class="normal">
<a title="Linked Data Platform Direct Container">LDP Direct Containers</a>
@@ -1940,10 +1923,6 @@
<section id="ldpic">
<h2>Indirect</h2>
-
- <div class="atrisk" id="atrisk-indirect-containers"><p class="atrisktext">Feature At Risk</p>
- <p>The LDP Working Group proposes the REMOVAL of indirect containers, unless more implementation reports arrive shortly.</p>
- </div>
<p>The following section contains normative clauses for <a title="">Linked Data Platform Indirect Container</a>.</p>
@@ -2625,6 +2604,7 @@
<!-- <blockquote><em><a href="http://www.w3.org/TR/2014/CR-ldp-20140619/">Candidate Recommendation Draft</a></em></blockquote> -->
<ul>
+ <li>2014-10-20 - Removed at-risk label for Indirect Containers (SS)</li>
<li>2014-10-20 - Removed at-risk label for json-ld requirement (SS)</li>
<li>2014-10-20 - Removed at-risk feature that clients should be prepared to handle server-initiated paging (SS)</li>
<li>2014-10-20 - Define LDP-server-managed for Robert Sanderson thread (JA)</li>