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

Invalid schema at https://schemas.isotc211.org/19115/-3/md2/2.0/md2.xsd #31

Closed
ronaldtse opened this issue Apr 10, 2020 · 8 comments
Closed
Assignees
Labels
bug Something isn't working

Comments

@ronaldtse
Copy link
Contributor

From Mr. Wern Yir Tsai:

I open the URL (https://schemas.isotc211.org/19115/-3/md2/2.0/md2.xsd) directly with the XML software,
the XML software shows the error message as follows.
"The schema doesn't appear to be valid by itself."
"File https://schemas.isotc211.org/19115/-3/gco/1.0/baseTypes2014.xsd is not valid."
(Please see the attached file: " 1-md2 is invalid.png ")

But I verify the "baseTypes2014.xsd" , it is valid.
(Please see the attached file: " 2-baseTypes2014 is valid.png " )

Would you mind checking the "md2.xsd" if it has any error between the linked schemas ?

2-baseTypes2014 is valid

1-md2 is invalid

@ronaldtse ronaldtse added the bug Something isn't working label Apr 10, 2020
@PeterParslow
Copy link

Oxygen fails to validate them, with a different reason - an HTTPS certificate issue:

image

@PeterParslow
Copy link

More usefully, I remember this from XMLSpy years ago - it sometimes gets in a muddle with all the circular imports, when it thinks it has detected some kind of clash between two different definitions of the same thing.

Although here the message is claiming the gco:nilReason is declared twice in the same file - presumably it hasn't coped with that file being imported twice.

Perhaps one of the files, somewhere, is using 'import' where it should be 'include' (or the other way round!). Not sure how to easily check that across all the files.

@ejbleys
Copy link
Contributor

ejbleys commented Apr 14, 2020 via email

@PeterParslow
Copy link

I had Oxygen set to use Xerces; set to Saxon gives the same certificate error. But perhaps the question wasn't addressed to me....

@ejbleys
Copy link
Contributor

ejbleys commented Apr 14, 2020 via email

@PeterParslow
Copy link

PeterParslow commented Apr 14, 2020 via email

@ejbleys
Copy link
Contributor

ejbleys commented Apr 14, 2020 via email

@ejbleys
Copy link
Contributor

ejbleys commented Oct 31, 2024

problem seems .to have been resolved

@ejbleys ejbleys closed this as completed Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants