[eml-dev] EML-2.1.0 Release Candidate-1 -- not valid

Mon Apr 14 12:01:58 PDT 2008

Hi Inigo -
I appreciate the work you did testing for these errors in spy2008. The 
latest copy I can get ahold of is 2007, which agrees with the validator 
at the W3C (http://www.w3.org/2001/03/webdata/xsv), that RC1 is a valid 
schema.  I made a few changes to the eml-documentation.xsd, which I am 
attaching here. Can you do me the favor of trying this out in your 
spy2008?  I want to be sure it works before I tag another rc. My fix: It 
looked like spy was objecting to the repeated occurences of 
<doc:module>, so I added a complexType whose elements referenced the 
remanining globals, set cardinality = 0..many, and wrapped them in 
sequence/choice to allow any them to appear in any combinations.

This fix applies to bug 2703, again -- here is what has been going on: 
You may have noticed that all the error reports are from the 
"xs:documentation" sections of EML schema components. The content model 
for xs:documentation (and also for appinfo) is a wildcard, which by 
default is processed with lax validation. If the processor can find 
appropriate element declarations, it should use those instead. But to 
make it unpredictable, processors are not required to perform the 
schemas imports until they absolutely need to. So up until ~2005 was 
processors probably did not bother to look at documentation.xsd, and so 
the contents of <annotation> were checked only for well-formedness. 
Fast-forward: processors get smarter, they might actually look at the 
imported schemas, validated against them and spot errors. While 
xmlSpy2008 happens to be ahead of the w3c in applying standards, they 
still may not be catching everything.

EML 2.0.x schemas were created according to the best recommendations 
available for documentation and the same examples are still being 
referenced in the literature today. All the changes I've made to 
eml-documentation.xsd have further defined these elements to match the 
way they were used by the original schema authors - and I hope, to 
maintain flexibility for the future. Given that processors may or may 
not load schema compoents, we cannot completely rely on their error 
reports - and so our only defense in anticipating errors is our own 
knowledge of schema construction. I would really like another person to 
look over the changes to documentation.xsd and the use of its elements 
in the other components for some requirement that I may have missed.

FYI, you can find info about XSV development on its author's home page: 
http://www.ltg.ed.ac.uk/~ht/xsv-status.html, 
http://www.ltg.ed.ac.uk/~ht/ . Altova (understandably) plays its hand 
close, and so I havent run into any specifics on their implementation. 
OxygenXML can validate using XSV as a plugin. And btw - OxygenXML is 
FREE to anyone trying to make the world a better place: 
http://www.oxygenxml.com/support_life.html (yes, this is a plug for oxygen).

Inigo - I did not address your entire list of changes (detailed in your 
email of 2/27), although I did mention in the bug notes which ones were 
applied and why. This note is long enough, and so I will do that later 
today or tomorrow. Again, thanks for your willingness to be the tester 
for spy.latest-version. If we need to get on vtc while you do that - no 
problem - I'm at my desk today/tommorow.

Margaret

inigo wrote:

>
> Margaret,
>
> Thanks for the instructions for the checkout - it turns out that there 
> is a particular password to access the CVS anonymously - loi
>
> The release candidate is not valid, according to XMLSpy 2008.
>
> I tested the schema against a (valid EML) document, and failed.
>
> Error is:
> <doc:module> not allowed under element <doc:moduleDocs> (no more 
> elements expected: the element <doc:moduleDocs> is not valid with 
> respect to the actual type definition '{anonymous}'
>
> The release candidate I sent about a month ago to this list did well 
> against the same test. I think that the way you fixed the 
> 'documentation' bug may be the trouble. I diffed a bit both the schema 
> you checked in and the valid schema i proposed, and saw some 
> differences that may account for the error observed.
>
> cheers, inigo
>
>
> Margaret O'Brien wrote:
>
>> Hi -
>> Some folks needed to checkout the release using anonymous checkout.. 
>> Here is a link to the instructions - see under the heading "Read-only 
>> anonymous CVS access" for the pswd
>> http://www.kepler-project.org/Wiki.jsp?page=DevelopmentForKepler
>>
>> For me, this worked:
>> cvs -d anonymous at cvs.ecoinformatics.org:/cvs checkout eml
>>
>>
>>
>> ========================
>> Margaret O'Brien
>> Information Management
>> Santa Barbara Coastal LTER Marine Science Institute
>> University of California
>> Santa Barbara, CA  93106-6150
>>
>> 805-893-2071
>> mob at icess.ucsb.edu
>> http://sbc.lternet.edu
>> ========================
>>
>>
>>
>> inigo wrote:
>>
>>>
>>> margaret,
>>>
>>> could you post some more data about checking out the candidate?
>>>
>>> i dont have an account in the ecoinformatics CVS (i assume im not 
>>> alone)
>>> and im not sure what parameters should i enter to do a checkout.
>>>
>>> cheers,
>>> inigo
>>>
>>>
>>> Margaret O'Brien wrote:
>>>
>>>> Hi eml-dev -
>>>> I have created a release candidate, tagged RELEASE_EML_2_1_0_RC_1, 
>>>> which is now available from cvs.ecoinformatics.org. A few notes 
>>>> from the README are below.
>>>> Hope this works for everyone -
>>>> Margaret
>>>>
>>>>
>>>> HIGHLIGHTS IN THIS RELEASE
>>>> --------------------------
>>>> This release addresses 2 bugs which caused the schema to be invalid 
>>>> with
>>>> respect to the W3C specifications using the XSV validator
>>>> (http://www.w3.org/2001/03/webdata/xsv). Although the changes were 
>>>> minor,
>>>> one was incompatible with 2.0 releases, which necessitated the version
>>>> number "2.1".  In the 2.0 series, the content model for 
>>>> additionalMetadata
>>>> included an element <describes> whose cardinality was 0..many, 
>>>> alongside
>>>> <xs:any>. This construct is non-deterministic, and so a child element
>>>> was added to the additionalMetadata section to contain the <xs:any> 
>>>> content.
>>>> Additionally, several elements of txt:TypeText required additional
>>>> definition so that mixed content could be accommodated. These errors
>>>> were not apparent with validation software available in 2004-2005, but
>>>> were brought to light more recently. Several small changes were 
>>>> made to
>>>> the enumeration list and unitTypes for standard units and stmml 
>>>> descriptions
>>>> of customUnits. Two elements in the literature schema were allowed 
>>>> to be
>>>> optional so that articles-in-press could be described.  No changes 
>>>> were
>>>> made to xsl stylesheets.
>>>>
>>>>
>>>>
>>>> BUGS FIXED AND NEW FEATURES (see also 
>>>> http://bugzilla.ecoinformatics.org/)
>>>> -------------------------------------------------------------------------- 
>>>>
>>>> 2.1.0 Changes - (numbers refer to the corresponding Bugzilla bug)
>>>> 2054: schema non-deterministic, added the <metadata> tag to 
>>>> additionalMetadata
>>>> 2083: in stmml.xsd, dimension 'current' was wrongly entered as 
>>>> 'charge'
>>>> 2703: elements changed in txt:TypeText for ulink, citetitle, para, 
>>>> section
>>>> 3051: missing units were added to exclusion list to match 
>>>> eml-unitDitionary
>>>> 3163: in literature.xsd, cardinality of volume and pageRange now 0..1
>>>>
>>>>
>>>>   
>>>
>>>
>

-- 
========================
Margaret O'Brien
Santa Barbara Coastal-LTER Data Management
Marine Science Institute
University of California
Santa Barbara, CA  93106-6150

805-893-2071
mob at icess.ucsb.edu
http://sbc.lternet.edu
======================== 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: eml-documentation.xsd
Type: text/xml
Size: 3736 bytes
Desc: not available
Url : http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/eml-dev/attachments/20080414/49ecaa11/eml-documentation.xml