ldp.html
changeset 237 6871b9ac5339
parent 235 b93936428fcd
child 238 59bacb9c7b5b
equal deleted inserted replaced
236:add97cfc2550 237:6871b9ac5339
    73           editors:  [
    73           editors:  [
    74               { name: "Steve Speicher", url: "http://stevespeicher.blogspot.com",
    74               { name: "Steve Speicher", url: "http://stevespeicher.blogspot.com",
    75                 company: "IBM Corporation", companyURL: "http://ibm.com/" },
    75                 company: "IBM Corporation", companyURL: "http://ibm.com/" },
    76               { name: "John Arwe", url: "https://www.ibm.com/developerworks/mydeveloperworks/groups/service/html/allcommunities?userid=120000CAW7",
    76               { name: "John Arwe", url: "https://www.ibm.com/developerworks/mydeveloperworks/groups/service/html/allcommunities?userid=120000CAW7",
    77                 company: "IBM Corporation", companyURL: "http://ibm.com/" },
    77                 company: "IBM Corporation", companyURL: "http://ibm.com/" },
    78 			  {name: "Ashok Malhotra", url: "ashok.malhotra@oracle.com",
    78 			  {name: "Ashok Malhotra", url: "mailto:ashok.malhotra@oracle.com",
    79 			    company: "Oracle Corporation", companyURL: "http://www.oracle.com" },
    79 			    company: "Oracle Corporation", companyURL: "http://www.oracle.com" },
    80           ],
    80           ],
    81 
    81 
    82           // authors, add as many as you like. 
    82           // authors, add as many as you like. 
    83           // This is optional, uncomment if you have authors as well as editors.
    83           // This is optional, uncomment if you have authors as well as editors.
   875 		whose subject is the <code>ldp:Page</code> resource URI,
   875 		whose subject is the <code>ldp:Page</code> resource URI,
   876 		whose predicate is <code>ldp:inlinedResource</code>, and
   876 		whose predicate is <code>ldp:inlinedResource</code>, and
   877 		whose object is the HTTP <code>Request-URI</code> of an inlined resource [[!HTTP11]].
   877 		whose object is the HTTP <code>Request-URI</code> of an inlined resource [[!HTTP11]].
   878 	</div>
   878 	</div>
   879 
   879 
   880 	<div id="ldpc-4_11_3_3" class="rule">4.11.3.3 LDPR clients SHOULD avoid making HTTP <code>GET</code> requests
   880 	<div id="ldpr-4_11_3_3" class="rule">4.11.3.3 LDPR clients SHOULD avoid making HTTP <code>GET</code> requests
   881 		against any resource whose HTTP <code>Request-URI</code> is the object of a triple of the form 
   881 		against any resource whose HTTP <code>Request-URI</code> is the object of a triple of the form 
   882 		described in <a href="#ldpc-4_11_3_2">section 4.11.3.2</a>, unless there are application-specific
   882 		described in <a href="#ldpr-4_11_3_2">section 4.11.3.2</a>, unless there are application-specific
   883 		reasons for doing so.  Clients should note that by the time the representation is received, the actual state
   883 		reasons for doing so.  Clients should note that by the time the representation is received, the actual state
   884 		of any inlined resource(s) may have changed due to subsequent requests.
   884 		of any inlined resource(s) may have changed due to subsequent requests.
   885 	</div>
   885 	</div>
   886 
   886 
   887 	<div id="ldpc-4_11_3_4" class="rule">4.11.3.4 LDPR clients MUST NOT assume that LDPR representations
   887 	<div id="ldpr-4_11_3_4" class="rule">4.11.3.4 LDPR clients MUST NOT assume that LDPR representations
   888 		lacking a <code>ldp:Page</code> resource or lacking the triple
   888 		lacking a <code>ldp:Page</code> resource or lacking the triple
   889 		described in <a href="#ldpc-4_11_3_2">section 4.11.3.2</a> contain all the triples for any resource(s)
   889 		described in <a href="#ldpr-4_11_3_2">section 4.11.3.2</a> contain all the triples for any resource(s)
   890 		listed in the representation whose HTTP <code>Request-URI</code> differs from 
   890 		listed in the representation whose HTTP <code>Request-URI</code> differs from 
   891 		the HTTP <code>Request-URI</code> used by the client.  
   891 		the HTTP <code>Request-URI</code> used by the client.  
   892 		The representation might in fact contain all such triples, or some
   892 		The representation might in fact contain all such triples, or some
   893 		subset of them, and that might or might not be completely adequate for the client's intended usage, but
   893 		subset of them, and that might or might not be completely adequate for the client's intended usage, but
   894 		an LDP client has no way to discern from such a representation which interpretation is accurate.
   894 		an LDP client has no way to discern from such a representation which interpretation is accurate.
  1585 
  1585 
  1586 <section>
  1586 <section>
  1587 <h2 id="ldpc-HTTP_HEAD">HTTP HEAD</h2>
  1587 <h2 id="ldpc-HTTP_HEAD">HTTP HEAD</h2>
  1588 	<p>Note that certain LDP mechanisms, such as paging, rely on HTTP headers, and HTTP generally requires that
  1588 	<p>Note that certain LDP mechanisms, such as paging, rely on HTTP headers, and HTTP generally requires that
  1589 		<code>HEAD</code> responses include the same headers as <code>GET</code> responses. Also LDPC servers must also include HTTP headers
  1589 		<code>HEAD</code> responses include the same headers as <code>GET</code> responses. Also LDPC servers must also include HTTP headers
  1590 		on response to <code>OPTIONS</code>, see <a href="#ldpr-4_7_2">4.7.2</a>.
  1590 		on response to <code>OPTIONS</code>, see <a href="#ldpr-HTTP_OPTIONS" class="sectionRef"></a>.
  1591 		Thus, implementers supporting <code>HEAD</code> should also carefully read the
  1591 		Thus, implementers supporting <code>HEAD</code> should also carefully read the
  1592 		<a href="#ldpc-HTTP_GET" class="sectionRef"></a> and <a href="#ldpc-HTTP_OPTIONS" class="sectionRef"></a>.</p>
  1592 		<a href="#ldpc-HTTP_GET" class="sectionRef"></a> and <a href="#ldpc-HTTP_OPTIONS" class="sectionRef"></a>.</p>
  1593 </section>
  1593 </section>
  1594 
  1594 
  1595 <section>
  1595 <section>