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 1001 - CORRELATION OF CHANNEL INSTANCES
Summary: CORRELATION OF CHANNEL INSTANCES
Status: CLOSED FIXED
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Last Call Comment: Confirmed Closed (show other bugs)
Version: unspecified
Hardware: PC Windows 2000
: P2 normal
Target Milestone: --
Assignee: Martin Chapman
QA Contact: Martin Chapman
URL: http://lists.w3.org/Archives/Public/p...
Whiteboard:
Keywords:
Depends on:
Blocks: 1496
  Show dependency treegraph
 
Reported: 2005-01-10 16:01 UTC by Martin Chapman
Modified: 2005-09-28 21:33 UTC (History)
0 users

See Also:


Attachments

Description Martin Chapman 2005-01-10 16:01:05 UTC
Currently it is not possible to monitor messages for different channel
instances, and associate those separate channel instances to the same
choreography session. Correlation information is required to bind the
multiple channel instances to the same choreography session.

Messages on a particular instance of a channel type should also not be
expected to all have the same 'identity' field, as a means of
correlating the message to the channel instance. This places unnecessary
constraints on the author of a business protocol.

Regards

Gary and Steve
Comment 1 Martin Chapman 2005-02-14 20:35:52 UTC
From meeting on 11-jan-05
http://lists.w3.org/Archives/Member/member-ws-chor/2005Jan/att-0002/2005-01-
11_WS-Chor_Notes.txt:

Discussion deferred as deemed to be a technical issue.
Comment 2 Martin Chapman 2005-03-08 10:37:04 UTC
Discussed at feb-mar 05 F2F:

Issue 1001 http://www.w3.org/Bugs/Public/show_bug.cgi?id=1001
Summary: CORRELATION OF CHANNEL INSTANCES 
URL: 
http://lists.w3.org/Archives/Public/public-ws-chor-comments/2005Jan/0006.html 
Proposal Outline: 
http://lists.w3.org/Archives/Public/public-ws-chor/2005Feb/0032.html 
Gary: Outlines proposal above 
NOTE: To establish the association with the channel instance, the message that 
initializes the alternate identity must also contain the value of at least one 
other identity field that is associated with that channel instance. 
<m2> 877 is Monica (changed phones) 
CONSENSUS that this issue does need to be resolved for CDL V1.0 (or whatever 
the 
number is) 
Nick writes on board: 
<choreo> 
<session> 
<channel A> 
<channel B> 
</session> 
</choreo> 
Summary: Clear need for operators on channels (types and/or instances) to 
define 
relationships. We need to understand clearly what it is that we need to express 
and then decide where it needs to be documented in a CDL specification. 
Steve: summarised above and suggested that 1026 and 1027 are then not issues 
anymore because they get solved by solving 1001 
... We shall come back to these two issues to check 
Nick: Summarises why it is not enough with the proposal from Enigmatec. An 
issue 
of finalization was raised and Charlton raised issue of monitoring. 
Steve: After Nick's comments Steve says that we need to handle both identity 
name and conversation name. 
This then enables proposal for 1001 for both 1001 and 1026 
Comment 3 Martin Chapman 2005-07-20 14:40:41 UTC
proposal agreed at meeting on 31 may 05:
http://www.w3.org/2002/ws/chor/5/05/31-minutes.html


Editors report incorporation into spec at jun/jul f2f:

http://www.w3.org/2002/ws/chor/5/06/F2Fminutes.html

Moved to closed.
Comment 4 Martin Chapman 2005-09-28 21:33:17 UTC
changed to closed confirm since editors have incorporated into spec