W3C home > Mailing lists > Public > public-ws-semann@w3.org > July 2006

Extensibility of operation WSDL 1.1

From: KUNAL VERMA <verma@cs.uga.edu>
Date: Tue, 25 Jul 2006 12:02:33 -0400 (EDT)
To: public-ws-semann@w3.org
Message-ID: <Pine.GSO.4.44.0607251200200.14419-100000@atlas.cs.uga.edu>

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 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 17 April 2012 12:14:27 GMT