ldp.html
changeset 152 938e7d21cc10
parent 151 9c3a6a3efd89
child 158 8af0b25f2748
--- a/ldp.html	Mon Jul 08 08:47:03 2013 -0400
+++ b/ldp.html	Mon Jul 08 08:59:47 2013 -0400
@@ -389,7 +389,7 @@
 	<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-open">
+	<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?
 	</div>
@@ -425,6 +425,18 @@
 		resources on the same server are also LDPRs.  Each HTTP <code>request-URI</code> needs to be 
 		individually introspected by a conservative client, in the absence of outside information.
 	</div>
+<div class="ldp-issue-pending">
+	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/78">ISSUE-78</a></div>
+	inferencing levels
+	</div>
+
+	<div id="ldpr-4_1_13" class="rule">4.1.13 LDPR servers
+		MUST NOT require LDP clients to implement inferencing in order to recognize the subset
+		of content defined by LDP.  Other specifications built on top of LDP MAY require clients
+		to implement inferencing.  The practical implication is that all content defined by LDP
+		must be explicitly represented. 
+	</div>
+
 </section>
 
 <section>