--- a/ldp.html Sat Feb 08 14:43:27 2014 -0500
+++ b/ldp.html Sat Feb 08 15:36:26 2014 -0500
@@ -462,7 +462,6 @@
<section id='conformance'>
-<p>LDP uses the term <b><dfn>informative</dfn></b> as a synonym for non-normative.</p>
<p>The status of the sections of Linked Data Platform 1.0 (this document) is as follows:</p>
<ul>
<li>1. Introduction: <b>non-normative</b></li>
@@ -729,9 +728,14 @@
<section id="ldpr-HTTP_PUT">
<h2>HTTP PUT</h2>
- <p>This specification imposes the following new requirements on HTTP <code>PUT</code> for LDPRs
- only when the LDPR supports that method. This specification does not impose any
- new requirement to support that method, and [[!HTTP11]] makes it optional.
+ <p>
+ Per [HTTP11], this HTTP method is optional and
+ this specification does not require <a title="LDP server">LDP servers</a> to support it.
+ When a LDP server chooses to support this method,
+ this specification imposes the following new requirements for LDPRs.
+ </p>
+
+ <p>
Any server-imposed constraints on LDPR creation or update
<a href="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
</p>
@@ -798,9 +802,13 @@
<section id="ldpr-HTTP_DELETE">
<h2>HTTP DELETE</h2>
- <p>This specification imposes the following new requirements on HTTP <code>DELETE</code> for LDPRs
- only when the LDPR supports that method. This specification does not impose any
- new requirement to support that method, and [[!HTTP11]] makes it optional.</p>
+ <p>
+ Per [HTTP11], this HTTP method is optional and
+ this specification does not require <a title="LDP server">LDP servers</a> to support it.
+ When a LDP server chooses to support this method,
+ this specification imposes the following new requirements for LDPRs.
+ </p>
+
<p>Additional requirements on HTTP <code>DELETE</code> of LDPRs within containers can be found in
<a href="#ldpc-HTTP_DELETE" class="sectionRef"></a>.
</p>
@@ -818,9 +826,14 @@
<section id="ldpr-HTTP_PATCH">
<h2>HTTP PATCH</h2>
- <p>This specification imposes the following new requirements on HTTP <code>PATCH</code> for LDPRs
- only when the LDPR supports that method. This specification does not impose any
- new requirement to support that method, and [[!HTTP11]] makes it optional.
+ <p>
+ Per [HTTP11], this HTTP method is optional and
+ this specification does not require <a title="LDP server">LDP servers</a> to support it.
+ When a LDP server chooses to support this method,
+ this specification imposes the following new requirements for LDPRs.
+ </p>
+
+ <p>
Any server-imposed constraints on LDPR creation or update
<a href="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
</p>
@@ -1774,9 +1787,14 @@
<section id="ldpc-HTTP_POST">
<h2>HTTP POST</h2>
- <p>This specification imposes the following new requirements on HTTP <code>POST</code> for LDPCs
- 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>
+ Per [HTTP11], this HTTP method is optional and
+ this specification does not require <a title="LDP server">LDP servers</a> to support it.
+ When a LDP server chooses to support this method,
+ this specification imposes the following new requirements for LDPCs.
+ </p>
+
+ <p>
Any server-imposed constraints on creation or update
<a href="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
</p>
@@ -1866,12 +1884,12 @@
SHOULD NOT re-use URIs.
</h2></section><!-- Was 5.4.11 / #ldpc-5_4_11 -->
- <section id="ldpc-post-createbinlinkmetahdr"><h2 class="normal">Upon successful creation of a non-RDF
- <a title="Linked Data Platform Binary Resource">(LDP-BR)</a> and therefore non-LDPR member (HTTP status code of
+ <section id="ldpc-post-createbinlinkmetahdr"><h2 class="normal">Upon successful creation of a
+ <a title="Linked Data Platform Binary Resource">LDP-BR</a> (HTTP status code of
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 Resource">LDP-RR</a>
- to contain data about the created resource. If an LDPC server creates this associated <a title="Linked Data Platform RDF Resource">LDP-RR</a> it MUST indicate
- its location on the HTTP response using the HTTP response header <code>Link</code> and relationship type <code>meta</code>
+ to contain data about the newly created LDP-BR. If an LDPC server creates this associated <a title="Linked Data Platform RDF Resource">LDP-RR</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]].
</h2></section><!-- Was 5.4.12 / #ldpc-5_4_12 -->
@@ -1918,9 +1936,14 @@
<section id="ldpc-HTTP_PUT">
<h2>HTTP PUT</h2>
- <p>This specification imposes the following new requirements on HTTP <code>PUT</code> for LDPCs
- 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>
+ Per [HTTP11], this HTTP method is optional and
+ this specification does not require <a title="LDP server">LDP servers</a> to support it.
+ When a LDP server chooses to support this method,
+ this specification imposes the following new requirements for LDPCs.
+ </p>
+
+ <p>
Any server-imposed constraints on creation or update
<a href="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
</p>
@@ -1939,9 +1962,12 @@
<section id="ldpc-HTTP_DELETE">
<h2>HTTP DELETE</h2>
- <p>This specification imposes the following new requirements on HTTP <code>DELETE</code> for LDPRs and LDPCs
- only when a LDPC supports that method. This specification does not impose any
- new requirement to support that method, and [[!HTTP11]] makes it optional.</p>
+ <p>
+ Per [HTTP11], this HTTP method is optional and
+ this specification does not require <a title="LDP server">LDP servers</a> to support it.
+ When a LDP server chooses to support this method,
+ this specification imposes the following new requirements for LDPCs.
+ </p>
<section id="ldpc-del-contremovesmbrtriple"><h2 class="normal">
When a LDPC contained resource is deleted, the LDPC server MUST also remove it from
@@ -1990,9 +2016,14 @@
<section id="ldpc-HTTP_PATCH">
<h2>HTTP PATCH</h2>
- <p>This specification imposes the following new requirements on HTTP <code>PATCH</code> for LDPCs
- only when a LDPC supports that method. This specification does not impose any
- new requirement to support that method, and [[!HTTP11]] makes it optional.
+ <p>
+ Per [HTTP11], this HTTP method is optional and
+ this specification does not require <a title="LDP server">LDP servers</a> to support it.
+ When a LDP server chooses to support this method,
+ this specification imposes the following new requirements for LDPCs.
+ </p>
+
+ <p>
Any server-imposed constraints on LDPR creation or update
<a href="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
</p>
@@ -2586,6 +2617,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-08 - Put final stake in heart of 'informative' (waves to Sandro), update boilerplate for readability per Arnaud (JA)</li>
<li>2014-02-08 - ACTION-132: Use Prefer in place of non-member properties resource (JA)</li>
<li>2014-02-08 - Add Prefer header examples, define new URIs from -126 in ttl, tweak acks per Arnaud email (JA)</li>
<li>2014-02-07 - ACTION-126: Add Prefer header (JA)</li>