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

Services Use Constraints guidance references datasets #122

Open
archaeogeek opened this issue Oct 10, 2023 · 0 comments
Open

Services Use Constraints guidance references datasets #122

archaeogeek opened this issue Oct 10, 2023 · 0 comments
Labels
Guidance Issues that primarily affect the general or element guidance, not the "normative" parts

Comments

@archaeogeek
Copy link
Member

Purpose and Meaning and Comment text need to change text from 'data' to 'data resource'.
Corresponding element in other standards - again a reference to MD_Identification
Encoding guidelines inconsistency. Guideline 2 refers to the MD_LegalConstraints element whereas Guideline 5 refers to the LegalConstraints element. Suggest MD_LegalConstraints is used in both cases for consistency and accuracy.

@archaeogeek archaeogeek added the Guidance Issues that primarily affect the general or element guidance, not the "normative" parts label Oct 10, 2023
@archaeogeek archaeogeek self-assigned this Sep 5, 2024
archaeogeek added a commit that referenced this issue Sep 6, 2024
Changed references from data to data resource, and confirmed all encoding guidelines refer to MD_LegalConstraints rather than just LegalConstraints. Fixes #122
@archaeogeek archaeogeek moved this from To do to For review in GEMINI issue handling Sep 6, 2024
@archaeogeek archaeogeek removed their assignment Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Guidance Issues that primarily affect the general or element guidance, not the "normative" parts
Projects
Status: For review
Development

No branches or pull requests

1 participant