[ECODP-dev] first RDF assesment

[David Raznick]

Hello Bert




On 9 August 2013 16:05, Bert Van Nuffelen <bert.van.nuffelen at tenforce.com>wrote:

> Hi David,
>
> here is a first assesment of the RDF produced by the current version of
> the EU ODP ckan
>
> * [Major] correct publisher URI
>   CKAN generates this:
>   <dct:publisher><skos:Concept rdf:about="
> http://publications.europa.eu/resource/authority/corporate-body/cnect
> "/></dct:publisher>
>
>   but the correct URI to use is
> http://publications.europa.eu/resource/authority/corporate-body/cnect
>
> These urls look the same to me.



>   In the po-corporate-bodies.json used to instantiate the right URI is
> given:
>
>  {
>         "term" : { "type": "uri", "value": "
> http://publications.europa.eu/resource/authority/corporate-body/CNECT" },
>         "label" : { "type": "literal", "value": "Generaldirektion
> Kommunikationsnetze, Inhalte und Technologien" } ,
>       "language" : { "type": "literal" , "value" : "da" }
>       },
>
>
> * [Minor] better is to specify this line with the next format in rdf/xml.
> Otherwise one additionally declares that the URI is a skos:Concept, which
> is (a) redundant, (b) not the task of the transformation.
>    <dct:publisher rdf:resource="
> http://publications.europa.eu/resource/authority/corporate-body/cnect"/>
>
> * [Major] use the correct URI's for the geospatial coverage domain:
>   CKAN generates the same triple:
>   <dct:spatial><skos:Concept rdf:about="
> http://publications.europa.eu/resource/authority/ntu/h"/></dct:spatial>
>
>   for each country
>
>   e.g. <http://publications.europa.eu/resource/authority/country/WSM>
>
>   present in the json po-countries.json: example extract
>
> {
>         "term": { "type": "uri" , "value": "
> http://publications.europa.eu/resource/authority/country/ABW" } ,
>         "label": { "type": "literal" , "value": "Aruba" } ,
>         "language": { "type": "literal" , "value": "fi" }
>       } ,
>
>
>
> * [Minor] see rdf/xml notation
>
> * [major] Catalog Record
>    missing values for
>    <dct:modified/>
>    <dct:issued/>
>
> * missing translations for the translatable fields (description, title)
>
>
> * [major] DCAT Catalog Record is not part of the dcat:Dataset but a
> separate piece of information
>
> ------------------
> related topics:
>
> * contact_webpage CKAN field is that supported?
>
Yes

> * documentation on how to handle a visualisation item
>
>
I think I have fixed what I understand to be the issues here.  Attached is
an example I have found that covers most of the points.  Could you look at
it and review it please

Thanks

David








> best regards,
>
> Bert
>
> --
> Bert Van Nuffelen
>
> Semantic Technologies Software Architect at TenForce
> www.tenforce.be
>
> Bert.Van.Nuffelen at tenforce.com
> Office: +32 (0)16 31 48 60
> Mobile:+32 479 06 24 26
> skype: bert.van.nuffelen
>
> _______________________________________________
> Ecodp-dev mailing list
> Ecodp-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ecodp-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.okfn.org/mailman/private/ecodp-dev/attachments/20130814/6a37cfc8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ccm.rdf
Type: text/xml
Size: 6102 bytes
Desc: not available
URL: <https://lists.okfn.org/mailman/private/ecodp-dev/attachments/20130814/6a37cfc8/attachment.xml>