The issue has been emailed:
- Time sent: 21/Mar/16 4:28 PM
- To: pasquale.vitale@eng.it
- with subject: *(
HELP-6158) [Fiware-tech-help] [CKAN] CKAN and Linked Open Data *
Hi Pasquale,
> I have installed only the dcat plugin.
Great, if you only want to produce RDF that the only one you'll need. If you want to import (harvest) RDF from other sources you'll need dcat_rdf_harvester (and the harvester extension).
> I put in my ckan server two datasets (catalog.json and catalog.rdf downloaded from this link https://github.com/ckan/ckanext-dcat/tree/master/examples).
> How can I check that it works?
You don't need to provide any existing RDF file. RDF serializations are generated on the fly from CKAN's internal metadata. You can access the RDF version of dataset visiting:
http://yourckaninstance.com/dataset/
{dataset_name}.rdf
or
http://yourckaninstance.com/dataset/{dataset_name}
.ttl
http://yourckaninstance.com/dataset/
{dataset_name}
.jsonld
This is an example from the CKAN demo site:
http://demo.ckan.org/dataset/newcastle-city-council-payments-over-500.rdf
There's also a catalog wide endpoint:
http://demo.ckan.org/catalog.rdf
Please check the ckanext-dcat docs for more details.
Hope this helps,
Adrià
The issue has been emailed:
HELP-6158) [Fiware-tech-help] [CKAN] CKAN and Linked Open Data *Hi Pasquale,
The official RDF support for CKAN is currently provided by the DCAT extension:
https://github.com/ckan/ckanext-dcat
Installing it and enabling it will provide a customizable RDF serialization for all datasets [1]. This serialization can be customized writing profiles [2] for your own needs. The default profile is compatible with DCAT-AP 1.1.
Note that the semantic output in RDF refers to the metadata of the datasets, not the actual data contained on the DataStore.
Hope this helps,
Adrià
[1] https://github.com/ckan/ckanext-dcat#rdf-dcat-endpoints
[2] https://github.com/ckan/ckanext-dcat#profiles