RE: [SCXML] Reusing code through functions/templates

Thanks for the example. I still think I might be
missing something. That example claims to be an
<invoke> and <finalize> one but I do not see the use
of <finalize> there. 

Furthermore the <invoke> statements refer to the file
dialog.vxml which I do not see there ... maybe because
the file is just the whole example by itself in which
case I would expect to find the bits to be reused like
dialog.vxml#PlayAds but I see no other "PlayAds"
reference than the name of the state where <invoke> is
used.

What I am asking for is an example in which I can see
how params al passed from the invoker bits, how the
invoked ones process those params and return back to
the invoker context the result. The parametrized
invoked bits are supposed to be reusable as we have
been discussing of course.

Thanks again for your help. It is greatly appreciated.

-Nestor
--- "Barnett, James" <James.Barnett@aspect.com> wrote:

> Nestor,
>  We don't believe that <invoke> will change much in
> future drafts.
> There is an example of how to use it in appendix F.3
> of the current
> draft:
>
http://www.w3.org/TR/2006/WD-scxml-20060124/#invokeex
> 
> 
> - Jim
> 
> -----Original Message-----
> From: www-voice-request@w3.org
> [mailto:www-voice-request@w3.org] On
> Behalf Of Nestor Urquiza
> Sent: Monday, January 08, 2007 9:11 AM
> To: www-voice@w3.org
> Subject: RE: [SCXML] Reusing code through
> functions/templates
> 
> 
> Sounds great,
> Do you think the proposed <invoke> mechanism could
> change in future drafts? I am asking because 
> current
> implementations like commons-scxml could potentially
> implement the full invoke mechanism including
> <finalize>.
> 
> In regards to the returning data from <invoke> seems
> like the only way to get the result would be through
> <finalize> right? 
> I am wondering how a sample use case like the below
> should look when using <invoke>:
> 
> Build an external to invoke SCXML piece that returns
> the name of the pet knowing that:
> if animal type="dog" then name="Fido"
> if animal type="cat" then name="Kitty"
> if animal type="bird" then name="Tweety"
> 
> How the above SCXML piece of code should look like
> if
> it must done using SCXML?
> 
> >From the main SCXML we should be able to <invoke>
> several time within even different states the above
> bits passing param animal-type and getting back
> animal-name.
> 
> How the <invoke> node should look like to pass the
> param when invoking?
> 
> How the finalize node should look like to get the
> name
> back in the context variable animalName?
> <var name="animalName" expr="''"/>
> <finalize>
> <!-- what comes here? -->
> <assign name="animalName" expr="what.comes.here.?"/>
> </finalize>
> 
> Many thanks,
> 
> -Nestor
> > 
> > 
> > 
> > --- "Barnett, James" <James.Barnett@aspect.com>
> > wrote:
> > 
> > > Nestor,
> > >   We have two reuse mechanisms in mind.  First
> > off,
> > > <invoke> is
> > > definitely intended to be used so that one SCXML
> > > script can invoke
> > > another.  Note that in this case, the two
> scripts
> > do
> > > not share any
> > > context (but parameters can be passed in and
> out).
> > 
> > > Secondly, there is
> > > an include mechanism that will be expanded in
> the
> > > next draft that allows
> > > one state to include part or all of another
> script
> > > as if by copy, so
> > > that the copied material does share context with
> > the
> > > copying context.  
> > > 
> > > We hope that these two mechanisms will cover
> most
> > of
> > > the common reuse
> > > cases.
> > > 
> > > - Jim
> > > 
> > > -----Original Message-----
> > > From: www-voice-request@w3.org
> > > [mailto:www-voice-request@w3.org] On
> > > Behalf Of Nestor Urquiza
> > > Sent: Friday, January 05, 2007 4:05 PM
> > > To: www-voice@w3.org
> > > Subject: [SCXML] Reusing code through
> > > functions/templates
> > > 
> > > 
> > > Hello guys,
> > > 
> > > I have been discussing about possibilities to
> > reuse
> > > code within SCXML and I wanted to know about the
> > > plans
> > > to offer those possibilities within the SCXML
> > > Specification [1].
> > > 
> > > Basically wherever executable content exists
> there
> > > is
> > > a clear need to reuse code and to apply DRY some
> > way
> > > of grouping code in functions/routines/templates
> > is
> > > needed.
> > > 
> > > Currently I see the following possibilities and
> I
> > > would like to know about any others and of
> course
> > if
> > > there is already a preference among them.
> > > 
> > > 1. <invoke>
> > > 2. <script>
> > > 3. Just as a proposal, I think an XSLT
> templating
> > > alike mechanism (just in terms of the syntax)
> > could
> > > be
> > > used to be able to call passing parameters a
> given
> > > template that in turns could return some result.
> > > 
> > > Thanks,
> > > 
> > > -Nestor
> > > 
> > > [1]
> > >
> >
>
http://marc.theaimsgroup.com/?t=116241382900003&r=1&w=2
> > > 
> > >
> __________________________________________________
> > > Do You Yahoo!?
> > > Tired of spam?  Yahoo! Mail has the best spam
> > > protection around 
> > > http://mail.yahoo.com 
> > > 
> > > 
> > 
> > 
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam
> > protection around 
> > http://mail.yahoo.com 
> > 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam
> protection around 
> http://mail.yahoo.com 
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Received on Wednesday, 10 January 2007 10:14:02 UTC