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

Parse the XML files via xmlschema and the XSD definitions #5

Closed
alexamici opened this issue Apr 12, 2021 · 2 comments · Fixed by #11
Closed

Parse the XML files via xmlschema and the XSD definitions #5

alexamici opened this issue Apr 12, 2021 · 2 comments · Fixed by #11
Labels
reafactor Improve code, payback technical debt

Comments

@alexamici
Copy link
Member

alexamici commented Apr 12, 2021

Most metadata are distributed in XML files (e.g. manifest.safe, product/swath and calibration files) and the product zip file contains part of the XSD definition to use.

As the XSD schemas are required when using xmlschema we need a way to always have a set of files. Strategy is:

  1. allow the user to specify a set of XSD files as a mapping from namespace to path to the schema file
  2. look for the distributed schema files based on a predefined product folder structure e.g. top_dir/support/s1-level-1-product.xsd
  3. use a mapping from namespace to shipped schema file
@alexamici
Copy link
Member Author

@alexamici alexamici added the reafactor Improve code, payback technical debt label Apr 15, 2021
@aurghs
Copy link
Member

aurghs commented Apr 21, 2021

I think #11 is the last small step for closing this issue.

@aurghs aurghs linked a pull request Apr 21, 2021 that will close this issue
@aurghs aurghs closed this as completed Apr 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
reafactor Improve code, payback technical debt
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants