--- a/ldp.html Tue Sep 09 12:18:47 2014 -0400
+++ b/ldp.html Tue Sep 09 15:19:19 2014 -0400
@@ -896,29 +896,32 @@
<section id="ldprs-HTTP_GET">
<h2>HTTP GET</h2>
- <section id="ldprs-get-turtle"><h2 class="normal"><a title="LDP server">LDP servers</a> MUST offer a <code>text/turtle</code>
- representation of the requested <a title="Linked Data Platform RDF Source">LDP-RS</a> [[!turtle]].
+ <section id="ldprs-get-turtle"><h2 class="normal"><a title="LDP server">LDP servers</a> MUST
+ respond with a <code>text/turtle</code>
+ representation of the requested <a title="Linked Data Platform RDF Source">LDP-RS</a> [[!turtle]] when
+ the request includes an <code>Accept</code> header, unless content negotiation <em>requires</em> a different outcome.
+ For example, if the <code>Accept</code> header lists <code>text/turtle</code> as a media type with the
+ highest relative quality
+ factor (<code>q=</code> value), <a title="LDP server">LDP servers</a> must respond with <code>text/turtle</code>
+ even if multiple media types have the same (highest) relative quality factor.
</h2></section><!-- Was 4.3.3 / #ldpr-4_3_3 -->
<div class="atrisk" id="atrisk-ldpr-jsonld"><p class="atrisktext">Feature At Risk</p>
- <p>The LDP Working Group proposes incorporation of the following clause (changed from Should to Must):</p>
+ <p>The LDP Working Group proposes incorporation of the following clause requiring JSON-LD support.</p>
</div>
<section id="ldprs-get-jsonld"><h2 class="normal"><a title="LDP server">LDP servers</a> MUST
- offer a <code>application/ld+json</code>
- representation of the requested <a title="Linked Data Platform RDF Source">LDP-RS</a> [[!JSON-LD]].
+ respond with a <code>application/ld+json</code>
+ representation of the requested <a title="Linked Data Platform RDF Source">LDP-RS</a> [[!JSON-LD]]
+ when the request includes an <code>Accept</code> header, unless content negotiation
+ or <a href="#ldprs-get-turtle">Turtle support</a>
+ <em>requires</em> a different outcome.
</h2></section><!-- new -->
- <section id="ldprs-get-conneg"><h2 class="normal"><a title="LDP server">LDP servers</a> MUST provide a <code>text/turtle</code>
- representation of the requested <a title="Linked Data Platform RDF Source">LDP-RS</a> whenever HTTP content negotiation
- does not force another outcome and the <code>Accept</code> request header is present.
- In other words, if the server receives a <code>GET</code> request whose <code>Request-URI</code>
- identifies a <a title="">LDP-RS</a>, and <code>text/turtle</code> has the highest relative quality
- factor (<code>q=</code> value) in the
- Accept request header, then an <a title="">LDP server</a> has to respond with Turtle,
- even if other media types share the highest relative quality factor.
- If the <code>Accept</code> request header is absent,
- then <a title="LDP server">LDP servers</a> SHOULD respond with <code>text/turtle</code>.
- </h2></section><!-- Was 4.3.3 / #ldpr-4_3_3 -->
+ <section id="ldprs-get-conneg"><h2 class="normal"><a title="LDP server">LDP servers</a> SHOULD
+ respond with a <code>text/turtle</code>
+ representation of the requested <a title="Linked Data Platform RDF Source">LDP-RS</a> whenever
+ the <code>Accept</code> request header is absent.
+ </h2></section><!-- new -->
</section> <!-- ldprs-HTTP_GET -->
@@ -1662,14 +1665,13 @@
</h2></section><!-- Was 5.4.13 / #ldpc-5_4_13 -->
<div class="atrisk" id="atrisk-ldpc-jsonld"><p class="atrisktext">Feature At Risk</p>
- <p>The LDP Working Group proposes incorporation of the following clause (changed from Should to Must):</p>
+ <p>The LDP Working Group proposes incorporation of the following clause requiring JSON-LD support.</p>
</div>
<section id="ldpc-post-jsonld"><h2 class="normal"><a title="LDP server">LDP servers</a>
that allow creation of <a title="Linked Data Platform RDF Source">LDP-RSs</a> via POST MUST
allow clients to create new members by enclosing a request entity body with a
<code>Content-Type</code> request header whose value is <code>application/ld+json</code> [[!JSON-LD]].
</h2></section><!-- new -->
-
</section>
@@ -2600,8 +2602,9 @@
<ul>
</ul>
-<blockquote><em><a href="http://www.w3.org/TR/2014/WD-ldp-20140916">Last Call Working Draft 3</a></em></blockquote> -->
+<blockquote><em><a href="http://www.w3.org/TR/2014/WD-ldp-20140916">Last Call Working Draft 3</a></em></blockquote>
<ul>
+ <li>2014-09-09 - Re-factor Turtle/JSON-LD required words for readability and completeness (JA) </li>
<li>2014-09-08 - Add link to Best Practices now that it has been published (JA) </li>
<li>2014-09-08 - Indirect containers (at risk) (JA) </li>
<li>2014-09-08 - Should return Turtle if Accept is absent, JSON-LD required (at risk), clarify creates (JA) </li>
@@ -2613,7 +2616,7 @@
<li>2014-07-20 - Added test coverage utility to annotate spec with test cases covering them, to be removed before publishing (SS)</li>
</ul>
-<blockquote><em><a href="http://www.w3.org/TR/2014/CR-ldp-20140619">Candidate Recommendation Draft</a></em></blockquote> -->
+<blockquote><em><a href="http://www.w3.org/TR/2014/CR-ldp-20140619">Candidate Recommendation Draft</a></em></blockquote>
<ul>
<li>2014-07-28 - Clarified syntax used by clients to request specific interaction model (JA) </li>
<li>2014-06-16 - Updated examples in Prefer section to be in request/response format (SS) </li>