- From: KUNAL VERMA <verma@cs.uga.edu>
- Date: Tue, 25 Jul 2006 12:02:33 -0400 (EDT)
- To: public-ws-semann@w3.org
Joel, The newer schema for WSDL 1.1 did add entension capabilities to "operation". Just not attribute extensions. Original: see http://www.w3.org/TR/wsdl#A4.1 <complexType name="operationType"> <complexContent> <extension base="wsdl:documented"> <choice> <group ref="wsdl:one-way-operation"/> <group ref="wsdl:request-response-operation"/> <group ref="wsdl:solicit-response-operation"/> <group ref="wsdl:notification-operation"/> </choice> <attribute name="name" type="NCName" use="required"/> </extension> </complexContent> </complexType> New: see http://schemas.xmlsoap.org/wsdl/ <xs:complexType name="tOperation" > <xs:complexContent> <xs:extension base="wsdl:tExtensibleDocumented" > <xs:sequence> <xs:choice> <xs:group ref="wsdl:request-response-or-one-way-operation" /> <xs:group ref="wsdl:solicit-response-or-notification-operation" /> </xs:choice> </xs:sequence> <xs:attribute name="name" type="xs:NCName" use="required" /> <xs:attribute name="parameterOrder" type="xs:NMTOKENS" use="optional" /> </xs:extension> </xs:complexContent> </xs:complexType> Want: <xs:extension base="wsdl:tExtensibleAttributesDocumented" > Proposed Solution: Make modelReference an element for operation, but an attribute for elsewhere. Thanks, John and Kunal
Received on Tuesday, 25 July 2006 16:02:47 UTC