[eml-dev] unable to validate eml.xsd and related schemas with XML*Spy and related suite of products

[Wade Sheldon]

Inigo,

Do the Altova products let you fine-tune the xml parser options like oXygen does? I've found that turning off the full-schema-checking parser feature in oXygen (i.e. http://apache.org/xml/features/validation/schema-full-checking) gets around the unique particle attribution issue because the EML schema grammar constraints are not exhaustively checked before the schema is used to validate/map an EML document. This option doesn't affect how thoroughly documents are validated using the schema, just schema checking, so it's a good work-around until the issue is corrected in EML 2.x.

Here's the xerces link about this feature: http://xerces.apache.org/xerces2-j/features.html#validation.schema-full-checking

Good luck.

Wade Sheldon (GCE)


inigo san gil wrote:
> Thanks Matt and Margaret,
> 
> Ok, I think I mixed different things: A XMLSpy 2006 problem with the 
> bugzilla EML bug ID 2054 (aka the <describes> bug), my bad. 
> 
> However XMLSpy users should note this:
> 
> I recall trying the XMLSpy 2006 version without the <describes> element, 
> and I still got errors which were cryptic but not related to 
> <describes>. That is, I removed the <describes>, I tried to validate a 
> document, and XML Spy complaint about the EML schema.
> 
> Originally, Paul Rees from Altova told me there is indeed a bug in the 
> 2006 version.. NOTE, I sent him the EML 2.0.1 schema sans the 
> <describes> element to reproduce the error.. Read quoted message below.
>  
> I rolled back to XMLSpy 2005, and kept working, until 6 months later, 
> Sabine unearthed what (now) looks like the <describes> bug ( bugzilla ID 
> 2054 ), and hence Paul's (altova) response to Sabine.
> 
> Perhaps someone else aside from Mark Servilla and me have bumped into 
> the XMLSpy2006 problem not related to <describes>?
> 
> Even though it seems that this is *not* a EML bug, because there are 
> some XMLSpy users out there that can be affected by this XMLSpy bug, I 
> think is worthy to post a warning here. My only workaround for that is 
> roll back to 2005, and go from there. Note, you will not be able to use 
> MapForce2006 even using the workarounds in XMLSpy2005 (such as removing 
> <describes>). This mapForce reference is the reason it made me think the 
> original post was related to this Altova bug.
> 
> hope this saves sometime to someone..
> 
> inigo
> 
> -----------------------------------------------------------------------------------
> Hello Inigo,
> 
> Thanks for contacting us.
> 
> I have been able to reproduce the behaviour that you reported and, upon 
> checking our issues tracking database, have found that it is something 
> we are
> already aware of. Consequently I have added your report to the existing 
> entry in order to bolster its chances of an early resolution. It 
> currently has the
> tracking number and title:
> 
> "8466 - appInfo schema elements should be ignored"
> 
> ..and will appear in the release notes here:
> 
> http://www.altova.com/Fixed_Defects.html 
> <http://www.altova.com/Fixed_Defects.html>
> 
> ..when it is addressed.
> 
> In the meantime as a workaround I note that Using <![CDATA[ ... ]]> the 
> embedded appInfo elements can be hidden from schema validation.
> 
> Please accept our sincere apologies for the inconvenience, and thanks 
> for taking the time to send us your report - it's much appreciated.
> 
> Don't hesitate to let me know if I can be of any further assistance.
> 
> Best regards,
> 
> .. Paul Rees
> .. Support Engineer
> .. Altova GmbH
> -------------------------------------------------------------------------------------------------------------
> bugzilla-daemon at ecoinformatics.org wrote:
> 
>> http://bugzilla.ecoinformatics.org/show_bug.cgi?id=2479
>>
>>
>> jones at nceas.ucsb.edu changed:
>>
>>           What    |Removed                     |Added
>> ----------------------------------------------------------------------------
>>             Status|NEW                         |RESOLVED
>>         Resolution|                            |DUPLICATE
>>
>>
>>
>>
>> ------- Comment #1 from jones at nceas.ucsb.edu  2006-06-28 11:10 -------
>> Yes, this is an existing, known issue that is currently being tracked in bug
>> #2054.  The EML schema is invalid, and causes problems in some external tools. 
>> It was not picked up early on because for some reason xerces does not detect
>> the problem.  There is a proposed solution in bug #2054, so I am marking this
>> bug as a duplicate of that one.
>>
>> The workaround for the time being until a new version of EML is released is to
>> modify eml.xsd as described in bug #2054 in order to be able to proceed with
>> your schema mapping activity.
>>
>> Please continue any further discussion on this issue in bug #2054.
>>
>> *** This bug has been marked as a duplicate of 2054 ***
>> _______________________________________________
>> Eml-dev mailing list
>> Eml-dev at ecoinformatics.org
>> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/eml-dev
>>  
>>
> 
> _______________________________________________
> Eml-dev mailing list
> Eml-dev at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/eml-dev

-- 
____________________________________

Wade M. Sheldon
GCE-LTER Information Manager/SIMO Database Administrator
School of Marine Programs
University of Georgia
Athens, GA 30602-3636
Email: sheldon at uga.edu
WWW: http://gce-lter.marsci.uga.edu/lter/asp/db/personnel_bios.asp?id=wsheldon