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

Problem when validating ATOM download service via INSPIRE VALIDATOR #1085

Open
pablobarreira opened this issue Jun 4, 2024 · 5 comments
Open
Labels
solved Solution developed and accepted, not yet deployed
Milestone

Comments

@pablobarreira
Copy link

Hello,

This is Pablo Barreira from Spanish Agricultural Guarantee Fund (Ministry of Agriculture). First of all thank you for solving the problem with our certificate.#1084.

Related with this, we finally perfomed the validation of our ATOM download service (https://www.fega.gob.es/atom/es.fega.sigpac.xml this morning. Among the three main failing issues (two of them we can solve them by ourselves), there is one which we want to ask you about. Here is the complete report (https://inspire.ec.europa.eu/validator/test-run/details.html?id=EIDdedc6cc8-809f-465b-a5e1-560602149228). And we want to ask you specifically about this one:
image

We think this error might be due to an error in the validator when it verifies requirement 42:
TG Requirement 42: The OpenSearch description shall contain a 'Url' element that describes a template URL for the Describe Spatial Data Set operation. This template shall accept the INSPIRE parameters 'spatial_dataset_identifier_code', 'spatial_dataset_identifier_namespace' and the OpenSearch 'language' parameter. The 'Url' element shall have an attribute 'type' with a value of 'application/atom+xml' or 'application/xml' or 'text/xml' and an attribute 'rel' with the value 'describedby'.

The cited element is whithin https://www.fega.gob.es/atom/osd.xml, that adresses the requirement is this one:

image

Could you please help us to solve this issue? Thank you in advance for your help.

@github-actions github-actions bot added this to To do in Validator issues Jun 4, 2024
@fabiovinci fabiovinci self-assigned this Jun 4, 2024
@pablobarreira
Copy link
Author

Dear all, have you any kind of answer for the question above?
Thank you in advance for your help.

@fabiovinci
Copy link
Collaborator

Dear @pablobarreira,

I confirm that your service is fine and should not result in an error for Requirement 42.
We are working to resolve the issue and will notify you when the solution is available for testing in the staging environment.

@fabiovinci fabiovinci assigned dperezBM and unassigned fabiovinci Jul 2, 2024
@MarcoMinghini MarcoMinghini moved this from To do to In progress in Validator issues Jul 2, 2024
@fabiovinci fabiovinci added this to the v2024.2 milestone Jul 5, 2024
@fabiovinci fabiovinci assigned pablobarreira and unassigned dperezBM Jul 9, 2024
@fabiovinci fabiovinci added ready for testing Solution provided to reporter or developed & deployed in staging (or beta), waiting for testing and removed under development labels Jul 9, 2024
@MarcoMinghini MarcoMinghini moved this from In progress to Staging: for acceptance in Validator issues Jul 9, 2024
@fabiovinci
Copy link
Collaborator

Dear @pablobarreira,

the fix for this issue is available in the staging instance.

I tested your service and it is 100% valid (see report https://staging-inspire-validator.eu-west-1.elasticbeanstalk.com/etf-webapp/test-run/index.html?id=EID9e91e340-7c92-445a-8d4f-cbddcc0b52da).

Could you please conduct additional tests and confirm? Thanks

@pablobarreira
Copy link
Author

Dear @fabiovinci .

I have performed the test right now in the staging environment and i get the same as you got. It is now solved!
Thank you so much for your help.

Would you mind to tell us when will this fix pass from the staging environment to the reference validator?

Thank you!

@fabiovinci
Copy link
Collaborator

Dear @pablobarreira,

thank you for confirmation, this fix will be available in the production instance in the coming days.

@fabiovinci fabiovinci added solved Solution developed and accepted, not yet deployed and removed ready for testing Solution provided to reporter or developed & deployed in staging (or beta), waiting for testing labels Jul 9, 2024
@MarcoMinghini MarcoMinghini moved this from Staging: for acceptance to Staging: in release planning in Validator issues Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solved Solution developed and accepted, not yet deployed
Projects
Validator issues
  
Staging: in release planning
Development

No branches or pull requests

3 participants