- From: Mark Baker <distobj@acm.org>
- Date: Wed, 30 Jun 2004 23:27:37 -0400
- To: Hugo Haas <hugo@w3.org>
- Cc: www-ws-desc@w3.org
Hi Hugo, On Wed, Jun 30, 2004 at 11:34:49AM +0200, Hugo Haas wrote: > So, I think that at this point the debate is on the syntax at this > point. Ok, good. > Therefore, I am happy with Dave's proposal, along with the defaulting > mechanism he proposes. I am too. It's a lot more "in your face" than I was expecting would ever be proposed, but that's fine by me. In a similar earlier proposal of mine, I didn't even attempt[1] to touch the interface, because I knew it would be immediately shot down due to the perceived value of (ahem) "protocol independence". I would also suggest that some prose be added to make the implication of using this attribute clear to developers. Specifically, they need to be aware that when it's used, an operation name becomes purely documentation. So for this example ... <wsdl:operation name="putStockQuote" wsdl:webMethod="PUT"> the WSDL spec needs to be clear that the semantics of the contract are PUT, and not putStockQuote. i.e. a successful response from a document being submitted to that endpoint, only means that PUT was invoked, not that putStockQuote was invoked. Perhaps making name optional would be useful, and discouraging its use when "webMethod" is used?? Dunno. BTW, I think we can do better than "webMethod" as the name, since it's not just for "Web" ("uniform"?) methods, it's for any method of an underlying application protocol, e.g. FTP STOR, SMTP DATA, etc.. What about "protocolMethod" (ick)? Hmm, can't think of a good one. > I would propose the friendly amendment to tie the webMethod attribute > to the SOAP Web Method Feature, by adding a paragraph in Part 3, in > the SOAP binding, saying that the value of the webMethod attribute > sets the value of the SOAP Web Method Feature > http://www.w3.org/2003/05/soap/features/web-method/Method property. Sounds good. I'm sure Dave intended that. [1] http://lists.w3.org/Archives/Public/www-ws-desc/2003Jan/0103.html Mark. -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca Seeking work on large scale application/data integration projects and/or the enabling infrastructure for same.
Received on Wednesday, 30 June 2004 23:41:56 UTC