W3C home > Mailing lists > Public > www-ws-desc@w3.org > March 2004

RE: proposal: make binding/operation/(input|output)/@messageLabel optional

From: <paul.downey@bt.com>
Date: Thu, 18 Mar 2004 15:16:29 -0000
Message-ID: <2B7789AAED12954AAD214AEAC13ACCEF0FFF209D@i2km02-ukbr.domain1.systemhost.net>
To: <tomj@macromedia.com>, <sanjiva@watson.ibm.com>, <www-ws-desc@w3.org>

i'm happy to +1 this so long as the default values for the 
messageLabel attribute are 'obvious'. 

That is I don't want to have to interpret complex rules to infer the 
default values for these attributes based upon the presence or order 
of input and output elements within a binding/operation. 

I'm puzzled about the impact on each of the MEPs identified in part 2
as well as any MEPs added in the future. What would tip the balance 
for me is a simple cheat-sheet: a table of the possible default 
messageLabel default values being considered. 


-----Original Message-----
From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]On
Behalf Of Tom Jordahl
Sent: 18 March 2004 15:00
To: 'Sanjiva Weerawarana'; 'www-ws-desc@w3.org'
Subject: RE: proposal: make
binding/operation/(input|output)/@messageLabel optional

+1 to making the messageLabel attribute optional on the binding operations.

Tom Jordahl
Macromedia Server Development

-----Original Message-----
From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
Behalf Of Sanjiva Weerawarana
Sent: Thursday, March 18, 2004 5:49 AM
To: www-ws-desc@w3.org
Subject: proposal: make binding/operation/(input|output)/@messageLabel

I know we discussed this before but the way things are is not
consistent. If there's exactly one input or output message in a
MEP there's no need to have the @messageLabel in binding either.

Can we please re-consider this? Look at the syntax summary
section and you'll see what I mean:


I'd like to make the attribute optional and keep the same rules
as with interface/operation/(input|output)/@messageLabel.


Received on Thursday, 18 March 2004 10:17:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:06:39 UTC