Re: [wsrf] Changes required in published wsdl

[Samuel Meder <meder@mcs.anl.gov>]

On Tue, 2004-07-13 at 16:59, Ian Robinson wrote:
> We ran out of time on Monday discussing "how" we would update the WSDL
> and schema given that it is already published. Savas made the point
> that, once we have published WSDL and XSD at a
> http://docs.oasis-open.org/wsrf/... URL, then we should not change it.
> I believe the only WSDL that needs to be changed for correctness is
> the ServiceGroups WSDL. The other problems described are more for
> consistency than correctness.

That is correct, though I do feel it is bad to have different versions
of the RL wsdl in the document vs the standalone wsdl file.

/Sam

> I propose that we produce an additional
> http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ServiceGroup-1.2-draft-02.wsdl 
> to fix the problems mentioned by Sam
> and work the other problems described for the WSRF-RL and WSRF-RP WSDL
> as issues in the normal way.
> 
> 
> Regards,
> Ian Robinson
> STSM, WebSphere Transactions Architect
> IBM Hursley Lab, UK
> ian_robinson@uk.ibm.com
> ----- Forwarded by Ian Robinson/UK/IBM on 13/07/2004 22:30 -----
> 
> Ian Robinson
> 
> 13/07/2004 22:28
> 
>         To:      
> "Latha Srinivasan"
> <Latha.Srinivasan@hp.com>, Tim Banks/UK/IBM, Tom Maguire/Hawthorne/IBM, David Snelling <d.snelling@fle.fujitsu.com>
>         cc:      
> wsrf-oasis
> <wsrf@lists.oasis-open.org>
>         From:      
> Ian
> Robinson/UK/IBM@IBMGB
>         Subject:      
> Re: [wsrf] Changes
> required in published
> wsdlLink
> 
> Some other comments on the WSDL and XSD:
> 
> 1. wsrf-WS-ResourceLifetime-1.2-draft-01.xsd defines global elements
> wsrl:CurrentTime and wsrl:TerminationTime that are not consistently
> used by other WSDL. For example,
> wsrf-WS-ResourceLifetime-1.2-draft-01.wsdl defines
>       <xsd:element name="SetTerminationTimeResponse">
>          <xsd:complexType>
>             <xsd:sequence>
>                <xsd:element name="NewTerminationTime"
>                             nillable="true"
>                             type="xsd:dateTime" />
>                <xsd:element name="CurrentTime"
>                             type="xsd:dateTime" />
>             </xsd:sequence>
>          </xsd:complexType>
>       </xsd:element>
> 
> 2. wsrf-WS-ServiceGroup-1.2-draft-01.wsdl doesn't need the wsdl:import
> or xsd:import of the ResourceLifetime wsdl or xsd. It would need the
> xsd:import if the latter defined a global element
>   <xsd:element name="InitialTerminationTime" nillable="true"
> type="xsd:dateTime" /> 
> and wsrf-WS-ServiceGroup-1.2-draft-01.wsdl used it:
>         <xsd:element name="Add">
>           <xsd:complexType>
>             <xsd:sequence>
>               <xsd:element name="MemberEPR" 
>                            type="wsa:EndpointReferenceType" />
>               <xsd:element name="Content" 
>                            type="xsd:anyType" />
>               <xsd:element ref="wsrl:InitialTerminationTime" 
>                            minOccurs="0" maxOccurs="1" />
>             </xsd:sequence>
>           </xsd:complexType>
>         </xsd:element>
> 
> 
> Regards,
> Ian Robinson
> STSM, WebSphere Transactions Architect
> IBM Hursley Lab, UK
> ian_robinson@uk.ibm.com
> 
> 
> 
> Samuel Meder
> <meder@mcs.anl.gov>
> 
> 13/07/2004 16:17
> Please respond to meder
>         
>         To:      
> wsrf-oasis
> <wsrf@lists.oasis-open.org>
>         cc:        
>         Subject:      
> [wsrf] Changes required
> in published wsdl
> 
> 
>       * WS-ResourceLifetime.wsdl and WS-ResourceProperties.wsdl import
>                 WS-Addressing schema but don't need to.
>      * WS-ServiceGroup.wsdl doesn't import WS-Addressing schema but
>        needs to.
>      * It looks like most of the namespace prefixes in the published
>        service group wsdl are wrong. For example:
>        
>            <wsdl:operation name="GetResourceProperty">
>              <wsdl:input name="GetResourcePropertyRequest" 
>                    message="wsrp:GetResourcePropertyRequest" />
>              <wsdl:output name="GetResourcePropertyResponse" 
>                    message="wsrp:GetResourcePropertyResponse" />
>              <wsdl:fault name="ResourceUnknownFault" 
>                    message="wsrp:ResourceUnknownFault" />
>              <wsdl:fault name="InvalidResourcePropertyQNameFault" 
>                    message="wsrp:InvalidResourcePropertyQNameFault" />
>            </wsdl:operation>
>        
>        should be
>        
>            <wsdl:operation name="GetResourceProperty">
>              <wsdl:input name="GetResourcePropertyRequest" 
>                    message="wsrpw:GetResourcePropertyRequest" />
>              <wsdl:output name="GetResourcePropertyResponse" 
>                    message="wsrpw:GetResourcePropertyResponse" />
>              <wsdl:fault name="ResourceUnknownFault" 
>                    message="wsrpw:ResourceUnknownFault" />
>              <wsdl:fault name="InvalidResourcePropertyQNameFault" 
>                    message="wsrpw:InvalidResourcePropertyQNameFault"
> />   
>            </wsdl:operation>
>        
>        This seems to be true for all operations in the spec (I think
>        even the service group operations themselves have it wrong).
>      * The Resource Lifetime wsdl at
>      
> http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2-draft-01.wsdl is missing the oasis copyright statement (though the spec itself has the wsdl with the copyright statement)
>      * The Resource Lifetime wsdl does not declare the
>        ScheduledResourceTerminationRP on the
>        ScheduledResourceTermination porttype.
> 
> /Sam
> -- 
> Sam Meder <meder@mcs.anl.gov>
> The Globus Alliance - University of Chicago
> 630-252-1752
> 
> 
> 
-- 
Sam Meder <meder@mcs.anl.gov>
The Globus Alliance - University of Chicago
630-252-1752