Open enricoboldrini opened 6 years ago
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.
In the meantime an updated version of SeaDataNet community profile has been released. Here are the updated test reports:
I have noticed a modified error message on the validator side in this case: System error in the Executable Test Suite. Please contact a system administrator. Error information: [err:FODC0002] "http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml" (Line 1): Premature end of file. (550/29) It could be related to the recent relocation of ISO official schemas from http to https (most probably the redirect isn't properly followed by the validator).
Based on ISO TS 19139 and XML schema, each gmd:identificationInfo property of gmd:MD_Metadata can contain only one gmd:MD_DataIdentification element (consequently, the TG req 1.2 seems to be unnecessary). If so, the test should be made only to check the first gmd:identificationInfo property, regardless the DataIdentification element contained. Nevertheless, the metadata element SpatialRepresentationType is required in any case.
This is fixed, thank you!
We keep the issue open, until it is also deployed in the production instance of the Reference Validator.
Error returned: Every metadata record must document the spatial representation types used in the dataset, but this record does not have a 'spatialRepresentationType' property.
I'm validating a SeaDataNet XML document, that is a community profile of ISO 19115 metadata (https://www.seadatanet.org/Standards/Metadata-formats/CDI), drafted according to official ISO 19115 rules. Actually, the element is present, and it is to be found inside the sdn:SDN_DataIdentification section (gco:isoType="MD_DataIdentification_Type"). Most likely, the test doesn't recognize extensions from community profiles.