W3C home > Mailing lists > Public > public-egov-ig@w3.org > March 2010

Re: Linked Data

From: Michael Hausenblas <michael.hausenblas@deri.org>
Date: Mon, 22 Mar 2010 16:16:05 +0000
To: Sandro Hawke <sandro@w3.org>, Cory Casanave <cory-c@modeldriven.com>
CC: Gannon Dick <gannon_dick@yahoo.com>, <public-egov-ig@w3.org>
Message-ID: <C7CD4845.E796%michael.hausenblas@deri.org>

Sorry for coming back so late re this - was on travel and hence a bit of a
backlog.

> I think Cory is asking procedurally, what should a peice of software do
> to discover VoiD triples about a dataset, given on the the URI of the
> dataset.

Well, as we are in the Linked Data world, this is straight-forward:

1. You have the URI of an RDF document, say http://dbpedia.org/data/Berlin

2. In this document you have a triple that says (old scheme):

   <http://dbpedia.org/data/Berlin> dcterms:isPartOf  :DBpedia .

3. So, eventually one only needs to dereference the :Dbpedia URI, which is
the voiD description of the dataset

Alternatively, there are case where one might want to use the sitemap-based
discovery as described in [1].

Please let me know if this answers you question or there is still something
unclear. All of this works due to applying the Linked Data principles, that
is working with dereferenceable URIs.

Cheers,
      Michael


[1] http://rdfs.org/ns/void-guide#sec_5_2_Discovery_via_sitemaps

-- 
Dr. Michael Hausenblas
LiDRC - Linked Data Research Centre
DERI - Digital Enterprise Research Institute
NUIG - National University of Ireland, Galway
Ireland, Europe
Tel. +353 91 495730
http://linkeddata.deri.ie/
http://sw-app.org/about.html



> From: Sandro Hawke <sandro@w3.org>
> Date: Thu, 18 Mar 2010 22:12:19 -0400
> To: Michael Hausenblas <michael.hausenblas@deri.org>
> Cc: Cory Casanave <cory-c@modeldriven.com>, Gannon Dick
> <gannon_dick@yahoo.com>, <public-egov-ig@w3.org>
> Subject: Re: Linked Data
> 
> 
>>> Given a linked data URI, how do I find the VoiD resource that describes
>>> it?
>> 
>> Initially, we suggested to reuse the dcterms:isPartOf property [1], however
>> due to various reasons we will introduce a dedicated property in voiD 2.0
>> called void:inDataset [2].
> 
> I think Cory is asking procedurally, what should a peice of software do
> to discover VoiD triples about a dataset, given on the the URI of the
> dataset.
> 
>       -- Sandro
> 
>> [1] http://rdfs.org/ns/void-guide#sec_4_2_Back-links
>> 
>> -- 
>> Dr. Michael Hausenblas
>> LiDRC - Linked Data Research Centre
>> DERI - Digital Enterprise Research Institute
>> NUIG - National University of Ireland, Galway
>> Ireland, Europe
>> Tel. +353 91 495730
>> http://linkeddata.deri.ie/
>> http://sw-app.org/about.html
>> 
>> 
>> 
>>> From: Cory Casanave <cory-c@modeldriven.com>
>>> Date: Thu, 18 Mar 2010 18:50:38 -0400
>>> To: Michael Hausenblas <michael.hausenblas@deri.org>, Gannon Dick
>>> <gannon_dick@yahoo.com>
>>> Cc: <public-egov-ig@w3.org>
>>> Subject: RE: Linked Data
>>> 
>>> Given a linked data URI, how do I find the VoiD resource that describes
>>> it?
>>> 
>>> -----Original Message-----
>>> From: public-egov-ig-request@w3.org
>>> [mailto:public-egov-ig-request@w3.org] On Behalf Of Michael Hausenblas
>>> Sent: Thursday, March 18, 2010 6:28 PM
>>> To: Gannon Dick
>>> Cc: public-egov-ig@w3.org
>>> Subject: Re: Linked Data
>>> 
>>> 
>>> Gannon,
>>> 
>>> Not sure I totally understand the issue you seem to raise, but if I
>>> understand you correctly the solution is simple: voiD (vocabulary of
>>> interlinked datasets) [1]-[4].
>>> 
>>> Cheers,
>>>       Michael
>>> 
>>> [1] http://semanticweb.org/wiki/VoiD
>>> [2] http://rdfs.org/ns/void-guide
>>> [3] http://rdfs.org/ns/void
>>> [4] http://sw-app.org/pub/ldow09-void.pdf
>>> 
>>> -- 
>>> Dr. Michael Hausenblas
>>> LiDRC - Linked Data Research Centre
>>> DERI - Digital Enterprise Research Institute
>>> NUIG - National University of Ireland, Galway
>>> Ireland, Europe
>>> Tel. +353 91 495730
>>> http://linkeddata.deri.ie/
>>> http://sw-app.org/about.html
>>> 
>>> 
>>> 
>>>> From: Gannon Dick <gannon_dick@yahoo.com>
>>>> Date: Thu, 18 Mar 2010 15:05:28 -0700 (PDT)
>>>> To: <public-egov-ig@w3.org>
>>>> Subject: Linked Data
>>>> Resent-From: <public-egov-ig@w3.org>
>>>> Resent-Date: Thu, 18 Mar 2010 22:06:04 +0000
>>>> 
>>>> CC wrote:
>>>> On the demo call today we discussed a couple of technical issues that
>>>> impact but are not specific to government.  These are:
>>>> 
>>>> 1)       That given a data URI, there is no standard way to
>>>> programmatically access the metadata about the resource.
>>>> 
>>>> Sandro wrote: (can't find the exact quote)
>>>> -The RDF model is the only one we (the W3C) have.-
>>>> 
>>>> I also looked at the DERI.ORG sitemap extensions.  The explanations
>>> were well
>>>> worth the read.  The potential problem I see with extending sitemap is
>>> that it
>>>> disconnects linked data from it's RDF and (Collection of) Human
>>> Readable HTML
>>>> parts - 1 site=1 Database - and if you had more than one <owl:Thing>
>>> to share
>>>> it could get very complicated.  Therein lies the rub.
>>>> 
>>>> For reasons stated here:
>>>> http://www.rustprivacy.org/2010/meta/linked-data.pdf
>>>> with an example here:
>>>> http://www.rustprivacy.org/2010/meta/linked-data.xml
>>>> or for the bold:
>>>> http://www.rustprivacy.org/2010/meta/linked-data.xsl (on valid XHTML)
>>>> 
>>>> I think the complexity is in the nature of meta data and not in the
>>> sitemap
>>>> mechanism.  However, I could really, really really use some feedback
>>> from the
>>>> W3C and deri.org.
>>>> 
>>>> --Gannon 
>>>> 
>>>> 
>>>>       
>>>> 
>>> 
>>> 
>>> 
>> 
>> 
Received on Monday, 22 March 2010 16:16:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 22 March 2010 16:16:52 GMT