Align usage of Link: rel= to not use single quotes per RFC5988
authorsspeiche
Mon, 26 Jan 2015 10:42:10 -0500
changeset 935 4c9e4a9dc2e8
parent 922 cb6efb8c91bf
child 936 391bf26afb13
Align usage of Link: rel= to not use single quotes per RFC5988
ldp-paging.html
ldp.html
--- a/ldp-paging.html	Thu Dec 11 08:44:40 2014 -0500
+++ b/ldp-paging.html	Mon Jan 26 10:42:10 2015 -0500
@@ -390,14 +390,14 @@
 	redirects to (<code>303</code> response) in response
 	to a retrieval request for the <a>paged resource</a>'s URI.
 	Syntactically, a
-	HTTP <code>Link &lt;<var>P<sub>1</sub></var>&gt;; rel='first'</code>
+	HTTP <code>Link &lt;<var>P<sub>1</sub></var>&gt;; rel="first"</code>
 	header [[!RFC5988]].
 	<p></p></dd>
 	
 	<dt><dfn>next page link</dfn></dt>
 	<dd>A link to the next <a title="In-sequence page resource">in-sequence page resource</a> 
 	of a <a>page sequence</a>.  Syntactically, a
-	HTTP <code>Link &lt;<var>P<sub>i</sub></var>&gt;; rel='next'</code>
+	HTTP <code>Link &lt;<var>P<sub>i</sub></var>&gt;; rel="next"</code>
 	header [[!RFC5988]] where 
 	the context URI identifies some <var>P<sub>i=1 (first)...n-1 (next to last)</sub></var> and
 	the target URI identifies <var>P<sub>i+1</sub></var>.
@@ -408,14 +408,14 @@
 	of a <a>page sequence</a>.  
 	The last page is the page that terminates a <a>forward traversal</a>, because it contains no <a>next page link</a>.
 	Syntactically, a
-	HTTP <code>Link &lt;<var>P<sub>n</sub></var>&gt;; rel='last'</code>
+	HTTP <code>Link &lt;<var>P<sub>n</sub></var>&gt;; rel="last"</code>
 	header [[!RFC5988]].
 	<p></p></dd>
 	
 	<dt><dfn>previous page link</dfn></dt>
 	<dd>A link to the previous <a title="In-sequence page resource">in-sequence page resource</a>
 	of a <a>page sequence</a>  Syntactically, a
-	HTTP <code>Link &lt;<var>P<sub>i</sub></var>&gt;; rel='prev'</code>
+	HTTP <code>Link &lt;<var>P<sub>i</sub></var>&gt;; rel="prev"</code>
 	header [[!RFC5988]] where 
 	the context URI identifies some <var>P<sub>i=2...n (last)</sub></var> and
 	the target URI identifies <var>P<sub>i-1</sub></var>.
@@ -658,8 +658,8 @@
 ETag: "_87e52ce291112"
 Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type",
       &lt;http://www.w3.org/ns/ldp#Page&gt;; rel="type"
-Link: &lt;http://example.org/customer-relations?p=2&gt;; rel='next'
-Link: &lt;http://example.org/customer-relations&gt;; rel='canonical'; etag="customer-relations-v1"
+Link: &lt;http://example.org/customer-relations?p=2&gt;; rel="next"
+Link: &lt;http://example.org/customer-relations&gt;; rel="canonical"; etag="customer-relations-v1"
 Allow: GET,OPTIONS,HEAD
 
 @prefix rdf: &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt;.
@@ -698,7 +698,7 @@
 	</p>
 	<ul>
 	<li>
-		The <code>Link: &lt;http://example.org/customer-relations&gt;; rel='canonical'</code>
+		The <code>Link: &lt;http://example.org/customer-relations&gt;; rel="canonical"</code>
 		response header tells the client which resource <code>&lt;http://example.org/customer-relations?page1&gt;</code>
 		is a page of.  The <code>etag="customer-relations-v1"</code> parameter value gives the client a way to know,
 		during its page traversal, whether or not the canonical <a>paged resource</a> has changed; not all
@@ -712,7 +712,7 @@
 		was generated by the server.
 	</li>
 	<li>
-		The <code>Link: &lt;http://example.org/customer-relations?p=2&gt;; rel='next'</code>
+		The <code>Link: &lt;http://example.org/customer-relations?p=2&gt;; rel="next"</code>
 		response header tells the client that at least one more <a>in-sequence page resource</a> exists,
 		and how to retrieve its representation.  The next page link's target URI is 
 		defined by the server and is not constrained by this specification.
