Re: SCXML: interpretation algorithm

Ales,

You raise/comment on a number of issues here.  Here are our responses to
your individual points.

 

1.        (Illegal configurations).  Yes, you're right.  This is
definitely a bug, and it's a big enough one that it won't be fixed in
our upcoming draft.  However, we are tracking the issue and will fix it
before the standard is finalized.

2.       (parallel transition order).  This will be fully specified in
the upcoming draft of the specification.

3.       (Shallow history of parallel state is useless)  You're right,
it is pretty useless, but we have decided to leave the definition as it
is to keep things simple.  You can get the behavior you want by putting
a shallow history state in each parallel sibling, and then using the set
of them as the target for your transition.  This is somewhat more
verbose, of course, but we prefer it to adding a special case to the
definition of history states.

 

Now for your comments on the open issues:

 

1.        We are removing the restrictions on <invoke> in the upcoming
draft.

2.       We are considering a proposal for an iterative construct, but
have not made a final decision.   It will not be in the upcoming draft,
but may be in a future one.

3.       We are not currently planning to change the notation.

4.       We are fully specifying parallel transition order.

5.       We still need to revise error naming and handling.  You will
not see any changes in the upcoming draft, but will in a future draft.

6.       I think that your comment here is based on a misunderstanding.
An SCXML session may use <send> to send  a message to its own internal
queue, but it may not send a message to the internal queue of a
different session.  All messages sent between SCXML sessions go the
external queue.

 

Thank you for your comments, and we look forward to your response to our
upcoming working draft.

 

-          Jim Barnett


					
-------------------------------------------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.