your mail

[Matt Jones]

Ravi,

We use Xerces to do the validation in the online EML parser, and in
the command line parser that we ship with EML.  My guess is that you
are either using an older verision of Xerces with a bug in it (we've
reported several bugs to them that they have fixed in various releases),
or you haven't set all of the validation options correctly.  Look
at the xercesImpl.jar file in the eml distribution and see if it the same
version you are using.  You might also look at the Java code we use for
validation to see if you're setting the options the same way we are -- its
in the eml distribution. Good luck, and let me know if the problem persists.

Matt

******************************************************************
Matt Jones                                    jones at nceas.ucsb.edu
http://www.nceas.ucsb.edu/    Fax: 425-920-2439   Ph: 907-789-0496
National Center for Ecological Analysis and Synthesis (NCEAS)
******************************************************************

On Mon, 30 Dec 2002, Ravi Peri wrote:

> Matt:
>
> My name is ravi, and I work as a programmer at Center for Environmental
> Studies, ASU.
> I am working on a tool to map EML documents to relational storage.
>
> I am having a difficulty in validating eml documents with Xerces parser.
> After couple of trial and errors I could narrow down the problem to
>
> eml-party.xsd and eml-resource.xsd. The parser cannot recognize res:IDType,
> res:SystemType, res:ScopeType in rp:responsibleParty type.
> The parser works just fine when I substitute xs:string for each in
> eml-party.xsd, but throws
>
> [Error] Datatypevalidator for attribute scope not found in element type
> creator
> [Error] Datatypevalidator for attribute id not found in element type
> metadataProvider
> [Error] Datatypevalidator for attribute system not found in element type
> metadataProvider
> [Error] Datatypevalidator for attribute scope not found in element type
> metadataProvider
> [Error] Datatypevalidator for attribute scope not found in element type
> contact
>
> when I change it back to original definition.
>
> I was wondering if you faced the same problem, or have a solution to it.
>
> One more thing the document is valid according to the EML parser service
> provided online, and XML Spy. Its just a problem when I am using Xerces.
>
> Thanks in advance,
> ravi
>
>
>