NEW ISSUE: Should MAPs be divorced from the rest of the specification?

Title: Should MAPs be divorced from the rest of the specification?

Description:  As they stand, MAPs are effectively an application of EPRs 
specifically targeted toward supporting asynchronicity in the usual 
well-known WSDL MEPs.  As such, they may be removed without affecting 
the semantics or utility of EPRs.  The issue at hand is whether they 
should be.

Justification: EPRs are a vital contribution of WSA with clearly 
identified applications in other specifications.  While the generalized 
request/reply pattern that MAPs aim to support is clearly useful as 
well, this pattern may be defined simply by making the appropriate 
definitions in the WSDL binding document, instead of partly in the WSDL 
binding document and partly in the core and SOAP documents.

There is currently considerable discussion over the semantics and 
utility of MAPs.  This discussion does not need to be resolved in order 
for EPRs to be useful to the world.  With MAPs gone from the core spec, 
work and public comment on EPRs could proceed unencumbered.

Target: Core, bindings

Proposal: Remove section 3 of the core spec.  Remove all sections of the 
SOAP binding referring to Message Addressing Properties.  Define a new 
SOAP module in the WSDL binding document, containing the current MAPs, 
and insert the removed text describing the semantics of the MAPs and the 
SOAP properties in the WSDL binding document.

Received on Thursday, 24 March 2005 21:29:15 UTC