RE: SCXML cancel event?

But cancel seem really basic (to me), especially since there is a sendid
and delay, this implies
an event is cancelable and should be a base part of SCXML.   For a
standard to be standard 
there needs to be some basic commonality between various "scxml
implementations", and cancel
is the compliment of send.   If all implementations have to implement
cancel then there is little 
portability of SCXML documents.   Said another way if too much is
"platform" specific, 
it there really any "standard"?
 
Ross
 

________________________________

From: Barnett, James [mailto:James.Barnett@aspect.com] 
Sent: Tuesday, December 18, 2007 6:11 AM
To: Yakulis, Ross (Ross); www-voice@w3.org
Subject: RE: SCXML cancel event?



We had <cancel> in an earlier draft, then took it out as an attempt to
simplify the basic set of executable content.  We will be reviewing
<send>/<invoke> functionality in a future draft.  In the meantime, if
you need <cancel>, you can add it as a platform-specific extension.  (In
general, we intend for platforms to provide extra executable content
suitable for their specific applications.)

 

- Jim

________________________________

From: www-voice-request@w3.org [mailto:www-voice-request@w3.org] On
Behalf Of Yakulis, Ross (Ross)
Sent: Monday, December 17, 2007 4:30 PM
To: www-voice@w3.org
Subject: SCXML cancel event?

 

Should the spec have a <cancel/> tag that allows on to cancel a delayed
event? 

Ross Yakulis