We use ODC-By with a "special cases" clause for some of our datasets to account 
for Linked Data situations. Thoughts and comments about this approach would be 
welcome. 

http://purl.oclc.org/dataset/WorldCat
http://viaf.org/viaf/data

Jeff

Sent from my iPad

On Mar 31, 2013, at 10:00 AM, "Dominic Oldman" <do...@oldman.me.uk> wrote:

> 
> 
> 
> All,
> 
> Sorry, the body of my last message didn't seem to appear on the list.
> 
> I had a question about licensing. Should licenses try to get web publishers 
> to embed original URIs into web implementations - a sort of invisible 
> attribution - where practical, and is this practical and/or desirable. 
> 
> There is another reason for including URIs which might not be considered in 
> the Academy. It allows knowledge organisations to see how its knowledge is 
> being enriched and provide options for bringing it back into the original 
> information system infrastructures so it can be preserved - a sort of mega 
> and indirect crowd sourcing but across the Internet rather than any 
> particular web site.
> 
> If I publish a cuneiform data record and it is reused in different projects 
> and applications, and the data is enriched with annotations, corrections, 
> additions etc., if the original URI is embedded, I can harvest this 
> information and enrich the object record against the original URI so that 
> subsequent users (including our own researchers and audiences) benefit by 
> this continual community improvement. This is one of the objectives of the 
> ResearchSpace project - to encourage enrichment against institutional URIs so 
> that research projects (which are temporary and are limited in the way that 
> they give back to the community) have a more permanent and long lasting 
> legacy. 
> 
> Dominic
> 
> From: Kingsley Idehen <kide...@openlinksw.com>
> To: "public-lod@w3.org" <public-lod@w3.org> 
> Sent: Saturday, 30 March 2013, 14:35
> Subject: Why is it bad practice to consume Linked Data and publish opaque 
> HTML pages?
> 
> All,
> 
> " Citing sources is useful for many reasons: (a) it shows that it isn't a 
> half-baked idea I just pulled out of thin air, (b) it provides a reference 
> for anybody who wants to dig into the subject, and (c) it shows where the 
> ideas originated and how they're likely to evolve." -- John F. Sowa [1].
> 
> An HTTP URI is an extremely powerful citation and attribution mechanism. 
> Incorporate Linked Data principles and the power increases exponentially.
> 
> It is okay to consume Linked Data from wherever and publish HTML documents 
> based on source data modulo discoverable original sources Linked Data URIs.
> 
> It isn't okay, to consume publicly available Linked Data from sources such as 
> the LOD cloud and then republish the extracted content using HTML documents, 
> where the original source Linked Data URIs aren't undiscoverable by humans or 
> machines.
> 
> The academic community has always had a very strong regard for citations and 
> source references. Thus, there's no reason why the utility of Linked Data 
> URIs shouldn't be used to reinforce this best-practice, at Web-scale .
> 
> Links:
> 
> 1. http://ontolog.cim3.net/forum/ontolog-forum/2013-03/msg00084.html -- 
> ontolog list post .
> 
> -- 
> 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
> 
> 
> 
> 
> 
> 
> 

Reply via email to