[ckan-discuss] Linked Data and the DataHub (and CKAN generally) DataStore(s)

Mon May 7 23:59:54 BST 2012

[Forwarding thread parts ...]

On 27 April 2012 16:20, Richard Cyganiak <richard at cyganiak.de> wrote:
> Hi Rufus,
>
> Sorry for the delay in responding.
>
> Yes, JSON-LD could be a good way of publishing CKAN metadata in a way that can be consumed directly by RDF apps.

This is *not* about metadata. It's about storing linked *data* in the
CKAN / DataHub DataStore:
<http://docs.ckan.org/en/latest/datastore.html>

> I don't quite understand what it means to put this metadata into a datastore table. How does the datastore table relate to the dataset that is being described? Is this somehow like an additional resource associated with the dataset? Or is it something completely separate?

It's structured storage associated with the resource. See the short
slides intro at the top of
<http://docs.ckan.org/en/latest/datastore.html>

> Who would put the JSON-LD records into the datastore?

Someone publishing linked data.

> How would an app would discover the JSON-LD data for a given dataset? Would you assume there's a “top-level” JSON-LD object or API that exposes the catalog (the list of datasets)?

For a given resource the JSON-LD data would be available via the
DataStore Data API located at a standard location, at present:

http://datahub.io/api/data/{resource-id...

> Sorry for the fuzzy questions -- it's a very big design space!

Not at all. Hope above has clarified a little bit.

Rufus