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

Re: mex.GetWSDL question

From: ashok malhotra <ashok.malhotra@oracle.com>
Date: Wed, 15 Sep 2010 05:49:08 -0700
Message-ID: <4C90C0C4.6010307@oracle.com>
To: Doug Davis <dug@us.ibm.com>
CC: public-ws-resource-access@w3.org
  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. 
Received on Wednesday, 15 September 2010 12:53:13 GMT

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