--- a/ldp.html Mon Feb 24 08:19:47 2014 -0500
+++ b/ldp.html Mon Feb 24 09:13:53 2014 -0500
@@ -629,14 +629,13 @@
<section id="ldpr-gen-pubclireqs"><h2 class="normal"><a title="LDP server">LDP servers</a> MUST
publish any constraints on <a title="LDP client">LDP clients’</a> ability to
create or update LDPRs, by adding a Link header with <code>rel='describedby'</code>
- [[!powder-dr]] to all responses to requests which fail due to violation of
+ [[!RFC5988]] to all responses to requests which fail due to violation of
those constraints. For example, a server that refuses resource creation
requests via HTTP PUT, POST, or PATCH would return this <code>Link</code> header on its
4xx responses to such requests.
The same <code>Link</code> header MAY be provided on other responses. LDP neither
- defines nor constrains the representation of the link's target resource;
- as stated in [[powder-dr]], the target might (or might not) be a POWDER
- document. Natural language constraint documents are therefore permitted,
+ defines nor constrains the representation of the link's target resource. Natural language
+ constraint documents are therefore permitted,
although machine-readable ones facilitate better client interactions.
</h2></section><!-- Was 4.2.13 / #ldpr-4_2_13 -->
@@ -735,8 +734,8 @@
<a title="LDP server">LDP servers</a> SHOULD provide a corresponding response body containing
information about which triples could not be
persisted.
- The format of the 4xx response body is not constrained by LDP.
- <!-- TODO: MUST respond with Link rel='describedBy' as in 4.2.13 -->
+ The format of the 4xx response body is not constrained by LDP. LDP servers
+ expose these application-specific constraints as described in <a href="#ldpr-general" class="sectionRef"></a>.
</h2></section><!-- Was 4.5.4 / #ldpr-4_5_4 -->
<section id="ldpr-put-create"><h2 class="normal"><a title="LDP server">LDP servers</a> MAY choose to allow the creation of new resources using HTTP <code>PUT</code>.
@@ -1378,9 +1377,8 @@
<section id="ldpc-post-mincontraints"><h2 class="normal"><a title="LDP server">LDP servers</a> SHOULD allow clients to create new resources without
requiring detailed knowledge of application-specific constraints.
- This is a consequence of the requirement to enable simple creation and modification of LDPRs.
- <!-- TODO: Consider reference to 4.2.13 to include Link rel='desribedBy' header for such constraints. Waiting for common creating-resources section.
- -->
+ This is a consequence of the requirement to enable simple creation and modification of LDPRs. LDP servers
+ expose these application-specific constraints as described in <a href="#ldpr-general" class="sectionRef"></a>.
</h2></section><!-- Was 5.4.9 / #ldpc-5_4_9 -->
<section id="ldpc-post-slug"><h2 class="normal"><a title="LDP server">LDP servers</a> MAY allow clients to suggest the URI for a resource
@@ -1398,8 +1396,8 @@
201-Created and URI indicated by <code>Location</code> response header), <a title="LDP server">LDP servers</a> MAY create an associated
<a title="Linked Data Platform RDF Source">LDP-RS</a>
to contain data about the newly created LDP-NR. If an LDPC server creates this associated <a title="Linked Data Platform RDF Source">LDP-RS</a> it MUST indicate
- its location on the HTTP response using the HTTP <code>Link</code> response header with link relation <code>meta</code>
- and <code>href</code> to be the URI of the meta-resource [[!RFC5988]].
+ its location on the HTTP response using the HTTP <code>Link</code> response header with link relation <code>describedBy</code>
+ and <code>href</code> to be the URI of the associated LDP-RS resource [[!RFC5988]].
</h2></section><!-- Was 5.4.12 / #ldpc-5_4_12 -->
<section id="ldpc-post-acceptposthdr"><h2 class="normal"><a title="LDP server">LDP servers</a> that support <code>POST</code> MUST
@@ -1531,20 +1529,14 @@
<p>This specification imposes the following new requirements on HTTP <code>OPTIONS</code> for LDPCs.
</p>
- <section id="ldpc-options-linkmetahdr"><h2 class="normal">When a LDPC creates a <a title="Linked Data Platform Non-RDF Source">LDP-NR</a> member (for example, one whose
- representation was HTTP <code>POST</code>ed to the LDPC and then referenced by a membership triple) it might create an associated <a title="Linked Data Platform RDF Source">LDP-RS</a> to contain data about the
- non-LDPR (see <a href="#ldpc-post-createbinlinkmetahdr">LDPC POST section</a>). For LDP-NRs that have this associated LDP-RS, an LDPC server MUST provide an HTTP <code>Link</code>
+ <section id="ldpc-options-linkmetahdr"><h2 class="normal">When a LDPC server creates a
+ <a title="Linked Data Platform Non-RDF Source">LDP-NR</a> member (for example, one whose
+ representation was HTTP <code>POST</code>ed to the LDPC and then referenced by a membership triple)
+ the LDP server might create an associated <a title="Linked Data Platform RDF Source">LDP-RS</a>
+ to contain data about the non-LDPR (see <a href="#ldpc-post-createbinlinkmetahdr">LDPC POST section</a>).
+ For LDP-NRs that have this associated LDP-RS, an LDPC server MUST provide an HTTP <code>Link</code>
header whose target URI is the associated LDP-RS, and whose link relation type is
- <code>meta</code> [[!RFC5988]].
-
- <!-- TODO: Consider some improvement to #ldpc-options-linkmetahdr
-
- Does a LDPC create a non-LDPR? or does and LDPC server do this?
- What is "it" in the first sentence?
- Adding a Request-URI clause to the last sentence may help clarify a couple things.
- Metadata resource definition?
- -->
-
+ <code>describedBy</code> [[!RFC5988]].
</h2></section><!-- Was 5.9.2 / #ldpc-5_9_2 -->
</section> <!-- h2 -->
@@ -2090,6 +2082,7 @@
<!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130930/">Candidate Recommendation Draft</a></em></blockquote> wah -->
<!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130730/">Last Call Draft</a></em></blockquote> -->
<ul>
+ <li>2014-02-24 - Corrected rel=meta to be rel=describedBy (SS) </li>
<li>2014-02-24 - Adjusted term membership triples and membership predicate (SS) </li>
<li>2014-02-24 - Removed 6.3.1 LDPC GET requirement and put in general clause (SS) </li>
<li>2014-02-20 - Changed LDPC SHOULD NOT put (6.5.1) to be about containment (SS) </li>