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

Re: remove hydra:Resource and hydra:Class

From: John Walker <john.walker@semaku.com>
Date: Sun, 11 Jan 2015 09:31:58 +0100
Message-Id: <588096FB-7A4A-4A3E-A7E3-FE5D56FAE3D7@semaku.com>
Cc: "public-hydra@w3.org" <public-hydra@w3.org>
To: Kingsley Idehen <kidehen@openlinksw.com>
Hi Kingsley, Ruben,

I had an old w3c blog post in mind [2] but time clouded my recollection.
The message there seems clear, clients should make use of and respect caching headers.

I think indicating/suggesting that it may be useful to dereference a resource (perhaps depending on context) might be useful.

Regards,

John

On 10 Jan 2015, at 20:28, Kingsley  Idehen <kidehen@openlinksw.com> wrote:

> 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.
> 
> +1
> 
> Names are always interpretable by definition, hence their inherent ability to provide denotation (signification) and connotation (description).
> 
> Each of the following identify (denote and connote) entities (things) that could the be the subject, predicate, or object of an RDF statement:
> 
> • file:{doc}:uriReferent
> • http://<cname>/doc#uriReferent
> 
> 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 notation
> 4. In your entity description document, refer to other entities using their HTTP URIs -- net effect, your Data Web is extended.
> 
> Links:
> 
> 
> [1] http://bit.ly/evidence-that-the-world-wide-web-was-based-on-linked-data-from-inception .
[2] http://www.w3.org/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic/
> 
> -- 
> Regards,
> 
> 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 Sunday, 11 January 2015 08:52:29 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 11 January 2015 08:52:30 UTC