This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Issue I-02. Should Portable Choreography message content be extended to include other items such as SOAP headers, security, etc or should this be included in the Channel?
Given how WSs are not necessarily bound by transport - XML over HTTP, and JMS are valid transports in addition to SOAP - I don't believe we should have the Portable Choreography message content extended to include anything specific to a transport. However, with respect to our dependency on WS-Security, and its level of abstraction, we may want to consider having the Portable Choreography Channel Variable extended to include QoS configuration for security, coordination and reliablemessaging.
I propose that we extend Concrete Choreography to include QoS configuration, in particular for: - security - coordination - reliableMessaging The detailed semantics and policies specific to security, coordination and reliableMessaging are outside of CDL. In CDL a reference is provided to - 'bound' the variables and their usage - select service level as a directive for the use of these QoS
SRT - Was talked about at the F2F. RECOMMENDATION - Due to Charlton's proposals at the F2F this should be marked as CLOSE FIXED.