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

accessService property of a Distribution #434

Closed
agreiner opened this issue Oct 3, 2018 · 7 comments
Closed

accessService property of a Distribution #434

agreiner opened this issue Oct 3, 2018 · 7 comments

Comments

@agreiner
Copy link
Contributor

agreiner commented Oct 3, 2018

I find it confusing that we define a property of a Distribution to point to a thing called an accessService, which is a DataDistributionService. A DataDistributionService is a service that serves data through an API, no? But a Distribution is now defined not to include APIs, so why does it have an accessService property?

@dr-shorthair
Copy link
Contributor

A 'Distribution' describes a file representation or serialization of a Dataset.
It is available directly from the dcat:downloadURL
It is available from a service endpoint at dcat:accessURL
It is available through a service described in a DCAT catalogue as indicated by dcat:accessService..

This is related to the introduction of services to DCAT raised primarily in #172, #180, #181
There was detailed discussion in May when it was resolved.

@agreiner
Copy link
Contributor Author

agreiner commented Oct 3, 2018

I think my confusion is coming from the Note where we say "Under the revised scope, instances of type dcat:Distribution SHOULD be limited to representations of datasets which might be transported as files, and SHOULD NOT be used for data services such as APIs or feeds." Is it the case that a distribution is meant to still be available via an API or feed? If so, the fix is relatively easy. "Data services including APIs and feeds SHOULD be described using instances of type dcat:DataService or dcat:DataDistributionService, which in turn serve dcat:Distributions."

@agreiner
Copy link
Contributor Author

agreiner commented Oct 3, 2018

Sorry to bring up an old issue, but it was only resolved in the DCAT subgroup. It's only now that the plenary is being asked to look at the document "with fresh eyes."

@agreiner
Copy link
Contributor Author

agreiner commented Oct 3, 2018

Probably that should say "which in turn may serve dcat:Distributions

@dr-shorthair
Copy link
Contributor

PR #440 has

Under the revised scope, instances of type dcat:Distribution SHOULD be limited to representations of datasets which might be transported as files, and SHOULD NOT be used for data services such as APIs or feeds. Data services including APIs and feeds SHOULD be described using instances of type dcat:DataService whose sub-class dcat:DataDistributionService MAY serve dcat:Distributions.

@davebrowning
Copy link
Contributor

@agreiner - so we can close this now?

@agreiner
Copy link
Contributor Author

yes, I think so.

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

No branches or pull requests

4 participants