Must use LDPC subtypes for rel='type', per 20140303 resln
authorsspeiche
Mon, 03 Mar 2014 15:38:14 -0500
changeset 521 46584a80fd9b
parent 520 02efebf6f85e
child 522 b3fd53a7b048
Must use LDPC subtypes for rel='type', per 20140303 resln
ldp.html
--- a/ldp.html	Mon Mar 03 14:41:49 2014 -0500
+++ b/ldp.html	Mon Mar 03 15:38:14 2014 -0500
@@ -1210,15 +1210,23 @@
 	<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
-		with a target URI of <code>http://www.w3.org/ns/ldp#Container</code>, and
+		with a target URI matching the type of container (see below) the
+		server supports, and
 		a link relation type of <code>type</code> (that is, <code>rel='type'</code>)
 		in all responses to requests made 
 		to the LDPC's HTTP <code>Request-URI</code>. 
-		<a title="LDP server">LDP servers</a> MAY provide additional HTTP <code>Link: rel='type'</code> headers
-		to advertise their support for <a href="#ldpc-typecontainer">specific LDPC types</a>.
+		<a title="LDP server">LDP servers</a> MAY provide additional HTTP <code>Link: rel='type'</code> headers.
 		The <a href="#ldpr-gen-linktypehdr">notes on the corresponding LDPR constraint</a> apply
 		equally to LDPCs.
-	</h2></section><!-- Was 5.2.11 / #ldpc-5_2_11 -->
+	</h2>
+	<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>
+	<li><code>http://www.w3.org/ns/ldp#DirectContainer</code> - for <a href="#ldpdc">LDP Direct Containers</a></li>
+	<li><code>http://www.w3.org/ns/ldp#IndirectContainer</code> - for <a href="#ldpic">LDP Indirect Containers</a></li>
+	</ul>
+	</p>
+	</section><!-- Was 5.2.11 / #ldpc-5_2_11 -->
 	
 	<section id="ldpc-prefer"><h2 class="normal"><a title="LDP server">LDP servers</a>
 		SHOULD respect all of a client's LDP-defined hints, for example 
@@ -1281,8 +1289,11 @@
 		If any model cannot be honored, the server MUST fail the request.
 	</h2><!-- Was 5.4.4 / #ldpc-5_4_4 -->
 	<ul>
-	<li>If the request header <a href="#ldpr-gen-linktypehdr">specifies an LDPR interaction model</a>, then the server MUST create an LDPR.</li>
-	<li>If the request header <a href="#ldpc-linktypehdr">specifies an LDPC interaction model</a>, then the server MUST create an LDPC.
+	<li>If the request header <a href="#ldpr-gen-linktypehdr">specifies an LDPR interaction model</a>, then the server MUST handle subsequent 
+	requests to the newly created resource's URI as if it is an LDPR.
+	(even if the content contains an <code>rdf:type</code> triple indicating a type of LDPC).</li>
+	<li>If the request header <a href="#ldpc-linktypehdr">specifies an LDPC interaction model</a>, then the server MUST handle subsequent 
+	requests to the newly created resource's URI as if it is an LDPC.
 	</li>
 	<li>This specification does not constrain the server's behavior in other cases.</li>
 	<p>Note: A consequence of this is that LDPCs can be used to create LDPCs, if the server supports doing so.</p>
@@ -2182,6 +2193,7 @@
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130930/">Candidate Recommendation Draft</a></em></blockquote> wah -->
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130730/">Last Call Draft</a></em></blockquote> -->
 <ul>
+	<li>2014-03-03 - Must use LDPC subtypes for rel='type', per 20140303 resln (SS) </li>
 	<li>2014-03-03 - Removed LDP-BC clauses that introduce membership (SS) </li>
 	<li>2014-03-03 - Tweaked LDPR PUT clauses to better match new defn of LDPR (SS) </li>
 	<li>2014-03-03 - Folded #ldpclients section into #ldprs (SS) </li>