Schema Validation of ISO 19115 community profile XML document

[enricoboldrini]

Error returned: Cannot find the declaration of element 'gmd:MD_Metadata'.

I'm validating a SeaDataNet XML document, that is a community profile of ISO 19115 metadata, drafted according to official ISO 19115 rules.
This document should be validated using the schema(s) specified in its xsi:schemaLocation. These schemas are in turn importing the official ISO/OGC schemas (http://schemas.seadatanet.org/Standards-Software/Metadata-formats/SDN2_CDI_ISO19139_10.0.1.xsd), as well as defining some community elements.
In particular, the gmd:MD_Metadata element definition should be correctly found in the imported ISO AP schemas: http://www.isotc211.org/schemas/2005/gmd/gmd.xsd.

• Test Report: http://inspire-sandbox.jrc.ec.europa.eu/etf-webapp/v2/TestRuns/EIDcb80f9ea-9d37-463a-9aaf-b45806194b35.html
• Assertion URI: http://inspire-sandbox.jrc.ec.europa.eu/etf-webapp//v2/TestRuns/EIDcb80f9ea-9d37-463a-9aaf-b45806194b35.html?lang=en#EID6885e93c-cfd6-4f9c-8220-85e47f913959
• Referenced file: https://s3.amazonaws.com/essi.documents/seadatanet-test-2.xml

[enricoboldrini]

Hello, I've noticed the planned tag has been added. Can you elaborate more on the planning schedule for this issue? Thank you in advance. Please let me know if more info are needed.

[enricoboldrini]

In the meantime an updated version of SeaDataNet community profile has been released. Here are the updated test reports:

• Test Report: http://inspire-sandbox.jrc.ec.europa.eu/etf-webapp/v2/TestRuns/EID1f2bbb8d-7789-42d8-b9b6-27ff5a23337c.html
• File used for validation: https://www.seadatanet.org/content/download/2602/file/CDI_ISO19139_full_example_11.0.0.xml

[enricoboldrini]

Hello, this error is still present. The profile schema extends the official ISO 19139, so all the gmd element declarations should be correctly found. You can try validating it with an editor (e.g. Oxygen XML Editor) and it will validate fine.

[MarcoMinghini]

Following the discussion in https://github.com/inspire-eu-validation/community/issues/45, we can mark the issue as solved. It will be deployed in the reference validator (production instance) soon.

[enricoboldrini]

The workaround proposed here: inspire-eu-validation/community#45 doesn't work anymore. Something has changed in the past few days in the staging validator.
The workaround was to define schema location in the following way: xsi:schemaLocation="http://www.seadatanet.org http://schemas.seadatanet.org/Standards-Software/Metadata-formats/SDN2_CDI_ISO19139_11.0.0.xsd http://www.isotc211.org/2005/gmd http://schemas.opengis.net/iso/19139/20060504/gmd/gmd.xsd"
The error raisen is Invalid content was found starting with element '{"http://www.seadatanet.org":SDN_HierarchyLevelNameCode}'. One of '{"http://www.isotc211.org/2005/gco":CharacterString}' is expected. schema validation error(s).
Something is changed also in the official validator, as it hangs with unknown error currently.
The file is valid according to its schema, and imports official ISO 19115 schemas.

[enricoboldrini]

Just a little update: in the staging validator the error persists, while the official validator works as expected now.

[danielnavarrogeo]

Dear @enricoboldrini

Thank you for your comments.

The XML schema validation in metadata 1.3 in staging instance works now as the official instance.

Could you please try again in staging instance?

We are working on some issues related to XML schema validation for metadata 1.3. Therefore, some changes might be expected.

I would like to remind that support for MD TG 1.3 will stop at the end of the year. Then, it is recommend to use MD TG 2.0.

Regards

[enricoboldrini]

Dear @danielnavarrogeo,

thank you very much for the follow up and info. I confirm that currently validation is successful in both environments. Regarding removal of support for MD TG 1.3 in favor of MD TG 2.0: does it mean that ISO schema version 20060504 (the one used by OGC IS AP ISO) will not be validated by the ETF-validator from next year? (in favor of version 20070417?)

Thank you very much in advance for the info,

Enrico

[fabiovin]

Dear @enricoboldrini,

please note that the OGC IS AP ISO schema (http://schemas.opengis.net/csw/2.0.2/profiles/apiso/1.0.0/apiso.xsd) already make use of the OGC version 2007-04-17 of the gmd namespace, and consequently of the GML version 3.2.1.

[enricoboldrini]

Dear @fabiovin,

thank you for the hint, I didn't noticed that. It seems OGC changed from 2006 to 2007 schemata in the AP ISO bug fix version 1.0.1 (2018-03-21).
(as far as I can understand from here: http://schemas.opengis.net/csw/2.0.2/profiles/apiso/ReadMe.txt)
Summarizing, the suggestion is to upgrade to 2007 schemata because they will be the only ones supported from next year. Is it correct?

Thank you again,

Enrico

[fabiovin]

Dear Enrico,
this is not completely correct!
The transition period, from MD version 1.3 to version 2.0, will end in December. For this reason, support for MD TG 1.3 will stop.

In any case, the MD TG 2.0 provides for the use of gmd.xsd schemas which refer to the GML 3.2.0 version (TG Requirement C.1). For instance, http://www.isotc211.org/2005/gmd/gmd.xsd or http://schemas.opengis.net/iso/19139/20060504/gmd/gmd.xsd (see footnotes on page 28). Please note that in footnote 14 there is an error since the cited schema refers to GML 3.2.0 version and not to 3.2.1.

[enricoboldrini]

O.k., perfect. Thank you for the follow up @fabiovin, that's appreciated.

Enrico

[josemasensio]

Dear @enricoboldrini,

Does the provided solution work?

Best regards.

[enricoboldrini]

Dear @josemasensio yes it works, thank you!

Enrico

[josemasensio]

Dear @enricoboldrini,

Glad to hear that. We will mark the issue as solved.

Best regards.