diff -r add97cfc2550 -r 6871b9ac5339 ldp.html --- 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: "ashok.malhotra@oracle.com", + {name: "Ashok Malhotra", url: "mailto:ashok.malhotra@oracle.com", company: "Oracle Corporation", companyURL: "http://www.oracle.com" }, ], @@ -877,16 +877,16 @@ whose object is the HTTP Request-URI of an inlined resource [[!HTTP11]]. -
4.11.3.3 LDPR clients SHOULD avoid making HTTP GET requests +
4.11.3.3 LDPR clients SHOULD avoid making HTTP GET requests against any resource whose HTTP Request-URI is the object of a triple of the form - described in section 4.11.3.2, unless there are application-specific + described in section 4.11.3.2, 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.
-
4.11.3.4 LDPR clients MUST NOT assume that LDPR representations +
4.11.3.4 LDPR clients MUST NOT assume that LDPR representations lacking a ldp:Page resource or lacking the triple - described in section 4.11.3.2 contain all the triples for any resource(s) + described in section 4.11.3.2 contain all the triples for any resource(s) listed in the representation whose HTTP Request-URI differs from the HTTP Request-URI used by the client. The representation might in fact contain all such triples, or some @@ -1587,7 +1587,7 @@

HTTP HEAD

Note that certain LDP mechanisms, such as paging, rely on HTTP headers, and HTTP generally requires that HEAD responses include the same headers as GET responses. Also LDPC servers must also include HTTP headers - on response to OPTIONS, see 4.7.2. + on response to OPTIONS, see . Thus, implementers supporting HEAD should also carefully read the and .