W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > February 2010

RE: MOAP v2

From: Asir Vedamuthu <asirveda@microsoft.com>
Date: Thu, 25 Feb 2010 05:44:31 +0000
To: Doug Davis <dug@us.ibm.com>, Ram Jeyaraman <Ram.Jeyaraman@microsoft.com>
CC: "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
Message-ID: <4F4942E980BD7147AE7F7D3DCB9CBA9F34E98581@TK5EX14MBXC140.redmond.corp.microsoft.com>
> When the WSDL is not included then the binding information for the MEX operations would default to be the same as the binding information for the stockquote EPR itself.

The quoted example below is a bootstrap case (in section 12 in the MOAP proposal). The binding information for the 'stockquote' EPR is NOT known.

Regards,

Asir S Vedamuthu
Microsoft Corporation

From: public-ws-resource-access-request@w3.org [mailto:public-ws-resource-access-request@w3.org] On Behalf Of Doug Davis
Sent: Wednesday, February 24, 2010 7:28 PM
To: Ram Jeyaraman
Cc: public-ws-resource-access@w3.org
Subject: RE: MOAP v2


Unless we want the example to show a more advanced case of the WSDL being different from the MEX WSDL in the spec (e.g. having a different EPR), I would suggest that we keep it simple and not include the WSDL.  When the WSDL is not included then the binding information for the MEX operations would default to be the same as the binding information for the stockquote EPR itself.  There really isn't any other choice - but perhaps we could make this assumption more explicit by adding something to the section of MEX that talks about policy within an EPR.

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
The more I'm around some people, the more I like my dog.

Ram Jeyaraman <Ram.Jeyaraman@microsoft.com>

02/24/2010 10:16 PM

To

Doug Davis/Raleigh/IBM@IBMUS

cc

"public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>

Subject

RE: MOAP v2







Yes, the WSDL is child to the mex:MetadataExchange assertion. Thanks.

From: Doug Davis [mailto:dug@us.ibm.com]
Sent: Tuesday, February 23, 2010 3:30 PM
To: Ram Jeyaraman
Cc: public-ws-resource-access@w3.org
Subject: RE: MOAP v2


Ram - did you mean for the WSDL to be a child of the mex:MetadataExchange assertion?

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com<mailto:dug@us.ibm.com>
The more I'm around some people, the more I like my dog.
Ram Jeyaraman <Ram.Jeyaraman@microsoft.com<mailto:Ram.Jeyaraman@microsoft.com>>

02/23/2010 03:16 PM


To

Doug Davis/Raleigh/IBM@IBMUS, "public-ws-resource-access@w3.org<mailto:public-ws-resource-access@w3.org>" <public-ws-resource-access@w3.org<mailto:public-ws-resource-access@w3.org>>

cc

Subject

RE: MOAP v2











I like to suggest an addition to MEX Example 12-1 to show how to specify the binding information. The additions are highlighted below. Thanks.



Example 12-1: Endpoint reference to a Service Endpoint that supports mex:GetWSDL

(01) <wsa:EndpointReference ... >

(02)   <wsa:Address>http://services.example.org/stockquote</wsa:Address<http://services.example.org/stockquote%3c/wsa:Address>>

(03)   <wsa:Metadata>

(04)     <wsp:Policy>

(05)       <mex:MetadataExchange/>

 (06)         <wsdl:definitions name='StockQuoteMetadataExchangeMetadata'

  (07)                  targetNamespace='http://services.example.org/stockquote/metadata'

(08)                  xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'

(09)                  xmlns:mex='http://www.w3.org/2009/09/ws-mex'

(10)                  xmlns:wsp='http://www.w3.org/ns/ws-policy'

(11)                  xmlns:wsoap12='http://schemas.xmlsoap.org/wsdl/soap12/'>

(12)                  <wsdl:import namespace='http://www.w3.org/2009/09/ws-mex'

(13)                               location='http://www.w3.org/2009/09/ws-mex/metadataexchange.wsdl' />

(14)                   <wsdl:binding name='MetadataExchangeBinding' type='mex:MetadataExchange'>

(15)                       <wsp:PolicyReference

(16)                               URI='http://services.example.org/stockquote/MetadataExchangePolicy' />

(17)                       <wsoap12:binding transport='http://schemas.xmlsoap.org/soap/http' />

(18)                        ...

(19)                  </wsdl:binding>

(20)                   ...

(21)         </wsdl:definitions>

(22)     </wsp:Policy>

(23)   </wsa:Metadata>

(24) </wsa:EndpointReference>





From: public-ws-resource-access-request@w3.org [mailto:public-ws-resource-access-request@w3.org] On Behalf Of Doug Davis
Sent: Tuesday, February 23, 2010 11:45 AM
To: public-ws-resource-access@w3.org
Subject: MOAP v2



All,
after several rounds of talks between Oracle, Microsoft and IBM, the latest version of MOAP can be found here: http://www.w3.org/2002/ws/ra/10/02/MOAPv2.zip

The zip file contains all proposed spec changes and the changes include:

WS-EVD: no changes since last time

WS-Eventing/Enum/Frag/Transfer - look for edits done by "Dugv5":
- Only minor wordsmithing/editing to the definitions of the assertions

WS-MEX:
- there are two MEX docs in the zip file.
- the v1 version is the one sent to the WG a few weeks ago - no new edits were made.
- the v6 version contains all of the edits since v1.  All v1 edits were "accepted" so it should be easy to see the diff from v1.
- the edits were done in stages so that's why you'll see several Dugv? names.  It wasn't until round 4 of edits that I remembered to change the user name.

The MEX edits include:
- lots of minor editorial tweaks
- there's a new Terminology section.  This was added because it was felt that the two roles ('service endpoint' and 'metadata resource') needed to be defined and clarified.  People should read/review this carefully.
- the assertion was modified to advertise whether GetMetadata is supported - and the Dialect/Content params are now under GetMetadataSupported.
- there's a new section 12 about Bootstrapping.  This section was added to pretty much put all of the various pieces of the puzzle together when trying to bootstrap the process of talking to an endpoint.
- updated the xsd/wsdl for GetWSDL

Note: I'm planning on moving section 5 before section 4.  This will make it so that we define the new mex:Metadata type before we use it.  I didn't move it in the doc because then it would show up as modified.

Outstanding MEX issues for the WG to discuss:
- Example 8-5 - see comments in the doc
- Example 12-1 - see comment in the doc

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com<mailto:dug@us.ibm.com>
The more I'm around some people, the more I like my dog.

________________________________
Received on Thursday, 25 February 2010 05:45:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:18:24 GMT