--- a/ldp.html	Thu Apr 25 16:44:31 2013 +0200
+++ b/ldp.html	Sat Apr 27 11:24:36 2013 -0400
@@ -242,6 +242,11 @@
 requests and generates HTTP responses that conform to the rules defined in sections on <a href="#linked-data-platform-resources">LDPRs</a>
 and <a href="#linked-data-platform-containers">LDPCs</a></p>
 
+<div class="ldp-issue">
+	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/57">ISSUE-57</a></div>
+	How can a client determine that it is in communication with an LDP server?
+	</div>
+
 <p>A conforming <b>LDP Client</b> is an application program that generates HTTP 
 requests and processes HTTP responses that conform to the rules defined in sections on <a href="#linked-data-platform-resources">LDPRs</a>
 and <a href="#linked-data-platform-containers">LDPCs</a></p>
@@ -738,6 +743,11 @@
    a o:RealEstateHolding;
    o:value 300000.</pre>
 
+<div class="ldp-issue">
+	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/58">ISSUE-58</a></div>
+	Property for asserting that complete description of members is included in LDPC representation
+	</div>
+
 	<div id="ldpc-get_non-member_props" class="rule">5.1.2 Retrieving Only Non-member Properties
 	</div>
 	<em>This section is non-normative</em>
@@ -979,6 +989,11 @@
 		SHOULD use the <code>rdfs:member</code> predicate.
 	</div>
 	
+	<div class="ldp-issue">
+	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/51">ISSUE-51</a></div>
+	Linking from a Resource to its Containers (not the containers the resource is in)
+	</div>
+	
 	<div id="ldpc-5_2_4" class="rule">5.2.4 An LDPC MUST contain one triple containing the <code>ldp:membershipSubject</code>
 		predicate when the membership subject is not the LDPC itself.  
 		This triple's object provides clients with the LDPC's membership subject URI.
@@ -1056,6 +1071,12 @@
 		retrieve non-member resource properties via a different Request-URI than “<code>&lt;containerURL&gt;?non-member-properties</code>”,
 		MUST return a HTTP Redirection 3xx status code such as 301 (Moved Permanently) or 302 (Found).
 	</div>
+	
+	<div class="ldp-issue">
+	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/55">ISSUE-55</a></div>
+	Hypermedia as the Engine of Application State (HATEOAS) Compliance
+	</div>
+	
 	<div id="ldpc-5_3_3" class="rule">5.3.3 An LDPC server that does not support a request to retrieve the first
 		page resource representation from a known LDPC whose URL is “<code>&lt;containerURL&gt;</code>” by using
 		the Request-URI “<code>&lt;containerURL&gt;?firstPage</code>”, MUST return a HTTP status code 404 (Not
@@ -1129,6 +1150,11 @@
 		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">
+	<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>
@@ -1200,6 +1226,11 @@
 		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">
+	<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.
@@ -1232,6 +1263,11 @@
 	</div>
 	
 	<div class="ldp-issue">
+	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/59">ISSUE-59</a></div>
+	Recursive delete: reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
+	</div>	
+	
+	<div class="ldp-issue">
 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/28">ISSUE-28</a></div>
 	transaction/rollback when deleting resources from a LDPC.
 	note also that 5.6.2's reminder about 5.6.1 is only sensible if there is no transactional behavior in the recursive delete.