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

ISO srv schema imports non-existant schema URLs #73

Closed
JohannaOtt opened this issue Dec 3, 2021 · 9 comments
Closed

ISO srv schema imports non-existant schema URLs #73

JohannaOtt opened this issue Dec 3, 2021 · 9 comments

Comments

@JohannaOtt
Copy link

Hi everybody,

This ISO serviceMetadata.xsd imports two schemas which are not availeble (any longer?) at the indicated schemaLocations: "http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd" and "http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gco/gco.xsd".

This can cause issues when trying to use the apiso metadata schema used in INSPIRE because the problematic schema is recursively imported there as well.

I did not find a contact point at ISO for reporting such issues. Does anyone know where to report it or is there a direct contact between the INSPIRE community and ISO that could be used for that?

Thank you and all the best

Johanna

@heidivanparys
Copy link
Collaborator

heidivanparys commented Dec 3, 2021

All ISO/TC 211 schemas, including annotated documentation, are available at the schema server of ISO/TC 211:

See also https://github.com/ISO-TC211/XML (@ejbleys) for more information.

Regarding a contact point at ISO, there is a standards tracker where you can submit all issues. For more information about the standards tracker, see this presentation and this video by @PeterParslow.

Note that the serviceMetadata.xsd resides on the OGC schema server (@ogcscotts), not on the ISO/TC 211 schema server.

@JohannaOtt
Copy link
Author

@heidivanparys Thank you for your reply. So would you recommend reporting this issue to OGC rather than to ISO?

@heidivanparys
Copy link
Collaborator

I checked again, and I actually think that you should be using the schemas from the ISO schema server directly, see https://schemas.isotc211.org/schemas/19119/.

But yes, for any issues regarding the OGC schema server, you should contact OGC indeed. This is a special case as it concerns schemas related to an ISO standard…

@JohannaOtt
Copy link
Author

JohannaOtt commented Dec 8, 2021

Hi Heidi,

Thank you for your quick replies.

I actually think that you should be using the schemas from the ISO schema server directly, see https://schemas.isotc211.org/schemas/19119/.

As mentioned in my first comment, this issue is occuring when using the apiso schema because it imports these schemas recursively. So I cannot change the schemas being used unfortunately.

But yes, for any issues regarding the OGC schema server, you should contact OGC indeed.

I contacted OGC now via the contact form on their homepage - hope that will help everyone to have an apiso schema available for which all imports are working.

All the best

Johanna

@heidivanparys
Copy link
Collaborator

I actually think that you should be using the schemas from the ISO schema server directly, see https://schemas.isotc211.org/schemas/19119/.

As mentioned in my first comment, this issue is occuring when using the apiso schema because it imports these schemas recursively. So I cannot change the schemas being used unfortunately.

Sorry, yes, you're right, apiso.xsd is only at the OGC server, so you can't use a more recent version from ISO there. I hope you'll get a quick reply from OGC.

@fabiovin
Copy link

fabiovin commented Dec 9, 2021

Hello @JohannaOtt,

I don’t know with what tool you are encountering this issue, because even though the links in the serviceMetadata.xsd are not valid, the apiso.xsd is valid.
It is used by the Validator without problems.

@JohannaOtt
Copy link
Author

@fabiovin I do not doubt that the apiso.xsd is valid but you can for example not load it in hale studio as it is expected that all imported schemas are available.

@fabiovin
Copy link

@JohannaOtt, ok, waiting for a fix by OGC, you can use this draft apiso schema (https://inspire.ec.europa.eu/draft-schemas/inspire-md-schemas-temp/apiso-inspire/apiso-inspire.xsd), we created it when there was a problem with gmd and gmx schemas.
It works in hale studio.

@JohannaOtt
Copy link
Author

@fabiovin Great, thank you for the info!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants