ldp.html
changeset 803 f66df9ac9d03
parent 802 2292dbc59fff
child 808 2100d73b2ad7
--- a/ldp.html	Mon Sep 08 14:29:43 2014 -0400
+++ b/ldp.html	Mon Sep 08 15:02:51 2014 -0400
@@ -1263,6 +1263,10 @@
 	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
 	to identify these advisors with URLs that contain a fragment (hash) to represent
@@ -1472,6 +1476,11 @@
 		<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
@@ -1484,6 +1493,7 @@
 		The <a href="#ldpr-gen-linktypehdr">notes on the corresponding LDPR constraint</a> apply
 		equally to LDPCs.
 	</h2>
+	<blockquote>
 	<p>Valid container type URIs for <code>rel='type'</code> defined by this document are:
 	<ul>
 	<li><code>http://www.w3.org/ns/ldp#BasicContainer</code> - for <a href="#ldpbc">LDP Basic Containers</a></li>
@@ -1491,6 +1501,7 @@
 	<li><code>http://www.w3.org/ns/ldp#IndirectContainer</code> - for <a href="#ldpic">LDP Indirect Containers</a></li>
 	</ul>
 	</p>
+	</blockquote>
 	</section><!-- Was 5.2.11 / #ldpc-5_2_11 -->
 	
 	<section id="ldpc-prefer"><h2 class="normal"><a title="LDP server">LDP servers</a>
@@ -1848,6 +1859,12 @@
 </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>  
 	MUST behave as if they
@@ -1890,6 +1907,10 @@
 <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>
 
 <section id="ldpic-general">
@@ -1921,6 +1942,9 @@
 	<var>( &lt;&gt; , foaf:primaryTopic , bob#me )</var>
 	<code>foaf:primaryTopic</code> says
 	that the <var>member-derived-URI</var> is <var>bob#me</var>.  
+	One consequence of this definition is that indirect container member creation is only 
+	well-defined by LDP when the document supplied by the client as input to the create request
+	has an RDF media type.
 	</h2>
 </section><!-- Was 5.2.10 / #ldpc-5_2_10 -->
 </section> <!-- ldpic General -->
@@ -2534,7 +2558,12 @@
 reviews, content, criticism and input in the creation of this specification:</p>
 
   <p style="margin-left: 3em;">
-  Alexandre Bertails, Andrei Sambra, Andy Seaborne, Antonis Loizou,  Arnaud Le Hors, Ashok Malhotra, Bart van Leeuwen, Cody Burleson, David Wood, Eric Prud'hommeaux, Erik Wilde, Henry Story, John Arwe, Kevin Page, Kingsley Idehen, Mark Baker, Martin P. Nally, Miel Vander Sande, Miguel Esteban Gutiérrez, Nandana Mihindukulasooriya, Olivier Berger, Pierre-Antoine Champin, Raúl García Castro, Reza B'Far, Richard Cyganiak, Roger Menday, Ruben Verborgh, Sandro Hawke, Serena Villata, Sergio Fernandez, Steve Battle, Steve Speicher, Ted Thibodeau, Tim Berners-Lee, Yves Lafon
+  Alexandre Bertails, Andrei Sambra, Andy Seaborne, Antonis Loizou,  Arnaud Le Hors, Ashok Malhotra, 
+  Bart van Leeuwen, Cody Burleson, David Wood, Eric Prud'hommeaux, Erik Wilde, Henry Story, John Arwe, 
+  Kevin Page, Kingsley Idehen, Mark Baker, Martin P. Nally, Miel Vander Sande, Miguel Esteban Gutiérrez, 
+  Nandana Mihindukulasooriya, Olivier Berger, Pierre-Antoine Champin, Raúl García Castro, Reza B'Far, 
+  Richard Cyganiak, Rob Sanderson, Roger Menday, Ruben Verborgh, Sandro Hawke, Serena Villata, Sergio Fernandez, 
+  Steve Battle, Steve Speicher, Ted Thibodeau, Tim Berners-Lee, Yves Lafon
   </p>
 
 </section>
@@ -2549,7 +2578,7 @@
 <h2>Summary</h2>
 <p>Summary of notable changes from the <a href="http://www.w3.org/TR/2014/CR-ldp-20140619/">previous public working draft</a>.</p>
 <ul>
-	<li>Indirect containers are AT RISK</li>
+	<li>Indirect containers are AT RISK for removal</li>
 	<li>Turtle is no longer required for an LDP-RS when the Accept header is absent</li>
 	<li>JSON-LD is required for an LDP-RS and LDPC create via POST, AT RISK</li>
 	<li>Changed the link relation used to articulate request constraints that a client has likely violated</li>
@@ -2562,6 +2591,7 @@
 
 <blockquote><em><a href="http://www.w3.org/TR/2014/WD-ldp-20140916">Last Call Working Draft 3</a></em></blockquote> -->
 <ul>
+	<li>2014-09-08 - Indirect containers (at risk) (JA) </li>
 	<li>2014-09-08 - Should return Turtle if Accept is absent, JSON-LD required (at risk), clarify creates  (JA) </li>
 	<li>2014-09-08 - Changed the constraints link relation to ldp#constrainedBy, per today's mtg resolution  (JA) </li>
 	<li>2014-09-08 - Clarify that Turtle/JSON-LD on LDPC POST are required only when the semantic is "create new member" (JA) </li>