Re: mex.GetWSDL question

Hi Doug,
It's difficult because I suspect that clients would have a preference... 
However, we need to allow the minimal compliant implementation to be as 
simple as possible,  Having to generate a reference to the WSDL might be 
more challenging for an implementation in order to be ws-mex compliant 
(e.g. in case of a firewall).    So, I think my preference would be - keep 
it simple for the sake of the minimal requirements to ensure compliance. 
Perhaps recommend that the WSDL is inlined if possible (as you state). 
It's not great for the client to have the possibility of an extra MEP, but 
not a showstopper as it can still get the WSDL.
Thanks,
Katy



From:
Doug Davis <dug@us.ibm.com>
To:
ashok.malhotra@oracle.com
Cc:
public-ws-resource-access@w3.org
Date:
15/09/2010 13:57
Subject:
Re: mex.GetWSDL question




Yes if we added the attribute I would want "inlined" to be the default - 
I'm just not sure if we're adding good optionality or unnecessary 
complexity  :-)   Our constant struggle. 

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. 


ashok malhotra <ashok.malhotra@oracle.com> 
09/15/2010 08:49 AM 

Please respond to
ashok.malhotra@oracle.com


To
Doug Davis/Raleigh/IBM@IBMUS 
cc
public-ws-resource-access@w3.org 
Subject
Re: mex.GetWSDL question








How about if we add the attribute to allow you to specify the form of the 
data with the default being 'inlined'. 
All the best, Ashok 

On 9/15/2010 5:44 AM, Doug Davis wrote: 

I'm working through the testcases for MEX and I have a question about the 
GetWSDL operation.  Right now GetWSDL acts much like the old GetMetadata 
operation did in that it is up to the service to decide which form to 
return the metadata in - inlined, URL or EPR.  Now that GetMetadata allows 
the client to optionally ask for the metadata in a certain form, I'm 
wondering if we should allow the same option on GetWSDL.  So, perhaps 
something like: 
       <GetWSDL Content="xs:anyURI"? > ... </GetWSDL> 

Another option would be to be a bit more prescriptive about it and require 
the data be inlined if available, and a URL or EPR only be returned as a 
last change kind of thing. 

I'm inclined to keep it simple and not add the optional Content attribute 
but then I do think we need to push people towards the "simple" response 
as well, which means inlining the data.  If enough services choose to 
always return a reference (e.g. http://www.example/stockQuote?wsdl ) then 
clients might get annoyed with not having the option of "just asking for 
the darn data" so that they can avoid the extra MEP. 

Thoughts? 

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. 







Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU