RE: attaching multiple licenses

Hi Tom,

sure, in an ideal world we could just point to the rdf data in other
sources. Unfortunately, we're not quite there yet...

Integrating data includes data cleansing, schema mapping etc., and if we'd
just publish the mapping and cleansing rules instead of the cleaned data,
then the rdf client would need to execute those rules. I doubt that would
really work...

> On a different note, why publish your owl:sameAs links as CC, rather
> than also putting them into the Public Domain and adding social norms
> if you want attribution, for example?

Yes, of course. It was just an example since currently owl:sameas statements
are included into the datasets and hence licensed under the same license as
the dataset itself. 

It would seem a bit strange to me to put every sameas triple into a separate
document and link from the "data"-rdf to that sameas-document. That's why I
asked to a solution to publish the sameas triple in the same document along
with the "data", but attribute a different license. 

Cheers,
Georgi

--
Georgi Kobilarov
www.georgikobilarov.com

> -----Original Message-----
> From: tzh@talisplatform.com [mailto:tzh@talisplatform.com] On Behalf Of
> Tom Heath
> Sent: Monday, December 07, 2009 12:05 PM
> To: Georgi Kobilarov
> Cc: public-lod@w3.org
> Subject: Re: attaching multiple licenses
> 
> Hi Georgi,
> 
> I guess I would question why you want to replicate external triples in
> your RDF document, rather than including them by reference to the
> source documents...
> 
> This is exactly the issue I came up against when developing Revyu,
> where I concluded that while the HTML document about a resource may
> usefully show external data so humans get the whole picture, there's
> something that feels fundamentally wrong about replicating RDF data
> rather than just pointing applications to the places where they can
> find it.
> 
> IIRC then Tim disagreed with this at some point, arguing that two
> documents that describe the same resource and are reached by content
> negotiation and a 303 from the same URI should contain the same
> information to the greatest possible extent. Even where we discount
> aspects like navigation and ads in HTML documents I don't agree with
> this; HTML and RDF documents have different audiences and therefore
> the requirements on them are different. Replicating data all over the
> place seems fundamentally un-Web-like and raises exactly the kinds of
> issues you've come up against.
> 
> On a different note, why publish your owl:sameAs links as CC, rather
> than also putting them into the Public Domain and adding social norms
> if you want attribution, for example?
> 
> Cheers,
> 
> Tom.
> 
> 
> 2009/12/6 Georgi Kobilarov <georgi.kobilarov@gmx.de>:
> > Dear LODers,
> >
> > I'm looking for a best practice for publishing multiple licenses along
> with
> > one rdf document.
> >
> > Say I publish one URI for an artist:
> > http://example.org/resource/Madonna
> >
> > I aggregate information from multiple sources about that artist, and
> those
> > sources have different licenses. One triple comes from a source under
> GNU
> > FDL, another triple from a source under Public Domain, and a owl:sameas
> link
> > which I want to publish under Creative Commons License.
> >
> > Any pointers to how to do that?
> >
> > Thanks,
> > Georgi
> >
> > --
> > Georgi Kobilarov
> > www.georgikobilarov.com
> >
> >
> >
> > ______________________________________________________________________
> > This email has been scanned by the MessageLabs Email Security System.
> > For more information please visit http://www.messagelabs.com/email
> > ______________________________________________________________________
> >
> 
> 
> 
> --
> Dr Tom Heath
> Researcher
> Platform Division
> Talis Information Ltd
> T: 0870 400 5000
> W: http://www.talis.com/

Received on Tuesday, 8 December 2009 15:06:30 UTC