Fixed various link checker bugs
authorsspeiche
Thu, 25 Jul 2013 08:23:01 -0400
changeset 237 6871b9ac5339
parent 236 add97cfc2550
child 238 59bacb9c7b5b
Fixed various link checker bugs
drafts/ldp/Overview.html
ldp.html
--- a/drafts/ldp/Overview.html	Wed Jul 24 16:10:19 2013 -0400
+++ b/drafts/ldp/Overview.html	Thu Jul 25 08:23:01 2013 -0400
@@ -250,7 +250,7 @@
 </dd>
 <dd class="p-author h-card vcard" rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a class="u-url url p-name fn" rel="foaf:homepage" property="foaf:name" content="John Arwe" href="https://www.ibm.com/developerworks/mydeveloperworks/groups/service/html/allcommunities?userid=120000CAW7">John Arwe</a>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://ibm.com/">IBM Corporation</a></span>
 </dd>
-<dd class="p-author h-card vcard" rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a class="u-url url p-name fn" rel="foaf:homepage" property="foaf:name" content="Ashok Malhotra" href="[email protected]">Ashok Malhotra</a>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://www.oracle.com">Oracle Corporation</a></span>
+<dd class="p-author h-card vcard" rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a class="u-url url p-name fn" rel="foaf:homepage" property="foaf:name" content="Ashok Malhotra" href="mailto:[email protected]">Ashok Malhotra</a>, <a rel="foaf:workplaceHomepage" class="p-org org h-org h-card" href="http://www.oracle.com">Oracle Corporation</a></span>
 </dd>
 
     
@@ -1051,16 +1051,16 @@
 		whose object is the HTTP <code>Request-URI</code> of an inlined resource [<cite><a class="bibref" href="#bib-HTTP11">HTTP11</a></cite>].
 	</div>
 
-	<div id="ldpc-4_11_3_3" class="rule">4.11.3.3 <abbr title="Linked Data Platform Resource">LDPR</abbr> clients <em class="rfc2119" title="SHOULD">SHOULD</em> avoid making HTTP <code>GET</code> requests
+	<div id="ldpr-4_11_3_3" class="rule">4.11.3.3 <abbr title="Linked Data Platform Resource">LDPR</abbr> clients <em class="rfc2119" title="SHOULD">SHOULD</em> avoid making HTTP <code>GET</code> requests
 		against any resource whose HTTP <code>Request-URI</code> is the object of a triple of the form 
-		described in <a href="#ldpc-4_11_3_2">section 4.11.3.2</a>, unless there are application-specific
+		described in <a href="#ldpr-4_11_3_2">section 4.11.3.2</a>, unless there are application-specific
 		reasons for doing so.  Clients should note that by the time the representation is received, the actual state
 		of any inlined resource(s) may have changed due to subsequent requests.
 	</div>
 
-	<div id="ldpc-4_11_3_4" class="rule">4.11.3.4 <abbr title="Linked Data Platform Resource">LDPR</abbr> clients <em class="rfc2119" title="MUST NOT">MUST NOT</em> assume that <abbr title="Linked Data Platform Resource">LDPR</abbr> representations
+	<div id="ldpr-4_11_3_4" class="rule">4.11.3.4 <abbr title="Linked Data Platform Resource">LDPR</abbr> clients <em class="rfc2119" title="MUST NOT">MUST NOT</em> assume that <abbr title="Linked Data Platform Resource">LDPR</abbr> representations
 		lacking a <code>ldp:Page</code> resource or lacking the triple
-		described in <a href="#ldpc-4_11_3_2">section 4.11.3.2</a> contain all the triples for any resource(s)
+		described in <a href="#ldpr-4_11_3_2">section 4.11.3.2</a> contain all the triples for any resource(s)
 		listed in the representation whose HTTP <code>Request-URI</code> differs from 
 		the HTTP <code>Request-URI</code> used by the client.  
 		The representation might in fact contain all such triples, or some
