--- a/ldp.html	Thu Nov 01 12:12:55 2012 +0100
+++ b/ldp.html	Fri Nov 02 14:39:34 2012 +0100
@@ -24,6 +24,7 @@
 
           // if you wish the publication date to be other than today, set this
           // publishDate:  "2009-08-06",
+          publishDate: "$Date$",
 
           // if the specification's copyright date is a range of years, specify
           // the start date here:
@@ -363,12 +364,13 @@
 	<div id="ldpr-4_2_2" class="rule">4.2.2 LDPR servers MUST provide an <code>text/turtle</code>
 		representation of the requested LDPR.[[!TURTLE]]
 	</div>
-	<div id="ldpr-4_2_3" class="rule">4.2.3 LDPR servers SHOULD provide a <code>application/rdf+xml</code>
-		representation of the requested LDPR.[[!RDF-SYNTAX]]
+	<div id="ldpr-4_2_3" class="rule">4.2.3 LDPR servers MAY provide other
+		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>
-	Remove application/rdf+xml as a SHOULD
+	<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
@@ -1180,7 +1182,7 @@
 	<div id="ldpc-5_4_6" class="rule">5.4.6 For LDPCs, servers MUST accept a request entity body with a content
 		type of <code>text/turtle</code> [[!TURTLE]].
 	</div>
-	<div id="ldpc-5_4_7" class="rule">5.4.7 For LDPCs, LDPR servers SHOULD accept a request with an entity body
+	<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]].
 	</div>
 	<div id="ldpc-5_4_8" class="rule">5.4.8 For RDF representations, LDPC servers MUST interpret the null relative