--- a/ldp.html Mon Jul 08 13:04:30 2013 +0100
+++ b/ldp.html Mon Jul 08 08:30:31 2013 -0400
@@ -271,11 +271,6 @@
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-open">
- <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>.
@@ -405,6 +400,26 @@
that can modify resources. For some server applications, excessive
constraints on modification of resources may be required.
</div>
+
+<div class="ldp-issue-pending">
+ <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>
+
+ <div id="ldpr-4_1_12" class="rule">4.1.12 LDPR servers
+ MUST advertise their LDP support by exposing a HTTP <code>Link</code> header
+ with a target URI of <code>http://www.w3.org/ns/ldp/Resource</code>, and
+ a link relation type of <code>type</code> (that is, <code>rel="type"</code>)
+ in all responses to requests made
+ to the resource's HTTP <code>request-URI</code>. This is notionally equivalent to the
+ presence of a <code>< subject-URI, rdf:type , ldp:Resource ></code> triple in the resource.
+ The HTTP <code>Link</code> header is the method by which servers assert their support for the LDP spec in a way
+ that clients can introspect dynamically at run-time. Conservative clients should note that
+ a server can host a mixture of LDPRs and other resources, and therefore there is no implication
+ that LDP support advertised on one HTTP <code>request-URI</code> means that other
+ 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>
</section>
<section>