validation of eml sample documents

[Scott Chapal]

Matt Jones <jones at nceas.ucsb.edu> writes:

> The spaces in the XPath statements are just for readability, so I
> can't imagine why we can't take them out.

This apparently is what MSV stumbled on using the -strict option, so
that corroborates the white space 'problem' in the xpath= statements:

Scott Chapal <scott.chapal at jonesctr.org> [31 Jul 2002 13:30:15]:
> Error at line:51, column:30 of
> file://test-eml2.0.0beta9-dataset.xml
>   tag name "boundingCoordinates" is not allowed.
>   Possible tag names are: <geographicDescription>,<references>
> 
> If the strict option is used, the validation fails like this:
> 
> element "xs:selector" is missing "xpath" attribute
>   141:118 at file://eml.xsd
> element "xs:selector" is missing "xpath" attribute
>   158:102 at file://eml.xsd
> element "xs:selector" is missing "xpath" attribute
>   167:99 at file://eml.xsd
> failed to load a grammar.

But I don't understand why the spaces matter.

Removing the spaces in the statements in eml.xsd results in this
however, from MSV:

validating caplterJune2002RE.xml
Error at line:9, column:21 of file://caplterJune2002RE.xml
  field #1 of the key constraint "identifierKey" is not found

Error at line:15, column:23 of file://caplterJune2002RE.xml
  field #1 of the key constraint "identifierKey" is not found

Error at line:18, column:23 of file://caplterJune2002RE.xml
  field #1 of the key constraint "identifierKey" is not found

???  Is something else going on?

> Changing the way we do imports in eml.xsd also was bugging me
> because of the need for the namespace prefix, so this seems like an
> all around good idea to do the import.

That sounds like an improvement.

-- 
Scott E. Chapal_________________________________________________
Database & Network Manager             scott.chapal at jonesctr.org
J.W. Jones Ecological Research Center          229.734.4706 x227
Rt. 2. Box. 2324. Newton, GA 31770-9651        229.734.6650 :FAX