ldp.html
changeset 183 910467cc58eb
parent 182 08403f15f875
child 184 30f00f94855a
--- a/ldp.html	Wed Jul 10 15:15:59 2013 -0400
+++ b/ldp.html	Wed Jul 10 15:20:27 2013 -0400
@@ -1417,12 +1417,6 @@
 	<div id="ldpc-5_3_5" class="rule">5.3.5 <strike>LDPC servers MAY split the response representation of any LDPC</strike> moved to section 4</div>
 	<div id="ldpc-5_3_6" class="rule">5.3.6 <strike>LDPC servers that support paging MUST include in the page</strike> moved to section 4</div>
 	
-	
-	<div class="ldp-issue-closed">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/18">ISSUE-18</a></div>
-	container membership and robust pagination
-	</div>	
-	
 	<div id="ldpc-5_3_7" class="rule">5.3.7 LDPC servers MAY represent the members of a paged LDPC in a sequential
 		order.  If the server does so, it MUST be specify the order using a triple 
 		whose subject is the page URI, 
@@ -1530,11 +1524,6 @@
 		the site that implements the LDPC.
 	</div>
 	
-	<div class="ldp-issue-closed">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/35">ISSUE-35</a></div>
-	POSTing to a container MUST yield a fresh URI
-	</div>
-	
 	<div id="ldpc-5_4_3" class="rule">5.4.3 LDPC servers MAY accept an HTTP POST of non-RDF representations for
 		creation of any kind of resource, for example binary resources.
 	</div>
@@ -1558,25 +1547,17 @@
 		triples in the created resource whose subject is the created
 		resource.  
 	</div>	
-		
-	<div class="ldp-issue-closed">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/20">ISSUE-20</a></div>
-	Identifying and naming POSTed resources using &lt;&gt;
-	</div>	
-	
 	<div id="ldpc-5_4_8" class="rule">5.4.8 LDPC servers SHOULD assign the subject URI for the resource to be
 		created using server application specific rules in the absence of a <a href="#ldpc-5_4_10">client hint</a>.
 	</div>
 	<div id="ldpc-5_4_8_1" class="rule">5.4.8.1 For RDF representations, LDPC servers MUST assign the base-URI for
 	   [[!RFC3987]] relative-URI resolution to be the URI of the created subject resource.
 	</div> 
-	
 	<div id="ldpc-5_4_9" class="rule">5.4.9 LDPC servers SHOULD allow clients to create new resources without
 		requiring detailed knowledge of application-specific constraints.
 		This is a consequence of the requirement to 
 		<a href="#ldpr-4_1_11">enable simple creation and modification</a> of LPDRs.
 	</div>
-
 	<div id="ldpc-5_4_10" class="rule">5.4.10 LDPC servers MAY allow clients to suggest the URI for a resource
 		created through POST, using the HTTP <code>Slug</code> header as defined in [[!RFC5023]].  LDP adds
 		no new requirements to this usage, so its presence functions as a client hint to the server 
@@ -1940,6 +1921,7 @@
 <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130701/">Third Public Working Draft</a></em></blockquote>
 -->
 <ul>
+	<li>2013-07-10 - Removed closed issues that required no new spec changes: 18, 35, 20 (SS)</li>
 	<li>2013-07-10 - ISSUE-44 move section 4.1.7 (relationships are simple RDF links) to guidance (SS)</li>
 	<li>2013-07-10 - ISSUE-72 take 2 - added ldp:MemberSubject to handle default case (SS)</li>
 	<li>2013-07-10 - ISSUE-72 adding 5.2.10 for ldp:membershipObject (SS)</li>