Andrea,
I have not tested against the XSD's provided with Geonetwork other than via
the Geonetwork tool itself. The XSD's that I have been using were sourced
from the end site at http://eden.ign.fr/xsd/isotc211.
-----Original Message-----
From: geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] On Behalf Of Andrea
Carboni
Sent: Thursday, 22 March 2007 2:37
To: geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] validating metadata on harvest
Hi Michael,
I have investigated and I have found 2 problems:
- the validation code does not work anymore.
I have changed it using the facility of Java 1.5. Now it works.
- the 19139 schema seems wrong
I tried oxygen to validate a metadata against the schema but I got
some errors inside the schema. I fixed one but then I got others:
SystemID: web/xml/schemas/iso19139/schema/gco/basicTypes.xsd
Position: 383:34
Description: src-resolve: Cannot resolve the name 'gco:Record' to a(n)
'element declaration' component.
Did you use the 19139 xsd files provided with geonetwork or do you have
another set of files? My schema files are dated 2006-05-02.
Cheers,
Andrea
Hi list,
I've been playing around with the new Geonetwork beta, specifically the
area
of its implementation of the 19139 templates.
I have created a test xml document around a dataset of ours to test the
harvesting with. This test document I am able to validate using both oXygen
and using my own wrappers around oNVDL.When I try to import this test record I get an error if I have validation
checked (without validation checked the record is imported successfully)
the
error message is:
org.jdom.input.JDOMParseException: Error on line 1: cvc-elt.1: Cannot find
the declaration of element 'gmd:MD_Metadata'.I moved on and created a default ISO19139 document through the Geonetwork
interface and compared its namespace declarations to mine, there seemed to
be
no reason that mine will not validate. I next tried to import the saved xml
of the default document and found that the same error is produced. Is there
somewhere that I have to setup a catalog for these records to validate
properly?I next tried to validate the default document using both oXygen and my own
oNVDL wrappers and found that there was an error in the gco:DateTime and
gmd:MD_TopicCategoryCode nodes. The DateTime was easily dismissible as the
value was null in the default record but the MD_TopicCategoryCode uses
"codeList" and "codeListValue" where MD_TopicCategoryCode is defined as a
simpleType and declares no attibutes in the xsd.My understanding of xml is coming along but is still not that great so
please
point out any floors in my logic here but I'm essentially trying to import
my
own record that I can validate externally but cannot validate through the
batch import function, and I'm also trying to import a record that
Geonetwork
beta1 created and cannot import that record either.
Any information would be great,
Cheers,
Michael Gannon.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork