- From: Stephen Richard via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Apr 2020 16:59:40 +0000
- To: public-dxwg-wg@w3.org
I think the distribution of interest is via a WebAPI, and the metadata needs to provide a machine-actionable representation of the resolvable URI template, that includes (at least via links) an explanation of the parameters in the template. Currently: - dcat:downloadURL appears to implement the simple get a file containing the dataset - dcat:accessURL is URL to get to a landing page or other web location that will require use interaction to obtain the desired resource representation. - dcat:accessService has a value that is a dcat:DataService resource that should include sufficient information for a machine agent to present user (human or automaton) with a way to get the data. This is where the current schema.org discussions on how to represent a WebAPI become important. I hope dcat v3 can provide some logically coherent guidance on this to formalize the loosy-goosy schema.org stuff... :) . see https://github.com/schemaorg/schemaorg/issues/2340 https://github.com/schemaorg/schemaorg/issues/2342 https://github.com/earthcubearchitecture-project418/p419dcatservices https://www.w3.org/TR/vocab-dcat-2/#Class:Data_Service (where is the URI template??) [Machine Readable Web APIs with Schema.org](https://www.sciencedirect.com/science/article/pii/S1877050918316302) from https://github.com/schemaorg/schemaorg/issues/1423#issuecomment-583157131 Some other efforts along these lines: EarthCube Resource Registry, [API resource type](https://github.com/earthcubearchitecture-ecresourcereg/infomodel/blob/ba3823bf015363fc7793c0724772b2317848cd51/SyntaxForTabularResourceDescriptions.md#service-interchange-format-interfaceapi) [Discussion of Machine actionable Links](http://usgin.github.io/usginspecs/ContentModelForLinks.htm), somewhat dated, but covers a lot of the content information that needs to be accounted. Example schema.org JSON-LD: [CHORDS](https://github.com/earthcubearchitecture-ecresourcereg/infomodel/blob/c67500b5da73c2faf330072b4e7f897f03b160ad/examples/Interface-ChordsWebAPIv2-SDO.json) [IRIS data](https://github.com/earthcubearchitecture-ecresourcereg/infomodel/blob/4b7cdaf408522d03edc0f096708103cc17a451e7/examples/Service-IRIS-fsdnEvent-JSON.json) [Template for service description](https://github.com/earthcubearchitecture-ecresourcereg/infomodel/blob/4b7cdaf408522d03edc0f096708103cc17a451e7/examples/ECRRTemplateSDO-Service-v2.JSON), using [potential action](https://github.com/ESIPFed/science-on-schema.org/blob/a1f2d30cf660204e8d93b58a695e455e2f13ea53/guides/Dataset.md#accessing-data-through-a-service-endpoint) There's a lot of interest in this in the science data community! -- GitHub Notification of comment by smrgeoinfo Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1230#issuecomment-613561157 using your GitHub account
Received on Tuesday, 14 April 2020 16:59:42 UTC