Date:         Tue, 7 Dec 2004 14:18:20 -0500
Reply-To:     Metadata Object Description Schema List <[log in to unmask]>
Sender:       Metadata Object Description Schema List <[log in to unmask]>
From:         Andrew E Switala <[log in to unmask]>
Subject:      Re: mads collection
Comments: To: [log in to unmask]
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline

Weird.  The Xerces parser from Apache (version 2.6.0) validates instance
documents with either <mads> or <madsCollection> as the root element,
using the simplified schema from R. Dennenberg's e-mail:
-----------------------
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://www.loc.gov/xxx"
xmlns="http://www.loc.gov/xxx"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">

 <xsd:element name="mads"/>
 <xsd:element name="madsCollection">
  <xsd:complexType>
   <xsd:sequence>
    <xsd:element ref="mads" maxOccurs="unbounded"/>
   </xsd:sequence>
  </xsd:complexType>
 </xsd:element>
 </xsd:schema>
--------------------------------------------
The instance documents tested were simply:
--------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<mads
  xmlns="http://www.loc.gov/xxx"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.loc.gov/xxx mads2.xsd">
</mads>
--------------------------------------------
and
--------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<madsCollection
  xmlns="http://www.loc.gov/xxx"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.loc.gov/xxx mads2.xsd">
        <mads/>
        <mads/>
</madsCollection>
--------------------------------------------
Do Oxygen or XMLSpy actually fail to validate a existing, valid
document (created e.g. with a plain text editor), or is this just an
issue with the editors' user interface for creating new documents?  If
validation fails, what's the error message?

--Andy

>>> [log in to unmask] 2004-12-07 13:57:40 >>>
On Dec 7, 2004, at 1:26 PM, Andrew E Switala wrote:

> It's definitely a XMLSpy bug.

I've tried on more than one occasion to try it out with Oxygen.  It
doesn't work there either.  Whether a bug in the applications or a bug
in the spec, this is not good.

Bruce