[5483] WSDL schema defines fault 'element' incorrectly
Philippe,
John Kaputin reported this bug.[1] I
reviewed it and agree. The spec was updated to include some tokens in the
definition of the content for faults, but the schema wasn't.
We haven't discussed the process for
maintainance. In this case, the schema was improperly updated when the
spec changed so I propose to simply correct the schema. Failure to do so
means that the schema reports that some valid WSDL documents are invalid,
e.g. those with a token like #none, #any, #other for the content of a Fault.
[1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=5483
The schema is currently:
<xs:complexType name="InterfaceFaultType"
mixed="false">
<xs:complexContent>
<xs:extension base="wsdl:ExtensibleDocumentedType">
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:any namespace="##other"
processContents="lax" minOccurs="1" maxOccurs="1"/>
</xs:choice>
<xs:attribute name="name" type="xs:NCName"
use="required"/>
<xs:attribute name="element"
type="xs:QName" use="optional"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
But it should be:
Arthur Ryman, Technical Executive (IBM
DE)
Project and Program Management, Rational Division
phone: +1-905-413-3077, TL 313-3077
assistant: +1-905-413-3831, TL 313-3831
fax: +1-905-413-4920, TL 313-4920
mobile: +1-416-939-5063
