Closed wangf1122 closed 1 year ago
@wangf1122 - I don't believe we want to be modifying the HNAP schema specification as we are not the authoritive source for this data.
I think the fix should be to modifying the following https://github.com/metadata101/iso19139.ca.HNAP/blob/3.12.x/src/main/plugin/iso19139.ca.HNAP/process/source-add.xsl so that it does not use the iso19139.ca's version and instead adds it own custom version with the gmd:scope
@josegar74 - Any suggestion?
I think it should be fixed the xsl, to add the <gmd:scope />
element instead of changing the xsd
. If the element content is not relevant, can be added with empty content, as <gmd:scope />
, what is valid.
This PR is no longer needed and replaced by https://github.com/metadata101/iso19139.ca.HNAP/pull/331
When adding dataset link
the dataquality node was added like this:![image](https://user-images.githubusercontent.com/74916635/168286885-da0a931c-a410-4fc6-bcbf-d769034efe31.png)
The schema validation failed![image](https://user-images.githubusercontent.com/74916635/168287680-a03b9d02-3fff-4882-a2e0-f35f54cb01db.png)
The xsl which is in ISO19139 has no such gmd:scope related code: https://github.com/geonetwork/core-geonetwork/blob/29f9f5e3b9bc390d82e23d75efe29d9a757c8e72/schemas/iso19139/src/main/plugin/iso19139/process/source-add.xsl#L73-L83
So I would like to make this gmd:scope not mandatory in its schema.