@@ -740,7 +740,7 @@
 ETag: "8_7e52ce291112"
 Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type",
       &lt;http://www.w3.org/ns/ldp#Page&gt;; rel="type"
-Link: &lt;http://example.org/customer-relations&gt;; rel='canonical'; etag="customer-relations-v1"
+Link: &lt;http://example.org/customer-relations&gt;; rel="canonical"; etag="customer-relations-v1"
 Allow: GET,OPTIONS,HEAD
 
 @prefix rdf: &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt;.
@@ -780,7 +780,7 @@
 		was generated by the server.
 	</li>
 	<li>
-		The absence of a <code>Link: &lt;http://example.org/customer-relations?p=2&gt;; rel='next'</code>
+		The absence of a <code>Link: &lt;http://example.org/customer-relations?p=2&gt;; rel="next"</code>
 		response header tells the client that no more <a>in-sequence page resource</a>s existed in this <a>paged resource</a>
 		at the time the response was generated; repeating the request might result in a representation with links to more pages,
 		if other processes are updating the customer relations data.
@@ -814,24 +814,24 @@
 	<li>
 		The <a title="first page link">first page</a>'s <a href="#ldpp-ex-paging-303-resp2">response message</a> might also have the following links:
 <pre class="example">
-Link: &lt;&gt;; rel='first'
-Link: &lt;http://example.org/customer-relations?p=2&gt;; rel='last'
+Link: &lt;&gt;; rel="first"
+Link: &lt;http://example.org/customer-relations?p=2&gt;; rel="last"
 </pre>
 	</li>
 	<li>
 		Any <a>in-sequence page resource</a>'s response message, including the <a title="first page link">first page</a> and the <a title="last page link">last page</a>,
 		might also have the following links:
 <pre class="example">
-Link: &lt;http://example.org/customer-relations?page1&gt;; rel='first'
-Link: &lt;http://example.org/customer-relations?p=2&gt;; rel='last'
+Link: &lt;http://example.org/customer-relations?page1&gt;; rel="first"
+Link: &lt;http://example.org/customer-relations?p=2&gt;; rel="last"
 </pre>
 	</li>
 	<li>
 		The <a title="last page link">last page</a>'s <a href="#ldpp-ex-paging-303-resp3">response message</a> might also have the following links:
 <pre class="example">
-Link: &lt;http://example.org/customer-relations?page1&gt;; rel='first'
-Link: &lt;http://example.org/customer-relations?page1&gt;; rel='prev'
-Link: &lt;&gt;; rel='last'
+Link: &lt;http://example.org/customer-relations?page1&gt;; rel="first"
+Link: &lt;http://example.org/customer-relations?page1&gt;; rel="prev"
+Link: &lt;&gt;; rel="last"
 </pre>
 	</li>
 	</ul>
@@ -1196,12 +1196,12 @@
 		link extension parameters include the parameter name <code>etag</code>
 		and a corresponding parameter value identical to the ETag [[!RFC7232]]
 		of the <a>paged resource</a>.
-		For example: <code>Link: &lt;http://example.org/customer-relations&gt;; rel='canonical'; etag="customer-relations-v1"</code>
+		For example: <code>Link: &lt;http://example.org/customer-relations&gt;; rel="canonical"; etag="customer-relations-v1"</code>
 		</h2>
 		<blockquote><em>Non-normative note:</em> 
-		If the <code>rel='canonical'; etag="..."</code> value changes as the client retrieves pages, 
-		for example the value accompanying the first page's representation is <code>rel='canonical'; etag="v1"</code> 
-		and the value accompanying the second page's representation is <code>rel='canonical'; etag="v2"</code>,
+		If the <code>rel="canonical"; etag="..."</code> value changes as the client retrieves pages, 
+		for example the value accompanying the first page's representation is <code>rel="canonical"; etag="v1"</code> 
+		and the value accompanying the second page's representation is <code>rel="canonical"; etag="v2"</code>,
 		the client can detect that the <a>paged resource</a>'s state has changed.
 		Some clients will ignore such changes, but others may choose to react to them, for example by restarting the traversal.
 		</blockquote>