@@ -1758,7 +1758,7 @@
 <h3 id="ldpc-HTTP_HEAD"><span class="secno">5.7 </span>HTTP HEAD</h3>
 	<p>Note that certain LDP mechanisms, such as paging, rely on HTTP headers, and HTTP generally requires that
 		<code>HEAD</code> responses include the same headers as <code>GET</code> responses. Also <abbr title="Linked Data Platform Container">LDPC</abbr> servers must also include HTTP headers
-		on response to <code>OPTIONS</code>, see <a href="#ldpr-4_7_2">4.7.2</a>.
+		on response to <code>OPTIONS</code>, see <a href="#ldpr-HTTP_OPTIONS" class="sectionRef"></a>.
 		Thus, implementers supporting <code>HEAD</code> should also carefully read the
 		<a href="#ldpc-HTTP_GET" class="sectionRef">section 5.3 </a> and <a href="#ldpc-HTTP_OPTIONS" class="sectionRef">section 5.9 </a>.</p>
 </section>
--- a/ldp.html	Wed Jul 24 16:10:19 2013 -0400
+++ b/ldp.html	Thu Jul 25 08:23:01 2013 -0400
@@ -75,7 +75,7 @@
                 company: "IBM Corporation", companyURL: "http://ibm.com/" },
               { name: "John Arwe", url: "https://www.ibm.com/developerworks/mydeveloperworks/groups/service/html/allcommunities?userid=120000CAW7",
                 company: "IBM Corporation", companyURL: "http://ibm.com/" },
-			  {name: "Ashok Malhotra", url: "[email protected]",
+			  {name: "Ashok Malhotra", url: "mailto:[email protected]",
 			    company: "Oracle Corporation", companyURL: "http://www.oracle.com" },
           ],
 
@@ -877,16 +877,16 @@
 		whose object is the HTTP <code>Request-URI</code> of an inlined resource [[!HTTP11]].
 	</div>
 
-	<div id="ldpc-4_11_3_3" class="rule">4.11.3.3 LDPR clients SHOULD avoid making HTTP <code>GET</code> requests
+	<div id="ldpr-4_11_3_3" class="rule">4.11.3.3 LDPR clients SHOULD avoid making HTTP <code>GET</code> requests
 		against any resource whose HTTP <code>Request-URI</code> is the object of a triple of the form 
-		described in <a href="#ldpc-4_11_3_2">section 4.11.3.2</a>, unless there are application-specific
+		described in <a href="#ldpr-4_11_3_2">section 4.11.3.2</a>, unless there are application-specific
 		reasons for doing so.  Clients should note that by the time the representation is received, the actual state
 		of any inlined resource(s) may have changed due to subsequent requests.
 	</div>
 
-	<div id="ldpc-4_11_3_4" class="rule">4.11.3.4 LDPR clients MUST NOT assume that LDPR representations
+	<div id="ldpr-4_11_3_4" class="rule">4.11.3.4 LDPR clients MUST NOT assume that LDPR representations
 		lacking a <code>ldp:Page</code> resource or lacking the triple
-		described in <a href="#ldpc-4_11_3_2">section 4.11.3.2</a> contain all the triples for any resource(s)
+		described in <a href="#ldpr-4_11_3_2">section 4.11.3.2</a> contain all the triples for any resource(s)
 		listed in the representation whose HTTP <code>Request-URI</code> differs from 
 		the HTTP <code>Request-URI</code> used by the client.  
 		The representation might in fact contain all such triples, or some
@@ -1587,7 +1587,7 @@
 <h2 id="ldpc-HTTP_HEAD">HTTP HEAD</h2>
 	<p>Note that certain LDP mechanisms, such as paging, rely on HTTP headers, and HTTP generally requires that
 		<code>HEAD</code> responses include the same headers as <code>GET</code> responses. Also LDPC servers must also include HTTP headers
-		on response to <code>OPTIONS</code>, see <a href="#ldpr-4_7_2">4.7.2</a>.
+		on response to <code>OPTIONS</code>, see <a href="#ldpr-HTTP_OPTIONS" class="sectionRef"></a>.
 		Thus, implementers supporting <code>HEAD</code> should also carefully read the
 		<a href="#ldpc-HTTP_GET" class="sectionRef"></a> and <a href="#ldpc-HTTP_OPTIONS" class="sectionRef"></a>.</p>
 </section>