- From: Torbjörn Lager <torbjorn.lager@gmail.com>
- Date: Wed, 21 Mar 2007 03:05:19 +0100
- To: "Barnett, James" <James.Barnett@aspect.com>
- Cc: "Serge Voloshenyuk" <serge_voloshenyuk@yahoo.com>, www-voice@w3.org
On 3/20/07, Barnett, James <James.Barnett@aspect.com> wrote: > > > What is the ID used for? If you look in the algorithm, you'll see that it > requires the implementation to generate a unique ID for each invocation. > This allows the *.Done events to be assigned to the correct states and > finalize tags. Do you want the ID reflected at the markup level? But how can you match on the ID.Done event if the ID is machine generated? That's why I felt the need to use a human-generated one. (Perhaps the state's ID would do, since a state containing an <invoke> cannot at the same time contain a <final>?) - Torbjörn > > - Jim > > > > ________________________________ > > > From: www-voice-request@w3.org [mailto:www-voice-request@w3.org] On Behalf > Of Serge Voloshenyuk > Sent: Tuesday, March 20, 2007 5:22 PM > To: www-voice@w3.org > Subject: Re: SCXML: New version of Synergy SCXML > > > >BTW, I felt the need to introduce an 'id' attribute for <invoke>... > perhaps > > >there's another way to do it? > > > > You have id of the state which invoke it. State can't have several > <invoke>s. > > > > ________________________________ > > > Be a PS3 game guru. > Get your game face on with the latest PS3 news and previews at Yahoo! > Games.
Received on Wednesday, 21 March 2007 02:05:22 UTC