@@ -1296,7 +1296,7 @@
 			indicate that they have abandoned a
 			sequence by responding with at <code>410 Gone</code> to HTTP requests to any of the 
 			<a title="in-sequence page resource">in-sequence page resources</a> with appropriate 
-			paging link response headers, for example, rel='first'.
+			paging link response headers, for example, rel="first".
 		</h2></section><!-- #ldpr-pagingGET-abandon-pageseq -->
 
 		<section id="ldpr-units-triple-count"><h2 class="normal">
@@ -1499,9 +1499,9 @@
 ETag: "_87e52ff291112"
 Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type",
       &lt;http://www.w3.org/ns/ldp#Page&gt;; rel="type"
-Link: &lt;http://example.org/netWorth/nw1/assetContainer/?p=2&gt;; rel='next'
-Link: &lt;http://example.org/netWorth/nw1/assetContainer/&gt;; rel='canonical'; etag="v1"
-Link: &lt;http://example.org/netWorth/nw1/assetContainer/sortedSequence/&gt;; rel='http://www.w3.org/ns/ldp#pageSequence'
+Link: &lt;http://example.org/netWorth/nw1/assetContainer/?p=2&gt;; rel="next"
+Link: &lt;http://example.org/netWorth/nw1/assetContainer/&gt;; rel="canonical"; etag="v1"
+Link: &lt;http://example.org/netWorth/nw1/assetContainer/sortedSequence/&gt;; rel="http://www.w3.org/ns/ldp#pageSequence"
 Allow: GET,OPTIONS,HEAD
 
 # The following is the ordered representation of
@@ -1547,7 +1547,7 @@
 	</p>
 	<ul>
 	<li>
-		A <code>Link rel='http://www.w3.org/ns/ldp#pageSequence'</code> response header has been
+		A <code>Link: rel="http://www.w3.org/ns/ldp#pageSequence"</code> response header has been
 		added, allowing the client to where to find information about the page sequence;
 		its content includes a <code>ldp:pageSortCriteria</code> triple, 
 		allowing the client to know what sort criteria the server used when allocating members
@@ -1573,7 +1573,7 @@
 	</ul>
 	
 	<p>
-		When the client retrieves the second page by following the <code>rel='next'</code> link,
+		When the client retrieves the second page by following the <code>rel="next"</code> link,
 		its representation might be:
 	</p>
 
@@ -1584,9 +1584,9 @@
 ETag: "_87e52ff291112"
 Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type",
       &lt;http://www.w3.org/ns/ldp#Page&gt;; rel="type"
-Link: &lt;http://example.org/netWorth/nw1/assetContainer/?pageSortOrder&gt;; rel='prev'
-Link: &lt;http://example.org/netWorth/nw1/assetContainer/&gt;; rel='canonical'; etag="v1"
-Link: &lt;http://example.org/netWorth/nw1/assetContainer/sortedSequence/&gt;; rel='http://www.w3.org/ns/ldp#pageSequence'
+Link: &lt;http://example.org/netWorth/nw1/assetContainer/?pageSortOrder&gt;; rel="prev"
+Link: &lt;http://example.org/netWorth/nw1/assetContainer/&gt;; rel="canonical"; etag="v1"
+Link: &lt;http://example.org/netWorth/nw1/assetContainer/sortedSequence/&gt;; rel="http://www.w3.org/ns/ldp#pageSequence"
 Allow: GET,OPTIONS,HEAD
 
 # The following is the ordered representation of
@@ -1607,7 +1607,7 @@
 	
 	<ul>
 	<li>
-		The same <code>Link rel='http://www.w3.org/ns/ldp#pageSequence'</code> response header is present,
+		The same <code>Link: rel="http://www.w3.org/ns/ldp#pageSequence"</code> response header is present,
 		allowing the client to know what page sequence, and hence what sort criteria, the server used.
 	</li>
 	<li>
@@ -1809,14 +1809,14 @@
 		In this case, the <a>next page link</a> in the first page might be:
 	</p>
 	<pre class="example" id="paging-no-session-state1">
-		Link: &lt;http://example.org/customer-relations?resumeafter=JoanRSmith&gt;; rel='next'
+		Link: &lt;http://example.org/customer-relations?resumeafter=JoanRSmith&gt;; rel="next"
 	</pre>
 	<p>
 		If the server also supports <a>backward traversal</a>, then the second page's 
 		<a>previous page link</a> might be:
 	</p>
 	<pre class="example" id="paging-no-session-state2">
