-
Notifications
You must be signed in to change notification settings - Fork 47
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
Comments
A 'Distribution' describes a file representation or serialization of a Dataset. This is related to the introduction of services to DCAT raised primarily in #172, #180, #181 |
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." |
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." |
Probably that should say "which in turn may serve dcat:Distributions |
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. |
@agreiner - so we can close this now? |
yes, I think so. |
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?
The text was updated successfully, but these errors were encountered: