Zafar Abbas of Microsoft pointed out to me that the CDISC ODM schema [1]
I pointed to in a previous note contains a UPA violation.

 <xs:sequence>
  <xs:element ref="Study" minOccurs="0" maxOccurs="unbounded"/>
  <xs:element ref="AdminData" minOccurs="0" =
maxOccurs="unbounded"/>
  <xs:element ref="ReferenceData" minOccurs="0" =
maxOccurs="unbounded"/>
  <xs:element ref="ClinicalData" minOccurs="0" =
maxOccurs="unbounded"/>
  <xs:element ref="Association" minOccurs="0" =
maxOccurs="unbounded"/>
  <xs:element ref="ds:Signature" minOccurs="0" =
maxOccurs="unbounded"/>
  <xs:any namespace="##other" minOccurs="0" =
maxOccurs="unbounded"/>
 </xs:sequence>

I hadn't noticed it and neither did any validator I tried. Apparently 
some version of the Microsoft validator does catch the error.  I 
tried Turbo XML, Xerces (via <oXygen>), XMLSpy">XMLSpy, Stylus Studio, 
and XSV.  None complained.  (I take it if I tried the MS validator, 
the license would prevent me from reporting the results anyway!)  

I also tried just duplicating the ds:Signature particle.

  ...
  <xs:element ref="ds:Signature" minOccurs="0" =
maxOccurs="unbounded"/>
  <xs:element ref="ds:Signature" minOccurs="0" =
maxOccurs="unbounded"/>
  ...

Then Turbo XML reported the violation, but none of the others did.  Is 
this intentional?  It is user error?  I seem to remember the XMLSpy">XMLSpy
folks reporting that they turned off the UPA check because of user 
confusion.

xan

[1] http://www.cdisc.org/schema/ODM1-2-0.xsd

From dareo@m... Wed Sep 15 22:28:18 2004
Received: from lisa.w