RE: dwbp-ACTION-117: Explore the use cases that might clarify the need for uri and url design

I agree with Tomas that we need to be careful not to conflate URI and URL. HTTP URIs may share the same syntax space as URLs but their roles are different: URIs identify while URLs locate. I think that design rules for URIs make sense, but design rules for URLs do not. 

Makx.



> -----Original Message-----
> From: Manuel.CARRASCO-BENITEZ@ec.europa.eu [mailto:Manuel.CARRASCO-
> BENITEZ@ec.europa.eu]
> Sent: Tuesday, November 04, 2014 3:37 PM
> To: public-dwbp-wg@w3.org
> Subject: RE: dwbp-ACTION-117: Explore the use cases that might clarify
> the need for uri and url design
> 
> Dear all,
> 
> One should use the term URI and only use URL when referring to URI
> that provides location.
> 
> Quote - https://tools.ietf.org/html/rfc3986#section-1.1.3
> 
> "Uniform Resource Locator" (URL) refers to the subset of URIs that, in
> addition to identifying a resource, provide a means of locating the
> resource by describing its primary access mechanism
> 
> Future specifications and related documentation should use the general
> term "URI" rather than the more restrictive terms "URL" and "URN"
> 
> Regards
> Tomas
> 
> -----Original Message-----
> From: Data on the Web Best Practices Working Group Issue Tracker
> [mailto:sysbot+tracker@w3.org]
> Sent: Friday, October 31, 2014 10:26 PM
> To: public-dwbp-wg@w3.org
> Subject: dwbp-ACTION-117: Explore the use cases that might clarify the
> need for uri and url design
> 
> dwbp-ACTION-117: Explore the use cases that might clarify the need for
> uri and url design
> 
> http://www.w3.org/2013/dwbp/track/actions/117
> 
> Assigned to: Phil Archer
> 
> 
> 
> 
> 
> 
>

Received on Tuesday, 4 November 2014 17:37:39 UTC