RE: some quick questions about scxml

1.  The point of <invoke> is that the state in question represents or
consists of the invocation of the external service (and will be exited
once the service returns).  That is the reason for restricting <invoke>
to being used only under <state>.  Note that <invoke> is really just a
syntactic convenience and can be replaced by <send> (plus appropriate
transitions), so the restriction on <invoke> doesn't really limit the
language any.

2.  There are lots of bugs in the schema, which we will hope to fix in
the next working draft.  

3.  '<normalize>' was an earlier name for <finalize>.  We'll replace all
occurrences of '<normalize>' with '<finalize>' in the next draft.  

- Jim

-----Original Message-----
From: www-voice-request@w3.org [mailto:www-voice-request@w3.org] On
Behalf Of Li Li
Sent: Monday, July 10, 2006 4:29 PM
To: www-voice@w3.org
Subject: some quick questions about scxml


Hi,
I'm just learning about scxml and found some questions about SCXML draft
dated 24 January 2006 (http://www.w3.org/TR/scxml/):

1) I wonder why <invoke> can only be used under <state>, unlike <send>
that
can be used in either <onentry> or <onexit>. What if I want to invoke an
external module only on exit?

2) The xsd doesn't seem to allow custom tags in <onentry> or <onexit>
element, even though the spec permits it, because "executablecontent"
group
in the xsd seems to miss a <xsd:any> definition.

3) Element <normalize> (F.3 Example of Invoke and finalize) doesn't seem
to
be described in spec or defined in the scxml xsd.

Thanks.

Li Li

Received on Tuesday, 11 July 2006 17:31:37 UTC