Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adopt DCAT accessURL, compressFormat and packageFormat #191

Open
smrgeoinfo opened this issue Dec 9, 2021 · 0 comments
Open

Adopt DCAT accessURL, compressFormat and packageFormat #191

smrgeoinfo opened this issue Dec 9, 2021 · 0 comments
Labels

Comments

@smrgeoinfo
Copy link
Contributor

Current schema:distribution has a schema:DataDownload value that only has a contentURL and encodingFormat property. This does no support clear indication whether the distribution link is to a landing page, feed, SPARQL endpoint, or web application to request data, or is a direct download link to get a file that contains the data.
DCAT solves this problem with dcat:accessURL and dcat:downloadURL.

A direct download link (dcat:downloadURL) might get a file containing data in a format represented by the schema:DataDownload/schema:encodingFormat string, but the dataset might be in a compressed file, or the dataset might be in a data package like Bagit, or a TAR bundle. For machine-actionable processing, it is very useful for the dataset distribution to be explicit about what the download URL is going to get. DCAT solves this problem by adding properties for compressFormat and packageFormat.

I propose that SOSO should add recommendation to use dcat:accessURL, dcat:downlowadURL, dcat:compressFormat and dcat:packageFormat, along with schema:contentURL and schema:encodingFormat.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants