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 3104 - Exchange type
Summary: Exchange type
Status: RESOLVED FIXED
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Implementation/CR Issue (show other bugs)
Version: unspecified
Hardware: PC Windows 2000
: P2 normal
Target Milestone: --
Assignee: Martin Chapman
QA Contact: WS Choreography mailing-list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-11 13:19 UTC by Martin Chapman
Modified: 2006-07-18 19:49 UTC (History)
0 users

See Also:

Attachments

Description Martin Chapman 2006-04-11 13:19:19 UTC 
implementation issue from Gary:

. Currently the type field is optional

. However, if the associated channel type has identity information,
then without the message type, it is not possible to determine how
the message will be correlated with the channel instance and
choreography session

. Possibly we could add a rule that indicates that the type must be
specified if the channel type has identity details, as these details
would only be added when intending to execute/monitor choreo,
instead of just as a description
Comment 1 Martin Chapman 2006-07-18 19:49:21 UTC 
proposal at:
http://lists.w3.org/Archives/Public/public-ws-chor/2006Jun/0006.html

the text needs to be added after paragraph that begins "Within the exchange element, the OPTIONAL attributes ..."

Proposal accepted at 18th jult 2006 meeting.