Re: Refers Or Denotes?

On 2/13/13 12:34 PM, Henry Story wrote:
> On 12 Feb 2013, at 22:09, Kingsley Idehen <kidehen@openlinksw.com> wrote:
>
>>> I am not sure why "denotes" is being taken up by the RDF group nowadays, when most philosophy books and logic books tend to use the word "refer". Most engineers use the word refer too on a daily basis.
>> Quite simple, when the context is Linked Data, an HTTP URI has an inherent duality whereby it denotes an entity and identifies a Web resource. This duality makes the use of "refers to" ambiguous as exemplified by the HttpRange-14 permathread. As I said, this matter was discussed to conclusion on the RDF working group list [1].
> While I agree with the general thought you are expressing, putting things like this is liable to be confusing Kingsely, and part of the reason for the existence of the permathreads. This is why we need to clarify the different concepts involved.
>
> I think the illustration here does this nicely:
> https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/img/WebID-overview.png
>
> It shows that URIs just refer/denote.

Yes, that works.

If possible, as already requested, you can add "(perception)" below 
"sense". It also adds visual uniformity too.

>   But as it happens with hash uris they are constitued as per URI definition of two URIs, or rather there is a very strong relation between the one and the other.
>
> [[
> The fragment identifier component of a URI allows indirect identification of a secondary resource by reference to a primary resource and additional identifying information. The identified secondary resource may be some portion or subset of the primary resource, some view on representations of the primary resource, or some other resource defined or described by those representations.
> ]
>    http://tools.ietf.org/html/rfc3986#section-3.5]
>
> This relation I name in the diagram to be the "sense" relation, which goes from the hash URI to the Profile document. This way there is no confusion between sense and reference, and it is clear how each accomplishes the task.
>
> One could make a similar case for URIs with no hash but with a 303 redirect, though in this case the relation between the URI and the sense is not determinable in advance with the URI alone.
>
> Henry
>
>
> Social Web Architect
> http://bblfish.net/
>
>

A hash based HTTP URI is simply about *implicit* indirection. The 
hashless HTTP URI is simply about *explicit* indirection using an HTTP 
redirection heuristic. In either case, abstraction is being used to 
enhance data access by reference (Name or Address).

ODBC and JDBC data access APIs offer the same capability via data source 
names (Names) and connections strings (Locators/Addresses). The 
shortcoming of ODBC (operating system specific) and JDBC (language 
specific)  boils down to not being as open as the Web. In addition, both 
suffer from underlying DBMS technology limitations due to SQL RDBMS 
specificity.

What's old is new :-)

-- 

Regards,

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