W3C home > Mailing lists > Public > www-ws-desc@w3.org > May 2002

RE: extensions [was: updated part1 docs (editor's drafts)]

From: Jeffrey Schlimmer <jeffsch@windows.microsoft.com>
Date: Fri, 3 May 2002 15:48:45 -0700
Message-ID: <2E33960095B58E40A4D3345AB9F65EC106E152AD@win-msg-01.wingroup.windeploy.ntdev.microsoft.com>
To: "WS-Desc WG (Public)" <www-ws-desc@w3.org>
Igor, thanks for being concrete. This looks about right. (But I reserve
the right to be smarter after we finish the discussion about 3 types of
"extensions" :-)

 

--Jeff 

 

-----Original Message-----
From: Sedukhin, Igor [mailto:Igor.Sedukhin@ca.com] 
Sent: Thursday, May 02, 2002 8:58 AM
To: Sanjiva Weerawarana; WS-Desc WG (Public)
Subject: RE: extensions [was: updated part1 docs (editor's drafts)]

 

Sanjiva,

To conform to our extensibility requirement I'd like to propose this (my
changes are in red):

This may allow one to provide WSDL extension in a very flexible manner
without breaking WSDL schema compliance.

<wsdl:definitions name="nmtoken"? targetNamespace="uri"?>

    <import namespace="uri" location="uri"/>*

    <wsdl:documentation .... /> ?

    <wsdl:types> ?
        <wsdl:documentation .... />?
        <xsd:schema .... />*
        <-- extensibility element --> *
    </wsdl:types>

    <wsdl:message name="nmtoken"> *
        <wsdl:documentation .... />?
        <part name="nmtoken" element="qname"? type="qname"?> *
           <-- extensibility element --> *
        </part>
        <-- extensibility element --> *
    </wsdl:message>

    <wsdl:portType name="nmtoken">*
        <wsdl:documentation .... />?
        <wsdl:operation name="nmtoken">*
           <wsdl:documentation .... /> ?
           <wsdl:input name="nmtoken"? message="qname">?
               <-- extensibility element --> *
               <wsdl:documentation .... /> ?
           </wsdl:input>
           <wsdl:output name="nmtoken"? message="qname">?
               <-- extensibility element --> *
               <wsdl:documentation .... /> ?
           </wsdl:output>
           <wsdl:fault name="nmtoken" message="qname"> *
               <-- extensibility element --> *
               <wsdl:documentation .... /> ?
           </wsdl:fault>
           <-- extensibility element --> *
        </wsdl:operation>
        <-- extensibility element --> *
    </wsdl:portType>

    <wsdl:binding name="nmtoken" type="qname">*
        <wsdl:documentation .... />?
        <-- extensibility element --> *
        <wsdl:operation name="nmtoken">*           
           <wsdl:documentation .... /> ?
           <-- extensibility element --> *
           <wsdl:input> ?
               <wsdl:documentation .... /> ?
               <-- extensibility element -->
           </wsdl:input>
           <wsdl:output> ?
               <wsdl:documentation .... /> ?
               <-- extensibility element --> *
           </wsdl:output>
           <wsdl:fault name="nmtoken"> *
               <wsdl:documentation .... /> ?
               <-- extensibility element --> *
           </wsdl:fault>
        </wsdl:operation>
    </wsdl:binding>

    <wsdl:service name="nmtoken"> *
        <wsdl:documentation .... />?
        <wsdl:port name="nmtoken" binding="qname"> *
           <wsdl:documentation .... /> ?
           <-- extensibility element -->
        </wsdl:port>
        <-- extensibility element -->
    </wsdl:service>

    <-- extensibility element --> *

</wsdl:definitions>


-- Igor Sedukhin .. (Igor.Sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788



-----Original Message-----
From: Sanjiva Weerawarana [ <mailto:sanjiva@watson.ibm.com>
mailto:sanjiva@watson.ibm.com]
Sent: Monday, April 29, 2002 4:35 PM
To: WS-Desc WG (Public)
Subject: updated part1 docs (editor's drafts)


Attached are the latest editors' draft of the part1 spec. I have also
included the slightly modified stylesheet I used to get
the issues color coded.

Sanjiva.
Received on Friday, 3 May 2002 18:53:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:20 GMT