489 2004-01-23 09:09:21 +0000 CDL - Issue I-02 2005-01-04 20:34:37 +0000 1 1 1 Unclassified WS Choreography Spec: Concrete and QOS unspecified Other other CLOSED FIXED P2 normal -- 1 gritzinger gritzinger oldest_to_newest 1220 0 gritzinger 2004-01-23 09:09:21 +0000 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? 2119 1 charlton 2004-08-06 04:40:48 +0000 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. 2138 2 charlton 2004-08-12 16:24:05 +0000 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 2777 3 gritzinger 2005-01-04 20:27:21 +0000 SRT - Was talked about at the F2F. RECOMMENDATION - Due to Charlton's proposals at the F2F this should be marked as CLOSE FIXED.