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

TG Metadata v2.1.0 - duplication in the numbering of TG Recommendations #32

Closed
sMorrone opened this issue Feb 2, 2022 · 0 comments · Fixed by #61
Closed

TG Metadata v2.1.0 - duplication in the numbering of TG Recommendations #32

sMorrone opened this issue Feb 2, 2022 · 0 comments · Fixed by #61
Labels
for JRC The change proposal is to be handled by the JRC.
Milestone

Comments

@sMorrone
Copy link
Collaborator

sMorrone commented Feb 2, 2022

Change proposal description

Fix typos in the numbering of TG recommendations

Addressed TG

http://inspire.ec.europa.eu/id/document/tg/metadata-iso19139/2.1.0

Location

Section 3.1.2:
TG Recommendation 1.1: metadata/2.0/rec/datasets-and-series/md-element-id
TG Recommendation 1.1: metadata/2.0/rec/datasets-and-series/use_md_identifier
Section 3.2.1
TG Recommendation 2.1: metadata/2.0/rec/isdss/source-crs
TG Recommendation 2.1: metadata/2.0/rec/isdss/
TG Recommendation 2.2: metadata/2.0/rec/isdss/srs-using-geographic-identifiers
Section 3.2.4
TG Recommendation 2.2: metadata/2.0/rec/isdss/topological-consistency-measure-name

Section 4.3
Missing TG Recommendations number 5.1, 5.2, 5.3 (directly starting from TG Recommendation 5.4).

Proposed solution

Update numbering of all TG Recommendations to ensure consistency

Pull request

To be provided

@sMorrone sMorrone added this to the 2022.2 milestone Feb 3, 2022
@fabiovinci fabiovinci added the for JRC The change proposal is to be handled by the JRC. label Mar 14, 2022
@fabiovinci fabiovinci linked a pull request Jul 27, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for JRC The change proposal is to be handled by the JRC.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants