3106 2006-04-11 13:23:19 +0000 Channel Passing 2006-08-01 21:20:40 +0000 1 1 1 Unclassified WS Choreography Implementation/CR Issue unspecified PC Windows 2000 RESOLVED REMIND P2 normal -- 1 martin.chapman martin.chapman public-ws-chor-comments oldest_to_newest 9140 0 martin.chapman 2006-04-11 13:23:19 +0000 Implementation issue from Gary: . Business messages can be correlated to a channel instance and choreography session using identity information derived (through the use of token locators) from the message contents . However, channels passed over other channel instances do not carry any business information, and therefore how can they be correlated? . Approach taken in pi4soa is currently restricted to use of WSAddressing endpoint reference, which it stores the identity token values of the channel on which the exchange is occurring – however this is not interoperable, as it relies on prior knowledge of the identity token encoding within the endpoint reference . Channel passing is also restrictive, as it can only be passed within its own exchange . This is currently necessary to enable the formal verification to identify where the channels are being passed . However, for subsequent versions of CDL, we should investigate the ability to describe message exchanges where a channel's details are passed as part of a business message, but still remain explicit enough for formal verification. 10968 1 martin.chapman 2006-08-01 21:20:40 +0000 at meeting on 1st august 2006 it was accpeted to defer this issue to version 2, since a workaround exists. Marked this as resolved, remind.