W3C home > Mailing lists > Public > public-hydra@w3.org > January 2015

Re: remove hydra:Resource and hydra:Class

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Sat, 10 Jan 2015 14:28:22 -0500
Message-ID: <54B17D56.3050705@openlinksw.com>
To: public-hydra@w3.org
On 1/10/15 4:42 AM, Ruben Verborgh wrote:
> Hi John,
>>>> >>>The use case is: mark a hyperlink as dereferenceable in-place.
>> >
>>> >>But then again, what tangible benefit does this give?
>> >
>> >I think to mark that from the perspective of the publisher that it could be dereferenced.
>> >Just thinking about things like XML schema references, these often refer to the URI of the schema, but it is not intended to dereference these links.
> Note that those are two different things: being dereferenceable,
> and suggesting an intent to dereference something.


Names are always interpretable by definition, hence their inherent 
ability to provide denotation (signification) and connotation 

Each of the following identify (denote and connote) entities (things) 
that could the be the subject, predicate, or object of an RDF statement:


How these names are interpreted (resolved to connotation) is a function 
of the naming mechanism (in this case URI scheme), which is why HTTP URI 
based names are so useful re., HTTP networks i.e., you have name => 
description document resolution baked in.

This is why Linked Data boils down to:

1. Naming entities (things)
2. Using HTTP URI based Names
3. Providing useful information in the docs to which HTTP URIs resolve 
-- e.g., an entity description using RDF statements, in your preferred 
4. In your entity description document, refer to other entities using 
their HTTP URIs -- net effect, your Data Web is extended.




Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog 1: http://kidehen.blogspot.com
Personal Weblog 2: 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
Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this

Received on Saturday, 10 January 2015 19:28:45 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 10 January 2015 19:28:45 UTC