How to describe different information elements for searching for and binding to a service? In this case, it would be useful to provide the minimal information needed for connecting to a service.
For furhter resolving this issue, please redirect to the new issue created after the DCAT-AP workshop in Rome (13/05/2016): https://joinup.ec.europa.eu/discussion/dt2-service-based-data-access
This issue has been reported by Uwe Voges: http://joinup.ec.europa.eu/mailman/archives/dcat_application_profile/2016-February/000381.html
Component
DocumentationCategory
improvement
Login or create an account to comment.
Comments
Indeed, that's what I propose, i.e. DCAT is a vocabulary that aims to describe datasets, how to access those datasets is beyond the scope of this vocabulary, thus vocabularies dedicated for this scope should be considered.
The possible protocols or the vocabularies to be used may not be exactly the ones that were used in the case of RML. I mean these are all indicative cases applicable for RML, but it is not meant to provide a complete list of such vocabularies. If such an approach is followed, the working group may decide upon suggested vocabularies.
Dear colleagues
After the today virtual meeting, I tried to follow the Andrea Perego suggestion published here
https://www.w3.org/2016/11/sdsvoc/SDSVoc16_paper_27#modelling-service-a… a:Dataset a dcat:Dataset; dcat:distribution [ a dcat:Distribution ; dct:title "GMIS - WMS (9km)"@en ; dct:description "Web Map Service (WMS) - GetCapabilities"@en ; dct:license <http://publications.europa.eu/resource/authority/licence/COM_REUSE> ; dcat:accessURL <http://gmis.jrc.ec.europa.eu/webservices/9km/wms/meris/?dataset=kd490> ; # The distribution points to a service dct:type <http://publications.europa.eu/resource/authority/distribution-type/WEB_…; ; # The service conforms to the WMS specification dct:conformsTo <http://www.opengis.net/def/serviceType/o In practical implementation this means to set in CKAN (my platform) some attributes that we extended in order to implement DCAT-AP (IT) A practical example on our catalogue (through the CKAN API and through the DCAT-AP JSONLD API ) The values are inserted manually. "URL" is the "AccessURL" type: "WEB_SERVICE" url: "http://www.comune.pomarolo.tn.it/api/opendata/v2/content/search/classes 'event'", license_id: "cc-by" conforms_to: "compliant to REST/JSON", You could see the result here http://dati.trentino.it/api/3/action/package_show?id=eventi-del-comune-… http://dati.trentino.it/dataset/eventi-del-comune-di-pomarolo.jsonld Is that dataset compliant in that way as "service-based access"? Anything about the "size" attribute?