-		Link: &lt;http://example.org/customer-relations?resumebefore=GlenWSmith&gt;; rel='next'
+		Link: &lt;http://example.org/customer-relations?resumebefore=GlenWSmith&gt;; rel="next"
 	</pre>
 	<p>
 		Keep in mind that this is an exemplary server implementation decision; it is not prescribed by 
@@ -1871,6 +1871,16 @@
 public draft it has been changed from.
 </p>  -->
 
+<!-- 
+<h2>Detailed history</h2> -->
+
+<!-- <blockquote><em><a href="http://www.w3.org/TR/2014/CR-ldp-paging-20141216/">Candidate Recommendation Draft</a></em></blockquote> wah -->
+<!-- 
+<ul>
+	<li>2015-01-26 - Align usage of Link: rel= to not use single quotes per RFC5988 (SS)</li>
+</ul>
+-->
+
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-paging-20140930/">Candidate Recommendation Draft</a></em></blockquote> wah -->
 <!-- 
 <ul>
--- a/ldp.html	Thu Dec 11 08:44:40 2014 -0500
+++ b/ldp.html	Mon Jan 26 10:42:10 2015 -0500
@@ -567,7 +567,7 @@
 		exposing LDPRs 
 		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>)
+		a link relation type of <code>type</code> (that is, <code>rel="type"</code>)
 		in all responses to requests made 
 		to an LDPR's HTTP <code>Request-URI</code> [[!RFC5988]]. 
 	</h2></section><!-- Was 4.2.10 / #ldpr-4_2_10 -->
@@ -944,7 +944,7 @@
 	<section id="ldpnr-type"><h2 class="normal"><a title="LDP server">LDP servers</a> exposing an <a title="Linked Data Platform Non-RDF Source">LDP Non-RDF Source</a> 
 		MAY advertise this by exposing a HTTP <code>Link</code> header
 		with a target URI of <code>http://www.w3.org/ns/ldp#NonRDFSource</code>, and
-		a link relation type of <code>type</code> (that is, <code>rel='type'</code>)
+		a link relation type of <code>type</code> (that is, <code>rel="type"</code>)
 		in responses to requests made 
 		to the LDP-NR's HTTP <code>Request-URI</code> [[!RFC5988]].  
 	</h2></section>
@@ -1495,15 +1495,15 @@
 		MUST advertise their LDP support by exposing a HTTP <code>Link</code> header
 		with a target URI matching the type of container (see below) the
 		server supports, and
-		a link relation type of <code>type</code> (that is, <code>rel='type'</code>)
+		a link relation type of <code>type</code> (that is, <code>rel="type"</code>)
 		in all responses to requests made 
 		to the LDPC's HTTP <code>Request-URI</code>. 
-		<a title="LDP server">LDP servers</a> MAY provide additional HTTP <code>Link: rel='type'</code> headers.
+		<a title="LDP server">LDP servers</a> MAY provide additional HTTP <code>Link: rel="type"</code> headers.
 		The <a href="#ldpr-gen-linktypehdr">notes on the corresponding LDPR constraint</a> apply
 		equally to LDPCs.
 	</h2>
 	<blockquote>
-	<p>Valid container type URIs for <code>rel='type'</code> defined by this document are:
+	<p>Valid container type URIs for <code>rel="type"</code> defined by this document are:
 	<ul>
 	<li><code>http://www.w3.org/ns/ldp#BasicContainer</code> - for <a href="#ldpbc">LDP Basic Containers</a></li>
 	<li><code>http://www.w3.org/ns/ldp#DirectContainer</code> - for <a href="#ldpdc">LDP Direct Containers</a></li>
@@ -2523,6 +2523,15 @@
 
 <!-- 
 <h2>Detailed history</h2> -->
+<!-- <blockquote><em><a href="http://www.w3.org/TR/2014/PR-ldp-20141216/">Proposed Recommendation Draft</a></em></blockquote> -->
+<!-- 
+<ul>
+	<li>2015-01-26 - Align usage of Link: rel= to not use single quotes per RFC5988 (SS)</li>
+</ul>
+-->
+
+<!-- 
+<h2>Detailed history</h2> -->
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2014/CR-ldp-20140619/">Candidate Recommendation Draft</a></em></blockquote> -->
 <!-- 
 <ul>