Re: How about "identifying URL" instead of "canonical" URL?

On 6/23/14 1:02 PM, Arnaud Le Hors wrote:
> Kingsley,
> How would you edit the text Cody quoted then?
Edit draft.
Note:  if the gist of it is understood and accepted, I can work with Ted 
on a much more formalized edit that fits into the current doc:

<section>
<h3>Respond with *resource URIs* and use them for identity comparison</h3>

<p>Clients can access an LDPR *by de-referencing* multiple *URIs*. An 
LDPR server
should respond to each of those requests using a single consistent
*URI, for the LDPR. This identifying *URI* 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
*URIs* that vary by protocol, one HTTP and one HTTPS, but are
otherwise identical *if the server reconciles across these URI schemes*.
                                 In *cases where two *URIs* refer to the 
same
resource, the server should respond to requests on either URI
with a single (description document) location (URL)*.</p>

<p>Clients should use HTTP URIs to denote LDPR's;
for example, when determining if two *URIs refer to the same resource
clients should compare HTTP URIs that denote LDPRs, not the HTTP URLs that
                                 denote their description documents.* </p>

Kingsley

> --
> Arnaud  Le Hors - Software Standards Architect - IBM Software Group
>
>
>
>
> From: Kingsley Idehen <kidehen@openlinksw.com>
> To: public-ldp-wg@w3.org,
> Date: 06/23/2014 09:49 AM
> Subject: Re: How about "identifying URL" instead of "canonical" URL?
> ------------------------------------------------------------------------
>
>
>
> On 6/23/14 11:52 AM, Arnaud Le Hors wrote:
> This sounds odd to me. I'd rather we use primary, as suggested by Sandro.
>
> So you find: Primary URL clearer than canonical URI or even canoical 
> URL. Where is "Primary..." in any RDF or AWWW spec?
>
>
> That it sounds nice to you is not the point!
>
> Kingsley
> --
> Arnaud  Le Hors - Software Standards Architect - IBM Software Group
>
>
> Cody Burleson _<cody.burleson@base22.com>_ 
> <mailto:cody.burleson@base22.com>wrote on 06/23/2014 08:19:06 AM:
>
> > From: Cody Burleson _<cody.burleson@base22.com>_ 
> <mailto:cody.burleson@base22.com>
> > To: Linked Data Platform WG _<public-ldp-wg@w3.org>_ 
> <mailto:public-ldp-wg@w3.org>,
> > Date: 06/23/2014 08:30 AM
> > Subject: How about "identifying URL" instead of "canonical" URL?
> >
> > 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
>
>
>
> -- 
>
> Regards,
>
> Kingsley Idehen
> Founder & CEO
> OpenLink Software
> Company Web: _http://www.openlinksw.com_ <http://www.openlinksw.com/>
> Personal Weblog: _http://www.openlinksw.com/blog/~kidehen_ 
> <http://www.openlinksw.com/blog/%7Ekidehen>
> Twitter Profile: _https://twitter.com/kidehen_
> Google+ Profile: _https://plus.google.com/+KingsleyIdehen/about_
> LinkedIn Profile: _http://www.linkedin.com/in/kidehen_
>
>
>
>
>


-- 

Regards,

Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter Profile: https://twitter.com/kidehen
Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen