ldp.html
changeset 818 ce013b1a4a0a
parent 817 509560819f78
child 825 cbbf4e00e019
--- a/ldp.html	Wed Sep 10 11:05:23 2014 -0400
+++ b/ldp.html	Wed Sep 10 13:01:49 2014 -0400
@@ -900,21 +900,23 @@
 		respond with a Turtle
 		representation of the requested <a title="Linked Data Platform RDF Source">LDP-RS</a> when
 		the request includes an <code>Accept</code> header specifying <code>text/turtle</code>, 
-		unless content negotiation <em>requires</em> a different outcome 
+		unless HTTP content negotiation <em>requires</em> a different outcome 
 		[[!turtle]].
 		</h2>
 		<blockquote>
 		<em>Non-normative note: </em>
-		In other words, Turtle must be returned in the usual case clients would expect (client requests it and server
-		supports it) <em>as well as</em> cases where the client requests something, content negotiation results in a tie,
+		In other words, Turtle must be returned by <a title="LDP server">LDP servers</a> 
+		in the usual case clients would expect (client requests it) 
+		as well as cases where the client requests Turtle or other media type(s), content negotiation results in a tie,
 		and Turtle is one of the tying media types.
-		For example, if the <code>Accept</code> header lists <code>text/turtle</code> as a media type with the
+		For example, if the <code>Accept</code> header lists <code>text/turtle</code> as one of several media types 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.
+		factor (<code>q=</code> value), <a title="LDP server">LDP servers</a> must respond with Turtle.
+		HTTP servers in general are not required to resolve ties in this way, or to support Turtle at all, but
+		<a title="LDP server">LDP servers</a> are.
 		On the other hand, if Turtle is one of several requested media types,
 		but another media type the server supports has a higher relative quality factor,
-		normal content negotiation rules apply and the server would not respond with Turtle.
+		standard HTTP content negotiation rules apply and the server (LDP or not) would not respond with Turtle.
 		</blockquote>
 	</section><!-- Was 4.3.3 / #ldpr-4_3_3 -->