W3C home > Mailing lists > Public > public-ldp-wg@w3.org > October 2012

Re: Use-Cases and call for help to add descriptions and scenarios.

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Wed, 03 Oct 2012 14:04:01 -0400
Message-ID: <506C7E11.5090200@openlinksw.com>
To: public-ldp-wg@w3.org
On 10/3/12 1:41 PM, Wilde, Erik wrote:
> On 2012-10-03 8:39 , "Steve Battle" <steve.battle@sysemia.co.uk> wrote:
>> For the scenario where the URIs do differ, do you have any thoughts on
>> whether POWDER would be a good approach to making the relationship between
>> the non-information and information resources explicit?
>> e.g. <http://example.com/people/alice> wdrs:describedby
>> <http://example.com/people/alice.rdf>
> i think this is exactly was POWDER's 'describedby' was created for, and
> for making the reverse direction discoverable,
> http://tools.ietf.org/html/draft-wilde-describes-link-01 proposes a
> 'describes' link relation type.
>
> cheers,
>
> dret.
>
>
>
>
'describes' is the inverse of 'describedby'  which is semantically 
equivalent to wdrs:describedby .

Example:

http://linkeddata.informatik.hu-berlin.de/uridbg/index.php?url=http://dbpedia.org/page/Linked_data&acceptheader=&useragentheader= 
-- URI Debugger output against DBpedia URI



-- 

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 Wednesday, 3 October 2012 18:04:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:17:32 UTC