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

DCAT: Including links to Requirements in UCR document #744

Closed
andrea-perego opened this issue Feb 7, 2019 · 4 comments
Closed

DCAT: Including links to Requirements in UCR document #744

andrea-perego opened this issue Feb 7, 2019 · 4 comments
Labels
dcat due for closing Issue that has been addressed and it is going to be closed if there are no objection within 6 days Editorial

Comments

@andrea-perego
Copy link
Contributor

Currently, the DCAT spec refers to requirements by linking to the corresponding GH issue.

I wonder whether we should also link to the actual Reqs in the UCR document.

Also, what about having an appendix with a summary showing how the new version of DCAT addresses the UCR? I was thinking of something similar to:

https://www.w3.org/TR/dwbp/#requirements

@andrea-perego andrea-perego added this to To do in DCAT revision via automation Feb 7, 2019
@andrea-perego
Copy link
Contributor Author

I have just realised DQV does have a specific section listing the addressed requirements from DWBP UCRs:

https://www.w3.org/TR/vocab-dqv/#requirements

@davebrowning
Copy link
Contributor

We have traceability from the changes through the github issues to the UCR since every UCR requirement has a corresponding issue. Going that way means that anyone interested can see any issue discussion (or link to PR for actual changes) so its a 'richer' experience. So I'm going to suggest we close this in part to provoke further discussion of the topic so we have clear consensus.

@davebrowning davebrowning added the due for closing Issue that has been addressed and it is going to be closed if there are no objection within 6 days label Sep 23, 2019
@riccardoAlbertoni
Copy link
Contributor

+1 to close

@andrea-perego andrea-perego added this to the DCAT2 ratification milestone Sep 26, 2019
@davebrowning
Copy link
Contributor

What we have in the CR now seems to have passed muster (and this has been marked due for closing for a while now). Will close, since I doubt we have bandwidth/effort available to add a new section at this stage unless there is a strongly voiced need... in which case we re-open/create a new issue

DCAT revision automation moved this from To do to Done Oct 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dcat due for closing Issue that has been addressed and it is going to be closed if there are no objection within 6 days Editorial
Projects
DCAT revision
  
Done
Development

No branches or pull requests

3 participants