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.

Sign up for GitHub

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

Jump to bottom

Typos in examples 3.4 and 3.5: "gco:distance" #70

Closed
thomruhl opened this issue Aug 22, 2022 · 0 comments · Fixed by #116
Closed

Typos in examples 3.4 and 3.5: "gco:distance" #70

thomruhl opened this issue Aug 22, 2022 · 0 comments · Fixed by #116
Labels
for JRC The change proposal is to be handled by the JRC.
Milestone
2023.2

Comments

@thomruhl
Copy link

While the guidelines correctly mention the "gco:Distance" class, it is mentionned as "gco:distance" in the examples.

Change proposal description

I suggest to fix the issue which occurs multiple times in the examples, and capitalize the "gco:Distance" class wherever it should be.

Addressed TG

Technical Guidance for the implementation of INSPIRE dataset and service
metadata based on ISO/TS 19139:2007

Location

Section 3.1.2.3: Spatial resolution
Examples 3.4 and 3.5 (page 70-71)

##Screenshot of: TG Requirement 1.5: metadata/2.0/req/datasets-and-series/spatial-resolution (page 70)
TG

##Screenshot of example 3.5 (page 71)
Example35
@fabiovinci fabiovinci added the for JRC The change proposal is to be handled by the JRC. label Aug 31, 2022
@fabiovinci fabiovinci added this to the 2023.2 milestone Mar 1, 2023
fabiovinci added a commit that referenced this issue Jul 19, 2023
@fabiovinci
Fix typos in examples 3.4 and 3.5
0274bc2 
Fix typos in examples 3.4 and 3.5: "gco:distance".
Related issue #70
@fabiovinci fabiovinci mentioned this issue Jul 19, 2023
Merged
@fabiovinci fabiovinci linked a pull request Jul 19, 2023 that will close this issue
Fix typos in examples 3.4 and 3.5 #116
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
for JRC The change proposal is to be handled by the JRC.
Projects
None yet
Milestone
2023.2
Development

Successfully merging a pull request may close this issue.

Fix typos in examples 3.4 and 3.5 INSPIRE-MIF/technical-guidelines
2 participants
@fabiovinci @thomruhl