Re: [scxml] Support for Rhapsody/Statemate special "timeout" event

Hi Jim,

Thank you for the reply. Intuitively, I can imagine expressing the
special timeout event by using <send> with @delay in the enter action
of a state, and then using <cancel> in the exit action of the state.
But I'm wondering if any work has been done to prove this more
formally?

Also, are there any online public records documenting the discussions
that may have occurred on this subject? Maybe something on the mailing
list, or minutes from the meetings of the working group? Any
information you could provide on this would be extremely helpful.

Best regards,

Jacob Beard

On Mon, Oct 25, 2010 at 3:09 AM, Jim Barnett
<Jim.Barnett@alcatel-lucent.com> wrote:
> Yes, the SCXML working group thinks that it is possible to achieve the
> correct semantics using <send> with the 'delay' attribute.
>
> - Jim Barnett
>
> -----Original Message-----
> From: www-voice-request@w3.org [mailto:www-voice-request@w3.org] On
> Behalf Of Jacob Beard
> Sent: Sunday, October 24, 2010 7:36 PM
> To: www-voice
> Subject: [scxml] Support for Rhapsody/Statemate special "timeout" event
>
> Hi,
>
> >From reading the specification, it seems that the SCXML does not
> natively support the special "timeout" event described in Harel's
> paper "The Rhapsody Semantics of Statecharts"[0]. It seems to me that
> it may be possible to achieve similar or identical semantics in SCXML
> by using the send element and delay attribute. I was wondering if
> anyone had fully explored this possibility, or whether the SCXML
> working group had considered adding the timeout event to the SCXML
> specification.
>
> I'd appreciate any insight anyone could offer into this. Thanks,
>
> Jacob Beard
>
> [0] http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.3.6949
>
>
>
> -------------------------------------------------------------------------------------------------------------------
> 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.
>
>

Received on Monday, 25 October 2010 08:49:27 UTC