Hi Jose,
Thank you very much. That answered question 2, and supports my assumption regarding question 1.
Best regards,
Johannes Echterhoff
Von: Jose Garcia [mailto:jose.garcia@…444…]
Gesendet: Dienstag, 30. Januar 2018 13:57
An: Johannes Echterhoff <echterhoff@...1647...>
Cc: geonetwork-users@lists.sourceforge.net
Betreff: Re: [GeoNetwork-users] Schematron validation - some questions
Hi Johanes
See feedback inline.
Regards,
Jose GarcÃa
On Tue, Jan 30, 2018 at 12:29 PM, Johannes Echterhoff <echterhoff@...1647...<mailto:echterhoff@…1647…>> wrote:
Hello,
While reviewing the Schematron validation capabilities of GeoNetwork, some questions came up. I hope that someone here can help answer them.
1. Does GeoNetwork v2.8.0 (yes, I'm really interested in this rather old version 
) support Schematron with queryBinding="xslt2"? Looking at the schematron-rules-inspire.xsl in the iso19139 schema plugin, that appears to be the case, since that XSLT has version=2.0. Also, schematron-rules-inspire.sch in the schema-plugins repository (branch 2.8.x) [1] has queryBinding="xslt2".
Schematron support has no change much over the time. I'm not really sure, but I guess should be supported that option in 2.8.0.
2. Does GeoNetwork (v2.8.0 and the current version) always process all Schematron files defined for a plugin when validating metadata? In v3.2.2 I've seen that the Schematron Admin allows you to configure "Selective Schematron Application" (as described in the change proposal at [2]). What I'm actually interested in is if GeoNetwork can skip processing of subsequent Schematron files if a previous Schematron file resulted in an error. The idea is that expensive computations could be put at the end of a validation workflow, and skipped if a previous validation step already determined that the metadata that is being tested is invalid.
In 3.x there's a Schematron Admin that allows to configure the rules based on some criteria (for example, if the metadata has specific content, it's in a specific group, etc.). That can be useful in some cases, for example if the catalogue has INSPIRE and non INSPIRE metadata, to customise rules to only executes INSPIRE schematrons for INSPIRE metadata. In previous versions, such a feature doesn't exists.
There's no feature to skip other schematron files if previous one failed (there's also no order configurable for schematron execution). If a schematron fails, the validation panel in the metadata editor displays the errors, but all schematrons are executed.
Best regards,
Johannes Echterhoff
[1] https://github.com/geonetwork/schema-plugins/blob/2.8.x/schematrons/rules/schematron-rules-inspire.sch
[2] https://github.com/geonetwork/core-geonetwork/wiki/SchematronAdmin
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net<mailto:GeoNetwork-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
--
Vriendelijke groeten / Kind regards,
Jose GarcÃa
[Das Bild wurde vom Absender entfernt.]<http://www.geocat.net/>
Veenderweg 13
6721 WD Bennekom
The Netherlands
T: +31 (0)318 416664<tel:+31318416664>
[Das Bild wurde vom Absender entfernt.]<https://www.facebook.com/geocatbv> [Das Bild wurde vom Absender entfernt.] <https://twitter.com/geocat_bv> [Das Bild wurde vom Absender entfernt.] <https://plus.google.com/u/1/+GeocatNetbv/posts>
Please consider the environment before printing this email.
(attachments)
