Hi

Would like to discuss this issue at the next choreography conf call if 
possible. Although it does not impact an implementation, it appears 
redundant information in terms of a global model description, and would 
therefore propose removing it from the spec, unless someone has a 
suitable usecase to demonstrate its purpose.

In the spec, the only description associated with this attribute is:

"When the OPTIONAL |initiate| attribute is set to "true", an interaction 
activity MUST be marked as a choreography initiator. The default value 
for this attribute is "false"."

in section 6.2.3.

The information regarding which interaction (or interactions) will 
initiate a choreography are obvious from the description. This can 
either be one interaction (if a sequence), or multiple if there is a 
parallel or choice construct.

If the purpose of adding this flag was in support of the 
'createInstance' attribute in BPEL, then it still is not adequate, 
because it is not clear whether the initiate flag is supposed to 
indicate the interactions that initiate a choreography session, or are 
they supposed to indicate which interactions initiate a session at each 
service endpoint? Surely this information is implied by the lifetime of 
the channel instance representing the endpoint session.

If the proposal is accepted, then the following minor changes are required:

1) Section 6.2.3:
Remove attribute from syntax: "initiate="true"|"false"? " Remove sentence "When the OPTIONAL |initiate| attribute is set to 
"true", an interaction activity MUST be marked as a choreography 
initiator. The default value for this attribute is "false"."

2) Remove the attribute from the WS-CDL schema


Regards
Gary