- From: Simon Cox via GitHub <sysbot+gh@w3.org>
- Date: Sat, 11 Jul 2020 08:50:44 +0000
- To: public-dxwg-wg@w3.org
DCATv2 has slots for 1-5 1. the `dcat:landingPage` (human readable) and `dcat:endpointURL` (API) are separate if needed 2. `dcterms:conformsTo` shoudl indicate the API standard 3. the data schema and format/mediaType are part of the description of the payload (i.e. the `dcat:Distribution`, using `dcterms:conformsTo` and `dcterms:format` or `dcat:mediaType`) 4. the query model and details are expected to be provided as part of the dcat:endpointDescription 5. ... which might also indicate ranges, etc No model for the value of `endpointDescription` was provided, since it was expected that this would be specified by the API standard, so 5. might not be covered but this is out of scope for DCAT itself. I agree that the directions of some of the relationships between Dataset, Distribution and DataService might not be quite what you were expecting, but I think there are slots available. -- GitHub Notification of comment by dr-shorthair Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1240#issuecomment-657017780 using your GitHub account
Received on Saturday, 11 July 2020 08:50:46 UTC