This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 489 - CDL - Issue I-02
Summary: CDL - Issue I-02
Status: CLOSED FIXED
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Spec: Concrete and QOS (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: --
Assignee: Greg Ritzinger
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-23 09:09 UTC by Greg Ritzinger
Modified: 2005-01-04 20:34 UTC (History)
0 users

See Also:

Attachments

Description Greg Ritzinger 2004-01-23 09:09:21 UTC 
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?
Comment 1 Charlton Barreto 2004-08-06 04:40:48 UTC 
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.
Comment 2 Charlton Barreto 2004-08-12 16:24:05 UTC 
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
Comment 3 Greg Ritzinger 2005-01-04 20:27:21 UTC 
SRT - Was talked about at the F2F. RECOMMENDATION - Due to Charlton's 
proposals at the F2F this should be marked as CLOSE FIXED.