--- a/ldp.html	Fri Nov 02 14:39:34 2012 +0100
+++ b/ldp.html	Sat Nov 03 01:07:11 2012 -0400
@@ -24,7 +24,7 @@
 
           // if you wish the publication date to be other than today, set this
           // publishDate:  "2009-08-06",
-          publishDate: "$Date$",
+          //publishDate: "$Date$",
 
           // if the specification's copyright date is a range of years, specify
           // the start date here:
@@ -182,11 +182,6 @@
 		[[HTTP11]]</dd>
   </dl>
   
-  	<div class="ldp-issue">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/8">ISSUE-8</a></div>
-	<em>CLOSED</em> Better define or just not use the "Basic profile" terminology
-	</div>
-  
 <section>
 <h2 id="conventions">Conventions Used in This Document</h2>
 
@@ -321,11 +316,6 @@
 		could be other RDF formats, like N3 or NTriples, but non-RDF formats
 		like HTML [[!HTML401]] and JSON [[!RFC4627]] would be likely be common.
 		
-	<div class="ldp-issue">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/22">ISSUE-22</a></div>
-	Need to normatively reference and recommend JSON-LD
-	</div>		
-	</div>
 	<div id="ldpr-4_1_12" class="rule">4.1.12 LDPRs MAY be created, updated and deleted using methods not defined in
 		this document, for example through application-specific means, SPARQL
 		UPDATE, etc. [[!SPARQL-UPDATE]]
@@ -368,11 +358,6 @@
 		representation of the requested LDPR using standard HTTP content negotiation. 
 		If the client does not indicate a preference, <code>text/turtle</code> MUST be returned.
 		
-	<div class="ldp-issue">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/23">ISSUE-23</a></div>
-	<em>CLOSED</em> Remove application/rdf+xml as a SHOULD
-	</div>	
-	</div>
 	<div id="ldpr-4_2_4" class="rule">4.2.4 In the absence of special knowledge of the application or domain, LDPR
 		clients MUST assume that any LDPR may have multiple values for <code>rdf:type</code>.
 	</div>
@@ -1183,7 +1168,8 @@
 		type of <code>text/turtle</code> [[!TURTLE]].
 	</div>
 	<div id="ldpc-5_4_7" class="rule">5.4.7 For LDPCs, LDPR servers MAY accept a request with an entity body
-		content type of <code>application/rdf+xml</code> [[!RDF-SYNTAX]].
+		representations as indicated by request header <code>Content-Type</code> when present or derived from the 
+		entity body [[!HTTP11]].
 	</div>
 	<div id="ldpc-5_4_8" class="rule">5.4.8 For RDF representations, LDPC servers MUST interpret the null relative
 		URI for the subject of triples in the LDPR representation in the
@@ -1282,6 +1268,7 @@
 	<li>2012-10-15 - ISSUE-8 Changed references from LDBP to LDP, removed definition for "profile" and new namespace (SS)</li>	
 	<li>2012-10-15 - Included additional open ISSUES from Oct 15 WG meeting: 22, 23, 24 (SS)</li>
 	<li>2012-11-01 - Fixed minor typo and added some notes (SS)</li>
+	<li>2012-11-03 - ISSUE-22, ISSUE-23: changed sections 4.2.3 and 5.4.7. Removed closed issues. (SS)</li>
 </ul></section>
 
 <section class='appendix informative' id="todos">
@@ -1291,6 +1278,7 @@
 <ul>
 	<li>Insert some additional examples</li>
 	<li>Expand on status code usages</li>
+	<li>Editor(Steve) to consider structure based on feedback from tbl and others</li>
 </ul>
 
 	<div class="ldp-issue">