[eml-dev] [Bug 2054] - Error in schema validation when XMLSpy or oXygen is used

[bugzilla-daemon@ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=2054





------- Comment #9 from john.cree at ec.gc.ca  2006-06-30 08:18 -------
If I replace the xml starting at: 
      <xs:element name="additionalMetadata" minOccurs="0"
maxOccurs="unbounded">


and ending with:
                 </xs:appinfo>
                </xs:annotation>
              </xs:any>
            </xs:sequence>
            <xs:attribute name="id" type="res:IDType" use="optional"/>
          </xs:complexType>
        </xs:element>

with the snippet from Comment #4.

<xs:complexType>
           <xs:sequence>
             <xs:element name="describes" type="xs:string" 
                         maxOccurs="unbounded">
             </xs:element>
             <xs:element name="metadata" type="xs:string" maxOccurs="1">
               <xs:complexType>
                 <xs:sequence>
                   <xs:any processContents="lax">
                 </xs:sequence>
               </xs:complexType>
             </xs:element>
             </xs:any>
           </xs:sequence>
           <xs:attribute name="id" type="res:IDType" use="optional"/>
         </xs:complexType>

, then eml.xsd, is still not well formed or valid.  Validation in XMLSpy
returns the following message: "xs:any closing element name expected.". 
Looking at the  schema, I can see where this problem arises, but, not being an
XML expert by any means, any of my attempts to correct to correct the lack of a
closing element for <xs:any> result in more serious validation errors.  Could
somebody else try this out to verify the problem and provide a resolution. 
Thank-you.