W3C home > Mailing lists > Public > public-rdf-wg@w3.org > May 2012

Re: Redefining “resource”

From: Dan Brickley <danbri@danbri.org>
Date: Fri, 25 May 2012 17:59:16 +0300
Message-ID: <CAFfrAFow3rT60DcCUnDkKQNvdjQka7TvwhZn6XVm=7Fgaa9H=g@mail.gmail.com>
To: Kingsley Idehen <kidehen@openlinksw.com>
Cc: public-rdf-wg@w3.org
On 25 May 2012 17:06, Kingsley Idehen <kidehen@openlinksw.com> wrote:

>
> We don't have to redefine 'Resource'. All we have to do is assume that
> readers of the spec understand that a URI denotes an entity and URLs
> identify resources.

a) URL is not a current precisely standardised technical term
b) Neither is 'resource'

Dan

> That also means that a generic HTTP URI can denote an
> entity and -- via magic of indirection -- identify a resource that's
> comprised of RDF content that describes said URI's referent.
>
> We've finally separated 'Entity' and 'Resource'. Hence my comment in an
> earlier post:
>
> http://dbpedia.org/resource/Paris  identifies a "resource" and "denotes" an
> entity. As for the actual entity in question, this is clarified when you
> de-reference the identifier and discern resource content.
>
>
> --
>
> 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
>
>
>
>
>
>
Received on Friday, 25 May 2012 15:00:56 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:25:49 GMT