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...
Best,
Georgi
