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

Re: LOD Data Sets, Licensing, and AWS

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Wed, 24 Jun 2009 13:17:39 -0400
Message-ID: <4A425FB3.3070702@openlinksw.com>
To: Leigh Dodds <leigh.dodds@talis.com>
CC: Ian Davis <lists@iandavis.com>, public-lod@w3.org
Leigh Dodds wrote:
> Hi,
>
> 2009/6/24 Kingsley Idehen <kidehen@openlinksw.com>:
>   
>> To save time etc..
>>
>> What is the URI of a license that effectively enables data publishers to
>> express and enforce how they are attributed? Whatever that is I am happy
>> with. Whatever that is will be vital to attracting curators of high quality
>> data to the LOD fold.
>>
>> If you have a an example URI even better.
>>     
>
> You can chose from several at http://www.opendatacommons.org/
>
>   
>> Take a look at Freebase, and how they are effectively doing what I espouse.
>> Google uses Freebase URIs, and they attribute by URI.
>>     
>
> I have. I've read the licensing, terms and policies of a number of
> different websites.
>
>   
>> I see Freebase using CC-BY-SA to effectively propagate their URIs. I also
>> see all consumers of Freebase URIs honoring the terms without any issues.
>>     
>
> Really? I'm not trying to be unfair, but where on:
>   
You're not being unfair. We are trying to get to the bottom of something 
that really important.
> http://lod.openlinksw.com/
>
> Or
>
> http://lod.openlinksw.com/describe/?url=http%3A%2F%2Ffreebase.com%2Fguid%2F9202a8c04000641f80000000083d84dd
>   
The URIs are in full view. Use a Linked Data Aware user agent against 
the URIs and you end up in the originating Freebase Data Space. This is 
my fundamental point re. preservation of original URIs.
> Are the attributions required in:
>
> http://www.freebase.com/signin/licensing
>
> A link to the topic page isn't enough based on the terms that Freebase
> currently publish. I'm not saying I agree with them, as clearly they
> don't scale well in the large. They've also not defined an attribution
> policy for data linking. And if they don't care enough about the
> attribution to follow-up, then why not publish it under a
> non-attribution license in the first place?
>   
The source of the data in our data space is crystal clear by virtue of 
URI visibility. Just look at the Entity URI associated with the text 
following "About:" (the @href value). We are saying: this page is about 
a resource in the Freebase Data Space and we use the Freebase URI in 
@href. In short, just click on it and see what happens :-)


You can use ODE, DISCO, Zitgist Data Viewer, or Tabulator etc. to 
explore the URIs, and you will end up in the originating data space of a 
given entity.

Now for the problems re. our pages:

Our embedded RDFa produces:

<rdf:RDF>
<rdf:Description rdf:about="http://lod.openlinksw.com/fct/rdfdesc/">
<xhv:alternate 
rdf:resource="http://lod.openlinksw.com/sparql?query=DESCRIBE%20%3Chttp%3A%2F%2Ffreebase.com%2Fguid%2F9202a8c04000641f80000000083d84dd%3E"/>
<xhv:stylesheet 
rdf:resource="http://lod.openlinksw.com/fct/rdfdesc/styles/default.css"/>
<xhv:stylesheet 
rdf:resource="http://lod.openlinksw.com/fct/rdfdesc/styles/highlighter.css"/>
<xhv:license rdf:resource="http://creativecommons.org/licenses/by-sa/3.0/"/>
</rdf:Description>
</rdf:RDF>

That's wrong, it should be:

<rdf:RDF>
<rdf:Description 
rdf:about="http://freebase.com/guid/9202a8c04000641f80000000083d84dd">
<xhv:alternate 
rdf:resource="http://lod.openlinksw.com/sparql?query=DESCRIBE%20%3Chttp%3A%2F%2Ffreebase.com%2Fguid%2F9202a8c04000641f80000000083d84dd%3E"/>
<xhv:stylesheet 
rdf:resource="http://lod.openlinksw.com/fct/rdfdesc/styles/default.css"/>
<xhv:stylesheet 
rdf:resource="http://lod.openlinksw.com/fct/rdfdesc/styles/highlighter.css"/>
<xhv:license rdf:resource="http://creativecommons.org/licenses/by-sa/3.0/"/>
</rdf:Description>
</rdf:RDF>


Kingsley
> Cheers,
>
> L.
>
>   


-- 


Regards,

Kingsley Idehen	      Weblog: http://www.openlinksw.com/blog/~kidehen
President & CEO 
OpenLink Software     Web: http://www.openlinksw.com
Received on Wednesday, 24 June 2009 17:18:20 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:21 UTC