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

Atom & WFS: data set identifier namespace #124

Open
heidivanparys opened this issue Oct 2, 2019 · 5 comments
Open

Atom & WFS: data set identifier namespace #124

heidivanparys opened this issue Oct 2, 2019 · 5 comments
Assignees

Comments

@heidivanparys
Copy link

This is a copy of inspire-eu-validation/download-service#89 , which hasn't been adressed yet.

In short: requirements 13, 50 and 51 of the INSPIRE Download Services Technical Guidance version 3.1, and the corresponding tests, should be updated.

@josemasensio
Copy link
Contributor

Dear @heidivanparys,

Thank you for your message. We will provide you with an answer as soon as possible.

Best regards.

@MichaelOstling
Copy link

Hi,
What is the final decision on requirement for resource identifier namespace.
Will this be implemented in ETF ?

@fabiovinci
Copy link
Collaborator

Dear @heidivanparys,

it seems the problem you raised is still present.
The changes of the Validator tests require a modification of the TG, could you please open a relative change proposal?
Thanks

@fabiovinci fabiovinci added requires change in TG The solution of the issue requires a change in TG and removed for-2017.4-discussion This issue will be discussed with the sub-group 2017.4 labels Sep 22, 2022
@heidivanparys
Copy link
Author

@fabiovinci This issue slipped my attention, but I created a change proposal now, see INSPIRE-MIF/technical-guidelines#82.

@fabiovinci
Copy link
Collaborator

Since the proposed changes to the TG have been approved and the updated TG has been released, the related changes will soon be implemented in the validator.

@fabiovinci fabiovinci added under development and removed requires change in TG The solution of the issue requires a change in TG labels May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In progress
Development

No branches or pull requests

6 participants