556 2004-02-23 12:35:02 +0000 Dependency to other technologies - Section 3.5.6 2005-01-04 20:39:12 +0000 1 1 1 Unclassified WS Choreography Spec: Concrete and QOS unspecified Other other CLOSED FIXED P2 normal -- 555 1 gritzinger gritzinger oldest_to_newest 1374 0 gritzinger 2004-02-23 12:35:02 +0000 > Section 3.5.6: > Monica. Please specify what specifications of which you make > reference. An agreement protocol doesn't exist in web services, unless > this is the > infrastructure coordination/transactional evolving capabilities. Is > this the meaning of this statement? > David. Perhaps a "common understanding" would be better than > "agreement" as in "the Roles in the Choreography have a common > understanding of the outcome". > Monica. If this relates to WS-CAF, suggest this be a team discussion > item for specific reference (Note: Do we approach by requirement or by > specification?). Implicit dependencies exist. Should we pose these in > a separate document or section of this overview? > David. I agree that dependencies exist and need to be discussed. 2085 1 charlton 2004-07-13 15:06:45 +0000 After further review and discussion, a short list of specifications have been identified as either critical or optional to ws-chor: --> Critical * BPEL * WSDL * XPath/XQuery --> Optional * BPMN * BPSS * WS-Coordination * WS-Reliability * WS-Addressing There are others which I am continuing to investigate and will discuss. I would like to enter the above critical and optional dependencies as a part of a general discussion point on ws-chor dependencies. The BPEL, WSDL and XPath dependencies are critical to ws-chor and we will need to resolve which versions we will support in 1.0. The BPMN, BPSS and WS-Coordination are less critical yet may impact ws-chor and thus need to be discussed. I will present more details on these in this bug description. 2122 2 charlton 2004-08-06 06:30:01 +0000 I believe we've addressed - at least conditionally - the BPEL, WSDL and by extension the XPath/XQuery dependencies. As to the rest, Monica has commented as follows: - WS-Coordination WS-Coordination Framework, WS-BTP are open and emerging standards. WS-C is proprietary currently. - WS-Reliability Same holds true here (WS-ReliableMessaging is proprietary). - WS-Addressing WS-MessageDelivery also applies. At least three groups, WS-CAF, WS-Reliability and WS-BPEL are working on an abstract content model that abstracts away from such a dependency (i.e. a proprietary specification - lock in avoided as well). We definitely need to ensure that we conform to open standards. I propose that as far as WS-Reliability and WS-Addressing are concerned, we hold to the WS-CAF/WS-Reliability/WS-BPEL abstract content model (vs. WS-ReliableMessaging and WS-MessageDelivery). I propose that as far as WS-Coordination is concerned, we hold to the WS-Coordination Framework and WS-BTP standards (vs. WS-C). 2673 3 martin.chapman 2004-12-01 16:40:07 +0000 *** Bug 557 has been marked as a duplicate of this bug. *** 2781 4 gritzinger 2005-01-04 20:38:05 +0000 SRT - Was talked about at the F2F. RECOMMENDATION - Due to Charlton's proposals at the F2F this should be marked as CLOSE FIXED.