Hi James,

Yes. This issue was the subject of some discussion last month. 
The Round 2 WSDL had indeed been updated to reflect the new 
rules for derivation by restriction. An objection was raised [1], 
various futher messages [2][3][4] resulted in a resolution to retain 
the form used in the WSDL spec with agreement all around that 
the situation is a mess.

Since the focus of the group is SOAP interop first, with WSDL 
interop a secondary consideration, I've left the issue on the back 
burner, as awkward as it is.

What concerns me is that nothing has been heard for a long time 
from the authors of the WSDL spec, on this or any other issue, and 
there seems to be no timetable for any revision of the spec.

We've gone around and around on this. Any thoughts?

RC

[1] http://groups.yahoo.com/group/soapbuilders/message/5855
[2] http://groups.yahoo.com/group/soapbuilders/message/5859
[3] http://groups.yahoo.com/group/soapbuilders/message/5855
[4] http://groups.yahoo.com/group/soapbuilders/message/5879

>  
>  The WSDL specification contains the following example of an array of floats:
>  
>  <complexType name="ArrayOfFloat">
>    <complexContent>
>      <restriction base="soapenc:Array">
>        <attribute ref="soapenc:arrayType" wsdl:arrayType="xsd:float[]"/>
>      </restriction>
>    </complexContent>
>  </complexType>
>  
>  This is invalid as the Schema Primer states that:
>  
>      that types derived by restriction must repeat all
>      the components of the base type definition that are to be
>      included in the derived type
>  
>  The implication of this is that the above definition describes a
>  complexType which can never contain child elements. The use of such
>  definitions causes problems for any software which correctly applies
>  the rules of xml schemas to such definitions.
>  
>  In order for it to contain elements, it must either:
>  	repeat the <xs:any> from the original SOAP array definition
>  or
>  	replace it with a more restrictive definition.
>  
>  There are a number of different ways to define an array. However, the
>  example in the spec should be replaced with the following:
>  
>  <xs:complexType name="ArrayOfFloat">
>    <xs:complexContent>
>      <xs:restriction base="soapenc:Array">
>        <xs:sequence>
>          <xs:element name="item" minOccurs="0" maxOccurs="unbounded"
>  type="xs:float" />
>        </xs:sequence>
>        <attribute ref="soapenc:arrayType" wsdl:arrayType="xs:float[]"/>
>      </xs:restriction>
>    </xs:complexContent>
>  </xs:complexType>
>  
>  
>  To make matters worse, such definitions appear in the interop tests for
>  WSDL.
>  Propagating such invalid definitions even further.
>  
>  We need an errata for the WSDL spec so that the use of this invalid array
>  definition can be prevented.
>  
>  James.
>  
>  
>  Cape Clear Software Limited.
>  61 Fitzwilliam Lane
>  Dublin 2
>  Ireland
>  
>  Email : james.pasley@[...].com
>  Switchboard  : + 353 (1) 2419900
>  Direct line  : + 353 (1) 2419957
>  Fax          : + 353 (1) 2419901
>  www          : www.capeclear.com
>  
>  Visit www.capescience.com
>  
>  
>  
>  To unsubscribe from this group, send an email to:
>  wsdl-unsubscribe@[...].com
>  
>   
>  
>  Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 
>  



------------------------ Yahoo! Groups Sponsor ---------------------~--> 
Tiny Wireless Camera under $80!
Order Now! FREE VCR Commander!
Click Here - Only 1 Day Left!
http://us.click.yahoo.com/75YKVC/7.PDAA/ySSFAA/W6uqlB/TM
---------------------------------------------------------------------~-> 

To unsubscribe from this group, send an email to:
wsdl-unsubscribe@[...].com

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/