ldp.html
changeset 186 a3471f4667d8
parent 185 58f49a8417b8
child 187 4b9d6800be9c
--- a/ldp.html	Thu Jul 11 08:45:15 2013 -0400
+++ b/ldp.html	Thu Jul 11 09:05:39 2013 -0400
@@ -370,10 +370,6 @@
 		[[!DC-TERMS]], RDF [[!RDF-PRIMER]] and RDF Schema [[!RDF-SCHEMA]], whenever
 		possible.
 	</div>
-	<div class="ldp-issue-pending">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/77">ISSUE-77</a></div>
-	why MUST a LDPR declare its type?  remove 4.1.5
-	</div>
 	<div id="ldpr-4_1_5" class="rule"><del>4.1.5 LDPRs MUST use the predicate <code>rdf:type</code> to
 		represent the concept of type. The use of non-standard type
 		predicates, as well as <code>dcterms:type</code>, is
@@ -399,14 +395,6 @@
 ones) as response <code>ETag</code> header values.
 	</div>
 	
-	<div class="ldp-issue-open">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/16">ISSUE-16</a></div>
-	Redirection of non-information resources to LDPRs
-	</div>
-	<div class="ldp-issue-pending">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/19">ISSUE-19</a></div>
-	Adressing more error cases
-	</div>	
 	<div class="ldp-issue-pending">
 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/32">ISSUE-32</a></div>
 	How can clients discover that a resource is an LDPR or LDPC, and what features are supported?
@@ -602,11 +590,7 @@
 		include an <code>Accept-Patch</code> HTTP response header [[!RFC5789]] on HTTP <code>OPTIONS</code>
 		requests, listing patch document media type(s) supported by the server.
 	</div>
-	
-	<div class="ldp-issue-pending">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/17">ISSUE-17</a></div>
-	changesets as a recommended PATCH format
-	</div>
+
 </section>
 
 <section>
@@ -1525,11 +1509,6 @@
 		only when an LDPC supports that method.  This specification does not impose any
 		new requirement to support that method, and [[!HTTP11]] makes it optional.</p>
 		
-	<div class="ldp-issue-open">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/50">ISSUE-50</a></div>
-	Intuitive Containers: better support for relative URIs
-	</div>	
-		
 	<div id="ldpc-5_4_1" class="rule">5.4.1 LDPC clients SHOULD create member resources by submitting a representation as
 		the entity body of the HTTP POST to a known LDPC. If the resource was created successfully, LDPC servers MUST
 		respond with status code 201 (Created) and the <code>Location</code>
@@ -1645,11 +1624,6 @@
 		only when an LDPC supports that method.  This specification does not impose any
 		new requirement to support that method, and [[!HTTP11]] makes it optional.</p>
 		
-	<div class="ldp-issue-open">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/56">ISSUE-56</a></div>
-	How can clients discover LDPR PUT URLs?
-	</div>	
-		
 	<div id="ldpc-5_5_1" class="rule">5.5.1 LDPC servers SHOULD NOT allow HTTP PUT to update a LDPC’s members; 
 		if the server receives such a request, it SHOULD respond with a 409
 		(Conflict) status code.
@@ -1947,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-11 - Removed closed issues that required no new spec changes: 50, 56, 16, 19, 17 (SS)</li>
 	<li>2013-07-11 - ISSUE-51 Added how a LDPR can show which LDPC is it in (SS)</li>
 	<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>