- From: Annette Greiner via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Feb 2019 23:22:44 +0000
- To: public-dxwg-wg@w3.org
This is in the PR already, but it would look something like this. Example 12 :dataset-004 rdf:type dcat:Dataset ; dcat:distribution :dataset-004-csv ; dcat:distribution :dataset-004-png ; . :dataset-004-csv rdf:type dcat:Distribution ; dcat:accessService :table-service-005 ; dcat:accessURL <http://example.org/api/table-005> ; dcat:mediaType <https://www.iana.org/assignments/media-types/text/csv> ; . :dataset-004-png rdf:type dcat:Distribution ; dcat:accessService :figure-service-006 ; dcat:accessURL <http://example.org/api/figure-006> ; dcat:mediaType <https://www.iana.org/assignments/media-types/image/png> ; . :figure-service-006 rdf:type dcat:DataAPI ; dct:conformsTo <http://example.org/apidef/figure/v1.0> ; dct:type <https://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/view> ; dcat:endpointDocumentation <http://example.org/api/figure-006/params> ; dcat:endpointURL <http://example.org/api/figure-006> ; dcat:servesDataset :dataset-004 ; . :table-service-005 rdf:type dcat:DataAPI ; dct:conformsTo <http://example.org/apidef/table/v2.2> ; dct:type <https://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/download> ; dcat:endpointDocumentation <http://example.org/api/table-005/capability> ; dcat:endpointURL <http://example.org/api/table-005> ; dcat:servesDataset :dataset-003, :dataset-004 ; I like the detail in the schema.org proposal, though much of what is there is already covered by the various properties of a resource in DCAT. It's been my understanding that the DCAT subgroup did not want to extend the vocabulary to information already contained in API documentation, since we can link to it, and it expands the scope of DCAT otherwise. -- GitHub Notification of comment by agreiner Please view or discuss this issue at https://github.com/w3c/dxwg/issues/432#issuecomment-468071315 using your GitHub account
Received on Wednesday, 27 February 2019 23:22:46 UTC