- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Thu, 9 Jun 2005 14:24:32 -0700
- To: "Arthur Ryman" <ryman@ca.ibm.com>, "Sanjiva Weerawarana" <sanjiva@opensource.lk>
- Cc: <public-ws-desc-comments@w3.org>
Thank you for your comment, which we tracked as LC71 [1]. The WG was able to agree on defaulting @pattern to the URI representing "in-out". If you find this resolution unacceptable please let us know within two weeks. [1] http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC71 > -----Original Message----- > From: public-ws-desc-comments-request@w3.org [mailto:public-ws-desc- > comments-request@w3.org] On Behalf Of Sanjiva Weerawarana > Sent: Wednesday, October 27, 2004 9:07 AM > To: public-ws-desc-comments@w3.org > Subject: default interface/operation/@pattern > > > We would like to see the "pattern" attribute of "operation" elements > defaulted based on the contained <input> and <output> elements for > those patterns where that is unambiguously possible. The component > model will continue to have the current behavior - this is only > a syntactic convenience. > > Requiring all users to remember the values of the pattern URIs > when the value is patently obvious from the <input> and/or > <output> elements makes the language overly cumbersome with > no value. We would like this extra complexity removed. > > Note that this is only a default - if someone else were to define > a pattern with only one <input> and no <output>s then they can > still live happily with the user explicitly setting the value. > > Sanjiva, on behalf of IBM. >
Received on Thursday, 9 June 2005 21:24:46 UTC