eml not valid is xmlSpy versions 2006+, eml-text and eml-documentation

[mbjones]

---

Author Name: Margaret O'Brien (Margaret O'Brien) Original Redmine Issue: 2703, https://projects.ecoinformatics.org/ecoinfo/issues/2703 Original Date: 2006-12-15 Original Assignee: Matt Jones

---

This is NOT a duplicate of bug 2054.

These changes are needed to make eml validate in xmlSpy2006+: eml-text.xsd:

=> add mixed="true" and to the choice of this complexType add minOccurs="0" eml-documentation.xsd: add elementFormDefault="qualified" to the root-element History: Some folks who have newer versions of xmlSpy (2006, 2007) were not able to validate eml documents. The failures are mysterious and variable. Validating eml.xsd is successful, but when validating a data package, Spy replies that the schema is invalid. It usually fails in eml-view, but also occasionally in eml-project, or eml-software. Initially, Altova tech support said that it was a bug in Spy. They recently changed their tune, and suggested the above changes to our schema. With these changes, local copies of EML can now be validated in Spy2007. Altova did not quote the parts of the xml specification relating to this error. Given the error messages from Spy, I was not able to see where eml failed to comply with the xml specs. I have put the email trail with error messages at the url above, if that helps anyone else get to the bottom of this. It could be that this xmlSpy behavior is still a defect in the software, and that eml schema is valid as is, and that tech support is just trying to shut me up. Relationships to other bugs: 1. It's possible that this was part of the behavior that Inigo reported in bug #2479, or described in emails to eml-dev. 2. This is not related to bug 2054, in which eml.xsd failed due to the element in additionalMetadata. That failure was noticed first in xmlSpy2005, whereas this behavior first appeared with Spy2006.

[mbjones]

---

Original Redmine Comment Author Name: Margaret O'Brien (Margaret O'Brien) Original Date: 2007-04-03T19:26:58Z

---

Bug 2704 has been marked as a duplicate of this bug.

[mbjones]

---

Original Redmine Comment Author Name: Margaret O'Brien (Margaret O'Brien) Original Date: 2007-04-03T19:30:06Z

---

Bug 2705 has been marked as a duplicate of this bug.

[mbjones]

---

Original Redmine Comment Author Name: Margaret O'Brien (Margaret O'Brien) Original Date: 2008-02-08T01:25:31Z

---

from INigo and Margaret: EML uses some parts of DocBook schema (eg. and children). Some of these are generating the parsing errors in XMLSpy 2006+. For example, in eml.xsd, there are these lines inside :

The Dublin Core Metadata Initiative

So it seems that there are 2 choices for the short term:

1. take all the ulink, citetitle, and other offending tags out of eml documentation
2. add these elements in as children of para

We could consider adding these back (and maybe more?) docBook elements later (i.e., 2.1+)

[mbjones]

---

Original Redmine Comment Author Name: Margaret O'Brien (Margaret O'Brien) Original Date: 2008-03-21T22:25:19Z

---

From Chris and Margaret: With respect to the docbook elements that contribute to this bug in eml-text.xsd, we looked into the status of the DocBook schema. We discovered that as of March 2008, there is a committee draft for DocBook schema v5. It appears to be a complete refactoring of v4 (the dtd), and introduces many backward incompatibilities. Although EML is not terribly dependent on v4, importing this schema is likely to be outside the scope of eml-2.0.2, but might be considered in the future.

current specification http://www.docbook.org/specs/docbook-5.0-spec-cd-03.html development history http://www.docbook.org/specs/

[mbjones]

---

Original Redmine Comment Author Name: Margaret O'Brien (Margaret O'Brien) Original Date: 2008-03-25T18:43:03Z

---

This is a summary of the fixes reported necessary by Inigo in his email to eml-dev (2008-02-27). Probably this list could be split into multiple bugs. Most schema docs are affected, and many also affect instance docs.

a. => add mixed="true"

b. and to the choice of this complexType add minOccurs="0"

c. eml-documentation.xsd: add elementFormDefault="qualified" to the root-element

1 - : unexpected under in eml.xsd and elsewhere--> add element , and child tag () to the element (in eml-text.xsd), following the "docBook" model.

2 - : no more elements under --> close element before we open s (group was not nested appropriately in eml.xsd)

3 - : further elements required under element in about ALL *.xsd files ---> added

group following and corresponding closing elements.

4 - : further elements required under element in most of *.xsd files --> added

group inside and corresponding closing elements.

5 - : empty element in "methods description" eml-entity.xsd --> entry deleted

6 - : element not allowed under element

in eml-attribute.xsd --> removed and corresponding closing element

7 - :