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

Metadata guidance rules [RMDG] #69

Open
jpullmann opened this issue Jan 18, 2018 · 6 comments
Open

Metadata guidance rules [RMDG] #69

jpullmann opened this issue Jan 18, 2018 · 6 comments

Comments

@jpullmann
Copy link

Metadata guidance rules [RMDG]

Ability to express 'guidance rules' or 'creation rules' in DCAT


Related use cases: Metadata Guidance Rules [ID42] 
@makxdekkers
Copy link
Contributor

makxdekkers commented Feb 7, 2018

The European DCAT-AP includes the property dct:conformsTo for Dataset referring to "an implementing rule or other specification" which seems sufficiently broad to also include guidance and creation rules.

@agbeltran
Copy link
Member

While the 'profile-guidance' label was removed from this issue and the 'dcat' label was added instead, the associated use case for this requirement refers to profiles rather than DCAT.

For DCAT, we have added dct:conformsTo for dcat:Resource (and therefore for dcat:Dataset, see here), dcat:CatalogRecord(see here) and for dcat:Distribution (see here)

@kcoyle given that this was your use case, can you confirm that we can close the issue (if related to DCAT) or change back the label to profile-guidance if it correspond to that document instead?

@kcoyle
Copy link
Contributor

kcoyle commented Mar 2, 2019

I'm adding profile-guidance back in. It also logically is covered by the profiles vocabulary but I think they already have that covered in the roles. This will remind us that a paragraph about the kinds of guidance and usefulness thereof should be added to profgui.

@davebrowning davebrowning added this to the DCAT Backlog milestone Mar 14, 2019
@andrea-perego
Copy link
Contributor

As there has been no further discussion on this issue, I propose to close it.

@andrea-perego andrea-perego added the due for closing Issue that is going to be closed if there are no objection within 6 days label Oct 28, 2020
@andrea-perego andrea-perego moved this from To do to In progress in DCAT Sprint: Requirements Nov 3, 2020
@aisaac
Copy link
Contributor

aisaac commented Nov 15, 2020

Why not just removing the DCAT tag from it, considering that it may be relevant for the other work (if we come back to it)?

@andrea-perego
Copy link
Contributor

Why not just removing the DCAT tag from it, considering that it may be relevant for the other work (if we come back to it)?

Done.

@andrea-perego andrea-perego removed this from To do in DCAT revision Nov 25, 2020
@andrea-perego andrea-perego removed this from In progress in DCAT Sprint: Requirements Nov 25, 2020
@andrea-perego andrea-perego removed the due for closing Issue that is going to be closed if there are no objection within 6 days label Mar 13, 2021
@andrea-perego andrea-perego modified the milestones: DCAT3 2PWD, DCAT3 3PWD May 4, 2021
@andrea-perego andrea-perego modified the milestones: DCAT3 3PWD, DCAT3 4PWD Jan 26, 2022
@andrea-perego andrea-perego removed this from the DCAT 3 4PWD milestone Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

8 participants