W3C home > Mailing lists > Public > public-ws-chor@w3.org > November 2004

Re: Multiple participants

From: Gary Brown <gary@enigmatec.net>
Date: Wed, 10 Nov 2004 09:42:56 -0000
Message-ID: <006701c4c709$ac420f20$4b00a8c0@LATTITUDEGary>
To: "Furniss, Peter" <Peter.Furniss@choreology.com>, <public-ws-chor@w3.org>
MessageOn your first point, I would be interested in such an example aswell. However, when I originally posed this problem, the case I was thinking about was where you would have a workunit (with repetition) that was performing an enclosed choreography, which contained the relevant channel variable(s) and interactions for dealing with a single participant instance. This would mean that if CDL had the ability to concurrently perform multiple instances of this choreography, each one of the sub-choreography instances would simply be managing its own channel instance. Therefore it would not have been necessary to manage an array.

This is probably a question for Nick, but possibly all that is required to be able to handle such an example as an array, would be to have an array of channel variables, as these represent the 'instance' details for the connection. The participant type and relationship type details would be the same across all of the channel instances, so I don't believe we would need to support an array of them.

However, I am not sure how we would define a variable that is an array of a particular channel type, or as you have pointed out, how it would be referenced.

On your second point, I found that this parsed ok:

guard="cdl:globalizedTrigger("cdl:getVariable('var2')",'yourrole', "cdl:getVariable('var3')", 'myrole')"

so the 'getVariable' function parameters should probably all be single-quoted.

Regards
Gary
Received on Wednesday, 10 November 2004 09:43:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 01:01:10 GMT