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

RE: attaching multiple licenses

From: Georgi Kobilarov <georgi.kobilarov@gmx.de>
Date: Tue, 8 Dec 2009 16:22:28 +0100
To: "'Toby Inkster'" <tai@g5n.co.uk>
Cc: <public-lod@w3.org>
Message-ID: <000001ca781a$416f5aa0$c44e0fe0$@kobilarov@gmx.de>
Hi Toby,
> Two methods spring to mind. The first is reification. [...]

Well... no reification. :)

> A better solution might be to publish your data in a format that can
> make use of multiple graphs. e.g. in N3:
> 	{
> 	  <http://example.org/resource/Madonna>
> 	    <http://xmlns.com/foaf/0.1/name>
> 	      "Madonna Veronica Louise Chicone"
> 	}
> 	  ex:graphLicence </public-domain-declaration> .
> Unfortunately, most of the data formats with native support for named
> graphs do not have very good support in consuming software. But you can
> fake named graphs in formats like RDF/XML, Turtle, etc by simply
> splitting your data into multiple documents. So, in one file, you'd
> have:
> 	<http://example.org/resource/Madonna>
> 	  <http://xmlns.com/foaf/0.1/name>
> 	    "Madonna Veronica Louise Chicone" .
> 	<>
> 	  ex:graphLicence
> 	    </public-domain-declaration> .
> And in other files, you'd publish your other statements under different
> licenses. You'd use rdfs:seeAlso links between the files to enable
> autodiscovery.

Yes, that'd be a solution (similar to what Tom suggested). 

And we'd run into the issue Tom mentioned re. "two documents about the same resource should serve the same data". The html output would probably show all triples, but the content negotiated / 303ed rdf document would contain only links to other rdf documents.

Also we'd need to set that as a common practice, otherwise Linked Data clients won't support it. And if the data is split into too many documents, it adds a lot of latency...  

Received on Tuesday, 8 December 2009 15:23:13 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:29:46 UTC