- From: Ashok Malhotra <ashok.malhotra@oracle.com>
- Date: Mon, 23 Jun 2014 11:49:00 -0400
- To: public-ldp-wg@w3.org
- Message-ID: <53A84C6C.204@oracle.com>
Or "authoritative URL"? All the best, Ashok On 6/23/2014 11:19 AM, Cody Burleson wrote: > Regarding today's discussion about the ambiguity and possible inaccurate nature of our use of the the term "canonical"... > > How about "identifying" ? > > Here's how it reads: > > <section> > <h3>Respond with identifying URLs and use them for identity comparison</h3> > > <p>Clients can access an LDPR using multiple URLs. An LDPR server > should respond to each of those requests using a single consistent > URL, an <em>identifying</em> URL, for the LDPR. This identifying URL may be found > in the response's Location and/or Content-Location headers, and > potentially also in the representation of the LDPR. A common case is > URLs that vary by protocol, one HTTP and one HTTPS, but are > otherwise identical. In most cases those two URLs refer to the same > resource, and the server should respond to requests on either URL > with a single (identity) URL.</p> > > <p>Clients should use the identifying URL as an LDPR's identity; > for example, when determining if two URLs refer to the same resource > clients should compare the identifying URLs, not the URLs used to > access the resources.</p> > > > > -- > Cody Burleson > >
Received on Monday, 23 June 2014 15:50:49 UTC