Re: A VoCamp Galway 2008 success story

Hi Richard,

My problem is the following. I'm working on a system for interlinking 
and fusing Web datasets. The output of the interlink module is a named 
graph containing a set of owl:same_as statements (a linkset). This graph 
is itself described using a few properties indicating how it was 
generated. I think it would make sense to type this graph as a 
voiD:Linkset and let it pointing to the two datasets. The idea behind is 
that, as we are dealing with open data, we cannot enforce people to use 
a given set of interlinks. Let's one use the linkset he trusts !

This approach is actually similar to the by ODDlinker output from 
LinkedMDB (example [1]). An interlink is a first-class citizen pointing 
to both linked resources.

Cheers,
François

[1] http://data.linkedmdb.org/page/interlink/135784

Richard Cyganiak wrote:
> 
> François,
> 
> We chose the current model (ds1 -> containsLinks -> ls -> target -> ds2) 
> because we want to record which dataset contains the links. We have some 
> use cases that require this. Your proposal (ds1 <- target <- ls -> 
> target -> ds2) doesn't capture that bit of information.
> 
> Note that *all* the links in the LOD cloud are published as part of one 
> of the datasets. I'm also not sure if there is a clear understanding 
> about how to publish linksets independently from the datasets on the 
> Web. I don't see it being done in practice.
> 
> François, can you point us to some examples of linksets that are 
> published independently from any of the linked datasets? Also, can you 
> present us with your use case that requires exchanging descriptions of 
> such linksets? If there is enough interest, we will consider a modelling 
> that can be used for both scenarios.
> 
> Best,
> Richard
> 
> 
> On 29 Nov 2008, at 10:16, François Scharffe wrote:
> 
>> Hi Michael,
>>
>> thank you for the link ;)
>> It seems that the current voiD spec supposes that the linkset (set of 
>> interlinks) is supposed to be included in one of the two interlinked 
>> datasets. I think it would make sense for the linkset to be considered 
>> independently from the two interlinked datasets, something like this:
>>
>> my:links a void:Linkset ;
>>         void:target <dataset1> ;
>>         void:target <dataset2> ;
>>
>> my:links is a named graph containing the set of owl:same_as links. 
>> This would avoiD to bind a dataset with a set of links.
>>
>> Cheers,
>> François
>>
>> Michael Hausenblas wrote:
>>> Just to let you know. One of the outcomes of the recent VoCamps [1] 
>>> was that we have agreed on a final layout for voiD (Vocabulary of 
>>> Interlinked Datasets). It is now available at [2] - please note that 
>>> the actual (final) namespace will be 'http://rdfs.org/ns/void#' ... 
>>> can't fix everything within two days, right :)
>>> A more detailed user guide to follow soon!
>>> Cheers,
>>>    Michael
>>> PS: A big thanks to the Neologism (http://neologism.deri.ie/) people 
>>> for creating such an awesome tool and John Breslin for the great 
>>> support re rdfs.org!
>>> [1] http://vocamp.org/wiki/VoCampGalway2008#Outcomes
>>> [2] http://rdfs.org/ns/neologism/void
>>> ----------------------------------------------------------
>>> Dr. Michael Hausenblas
>>> DERI - Digital Enterprise Research Institute
>>> National University of Ireland, Lower Dangan,
>>> Galway, Ireland
>>> ----------------------------------------------------------
>>
>> <francois_scharffe.vcf>
> 
> 
>