Re: LC84b resolution

Regarding LC84b, I really think that the inability to specify the action
for each message represents a significant factoring error.  WS
Addressing provides a fine mechanism for doing this, but the capability
belongs in WSDL natively: abstractly, there is hardly anything more
fundamental to the definition of an interface than the notion of what is
intended to happen when a particular message is received.  

Grouping messages into operations (via MEPs) is useful, but in reality
it is somewhat arbitrary, as the same sequence of messages could be
grouped in multiple ways.  But when a message is sent from one party to
another, there is almost always some kind of intent, whether it is
explicitly stated or not.  Furthermore, if an action attribute has a
reasonable default value in WSDL, then its existence would place no
burden on users that don't care about it.

Given that WS Addressing does fill the need for this, those who are
using WS Addressing would have no reason to care that it isn't in WSDL
natively.  But since WSDL is such a fundamental building block of the
Web services stack of standards, and this seems so fundamental to the
notion of an abstract interface, I really think WSDL is where it

In summary, I will not ask the WG to reopen this, but I do think it is a
factoring error in the design of WSDL.

David Booth

> -----Original Message-----
> From: Jonathan Marsh []
> Sent: Thursday, June 09, 2005 5:34 PM
> To: Booth, David (HP Software - Boston)
> Cc:
> Subject: LC84a/b resolutions
> The remaining issues exposed in [1] have been resolved.
> Since the Operation Name Mapping Feature has been removed 
> from the Core spec (and is being generalized further in the 
> Primer, we felt that the remaining two issues LC84b [2] and 
> LC84c [3] could be closed with no further action.  If we 
> don't hear otherwise within two weeks, we will assume this 
> satisfies your concern.
> [1]
> [2]
> [3]

Received on Saturday, 25 June 2005 12:14:11 UTC