NEW ISSUE: Testing experience suggests requirements BWS40002 & BWS40003are too strict for services

[Eric Johnson <eric@tibco.com>]

Target: sca-wsbinding-1.1-spec-cd03

Title: Testing experience suggests requirements BWS40002 & BWS40003 are
too strict for services

Description:

Current normative statements:

When the SOAP.1_1 intent is required, the SCA runtime MUST transmit and
receive messages using only SOAP 1.1. [BWS40002]

When the SOAP.1_2 intent is required, the SCA runtime MUST transmit and
receive messages using only SOAP 1.2. [BWS40003]

Mike Edward's experience in creating test cases suggests that at least
two existing implementations (Axis, JAX-WS reference implementation) of
SOAP stacks will gladly accept SOAP 1.1 or SOAP 1.2 at a given endpoint,
and that restricting them to only allowing SOAP 1.1 or SOAP 1.2 is
actually tricky, if it is even possible.

This suggests that the normative statements, when applied to *services*
are perhaps overly strict.  Note that it still makes sense to have these
policy intents on references.

Proposal:

Change the normative statements to read as follows:
When the SOAP.1_1 intent is required on a reference, the SCA runtime
MUST transmit and receive messages using only SOAP 1.1. [BWS40002]

When the SOAP.1_2 intent is required on a reference, the SCA runtime
MUST transmit and receive messages using only SOAP 1.2. [BWS40003]