W3C home > Mailing lists > Public > public-lod@w3.org > January 2009

Re: [call for comments] voiD 1.0

From: Michael Hausenblas <michael.hausenblas@deri.org>
Date: Fri, 30 Jan 2009 08:43:16 +0000
To: Peter Ansell <ansell.peter@gmail.com>
CC: Linked Data community <public-lod@w3.org>, Semantic Web community <semantic-web@w3.org>
Message-ID: <C5A86E24.1682%michael.hausenblas@deri.org>


> What was the rationale behind having both void:target and the
> combination of void:subjectsTarget and void:objectsTarget?

I have to admit it is likely not as obvious as I'd want it to be ;)

May I refer to a nice explanation posted earlier here by Danny [1]?

So, basically this modelling allows you (as the dataset publisher) some more
flexibility. Additionally one has to note that SPARQL queries only work
properly (as intended by this modelling) when taking into account that both
void:subjectsTarget and void:objectsTarget are actually sub-properties of
void:target, that is needs some light-weight reasoning along with it.


[1] http://lists.w3.org/Archives/Public/public-lod/2008Nov/0214.html

Dr. Michael Hausenblas
DERI - Digital Enterprise Research Institute
National University of Ireland, Lower Dangan,
Galway, Ireland, Europe
Tel. +353 91 495730

> From: Peter Ansell <ansell.peter@gmail.com>
> Date: Fri, 30 Jan 2009 09:11:44 +1000
> To: Michael Hausenblas <michael.hausenblas@deri.org>
> Cc: Linked Data community <public-lod@w3.org>, Semantic Web community
> <semantic-web@w3.org>
> Subject: Re: [call for comments] voiD 1.0
> 2009/1/30 Michael Hausenblas <michael.hausenblas@deri.org>:
>> Dear LODers,
>> We are very pleased to announce the release of voiD [1].
>> voiD (from "Vocabulary of Interlinked Datasets") is an RDF based schema to
>> describe linked datasets. With voiD the discovery and usage of linked
>> datasets can be performed both effectively and efficiently. A dataset is a
>> collection of data, published and maintained by a single provider, available
>> as RDF, and accessible, for example, through dereferenceable HTTP URIs or a
>> SPARQL endpoint.
>> We ask for comments on both the vocabulary [2] as well as the guide [3] -
>> this will certainly help to release a second version of voiD in the near
>> future.  When providing feedback, please CC
>> void-rdfs-internals@googlegroups.com.
>> Our thanks go out to some chaps who influenced the design of voiD, provided
>> use cases and ensured that we would never get bored too quickly (in
>> alphabetic order): Orri Erling, Hugh Glaser, Olaf Hartig, Tom Heath, Ian
>> Millard, Marc-Alexandre Nolin, Yves Raimond, Yrjänä Rankka, Francois
>> Scharffe, Giovanni Tummarello.
>> On behalf of the voiD team (Keith, Richard, Jun and /me)
>> Cheers,
>>      Michael
>> [1] http://semanticweb.org/wiki/VoiD
>> [2] http://rdfs.org/ns/void
>> [3] http://rdfs.org/ns/void-guide
> What was the rationale behind having both void:target and the
> combination of void:subjectsTarget and void:objectsTarget?
> I would have thought that linksets would always be directed, otherwise
> it leaves you uncertain about whether you can actually find anything
> in one set or the triples are actually contained in the other dataset.
> At least with subjectsTarget you can always be sure that that dataset
> will contain the relevant triples. If people use two void:target
> statements as part of a linkset can we only assume that they are
> trying to include triples from both datasets at once? If so, the
> target's might contain anything resembling the statistics that one
> might be able to apply to directed linksets where one is really only
> trying to describe a subset of triples from void:subjectsTarget that
> happen to have object resources in another known dataset?
> Cheers,
> Peter
Received on Friday, 30 January 2009 08:44:04 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:15:54 UTC