Menu
▾
▴
Re: [GeoNetwork-devel] ISO 19119 Validation [SEC=UNCLASSIFIED]
|
From: <Joh...@ga...> - 2008-09-12 03:04:00
|
Hi Andrew, The XSDs can't implement the constraints of ISO 19115 and ISO 19119. That is why Schematron is used. Your list of Schematron validation errors are all related to constraints. There are few mandatory fields but many conditional fields. Of course all conditional fields will not be available in the default view because they only become mandatory under certain conditions. John -----Original Message----- From: geo...@li... [mailto:geo...@li...] On Behalf Of Andrew Chamberlain Sent: Thursday, 11 September 2008 2:51 AM To: geo...@li... Subject: Re: [GeoNetwork-devel] ISO 19119 Validation Hi Simon, Thanks for that. Just to confirm/paraphrase, if the check gets as far as the schematrons, then can I assume the metadata is at least valid against the XSDs? I ask because I was previously getting errors which GeoNetwork itself would pick up and report (like missing mandatory elements). When I 'fixed' these (by populating them), I started getting the schematron reports, I wasn't sure if I was going forwards or backwards! Regarding the schematron errors themselves, I enclose them below. Not sure if these are all oddities/anomalies, but either way, I'm rather surprised that some metadata which adheres to the XSD schema could be so wrong after all! So far I've only filled in the elements in the Default View of the metadata. Is it possible that the errors are due to some of the (mandatory) fields in the Advanced View being left empty? Please forgive me it should have been obvious, but I would have thought that a Default View would include all the mandatory fields? Andy --------------- Schematron validation for ISO 19115(19139) CharacterString must have content or it's parent must have a valid nilReason attribute. CRS attributes constraints ISOFTDS19139:2005-TableA1-Row24 - name required ISOFTDS19139:2005-TableA1-Row07 - otherConstraints required if otherRestrictions ISOFTDS19139:2005-TableA1-Row16 - units required for values ISOFTDS19139:2005-TableA1-Row13 - description required if no sourceExtent ISOFTDS19139:2005-TableA1-Row14 - sourceExtent required if no description ISOFTDS19139:2005-TableA1-Row10 - content mandatory for dataset or series ISOFTDS19139:2005-TableA1-Row11 - source required if no statement or processStep ISOFTDS19139:2005-TableA1-Row12 - processStep required if no statement or source ISOFTDS19139:2005-TableA1-Row08 - dataset must have report or lineage ISOFTDS19139:2005-TableA1-Row09 - levelDescription needed unless dataset or series * "levelDescription" is mandatory if "level" notEqual 'dataset' or 'series'. ISOFTDS19139:2005-TableA1-Row17 - units required for density values ISOFTDS19139:2005-TableA1-Row18 - MD_Format required ISOFTDS19139:2005-TableA1-Row23 - element required ISOFTDS19139:2005-TableA1-Row04 - dataset must have extent ISOFTDS19139:2005-TableA1-Row05 - dataset or series must have topicCategory ISOFTDS19139:2005-TableA1-Row06 - either aggregateDataSetName or aggregateDataSetIdentifier must be documented ISOFTDS19139:2005-TableA1-Row01 - language indication ISOFTDS19139:2005-TableA1-Row02 - character set indication ISOFTDS19139:2005-TableA1-Row19 - detail required unless simple term ISOFTDS19139:2005-TableA1-Row20 - condition ISOFTDS19139:2005-TableA1-Row21 - domainCode ISOFTDS19139:2005-TableA1-Row22 - shortName ISOFTDS19139:2005-TableA1-Row15 - checkPointDescription required if available Sim...@cs... wrote: Hi Andy, The schematron heading you refer to is just a text string included in the schematron report xsl - it could be modified to anything we/you want - schematrons are just rules that end up being applied as an xslt to the metadata record - they are the second part of the validation process. The first part of the validation process is against the XSDs - which are the iso19139 and iso19119 XSDs. The schematron xslts and XSDs etc are in the appropriate directory in web/geonetwork/xml/schemas. The schematron rules and instructions for generating the xslts are in the schematrons directory. The html templates used to display the report are in schematronCache/schematronscripts. The schematron report shown tells you that is work from David Carlisle and Rick Jelliffe but see also http://xml.ascc.net/resource/schematron/schematron-report.html I'd be interested to see the validation errors and whether any of them are oddities/anomalous. Cheers, Simon -----Original Message----- From: geo...@li... on behalf of Andrew Chamberlain Sent: Tue 9/9/2008 11:50 PM To: geo...@li... Cc: Subject: [GeoNetwork-devel] ISO 19119 Validation Hi All, I'm just testing out the new ISO 19119 support with a trial WMS service. Everything looks good, but when I perform a check on the metadata, quite a few errors are reported. I can forward these problems, but first I was wondering if these errors may be occurring because the wrong schema is being used to validate the XML? I say this because the Schematron Report is headed: "Schematron validation for ISO 19115(19139)" Should I expect a different heading if the "WMS service in ISO19139/119" template was used? Best regards, Andy P.S. I realise the code is yet to be included in a stable release, but I'm happy to be a guinea pig in the meantime. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ GeoNetwork-devel mailing list Geo...@li... https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork . |