Question on SCXML algorithm

Hello,

 

I am the CTO of DS SIMULIA Corporation.  I am looking at adopting SCXML for a controller for multiphysics simulation - a far cry from the voice applications which reference SCXML.  I am very excited about the emerging standard as Haral state charts are quite useful for some of our applications.

 

I have a question on the "Algorithm for SCXML Interpretation from the Working Draft 29 document.  In procedure addStatesToEntry, when evaluating the block isCompoundState(s), there is a call to getDefaultInitialState(s).  I cannot find this function defined in the document.  Presumably it returns a single value of a state id.  However, in my understanding of SCXML that the target of the sole transition of an <initial> element can be any decendant (not necessarily direct) of the composite state. If the composite state has parallel grandchildren then can't there be multiple targets within that parallel region?   If so, then how do I interpret getDefaultInitialState(s) in the algorithm.

 

It may be my lack of understanding of SCXML but I sure would appreciate some help here.  I am very excited from what I see so far and this seems very applicable to our domain.  I would be glad to update you on our progress in the future.

 

Thanks for your help in advance.

 

Bruce

 

 

Cordialement / Best regards, 

________________________________

Bruce ENGELMANN
SIMULIA Product Dev & Research
Office: +1 401276 4460
Bruce.ENGELMANN@3ds.com <mailto:Bruce.ENGELMANN@3ds.com> 
Dassault Systèmes I www.3ds.com <http://www.3ds.com>  

Visit us at: www.simulia.com <http://www.simulia.com> 
SIMULIA - Dassault Systemes Simulia Corp. 166 Valley Street - 02909-2499 PROVIDENCE - United States

  <http://www.simulia.com/auc2008> 

 

 



This email and any attachments are intended solely for the use of the individual or entity to whom it is addressed and may be confidential and/or privileged.  If you are not one of the named recipients or have received this email in error, (i) you should not read, disclose, or copy it, (ii) please notify sender of your receipt by reply email and delete this email and all attachments, (iii) Dassault Systemes does not accept or assume any liability or responsibility for any use of or reliance on this email.For other languages, go to http://www.3ds.com/terms/email-disclaimer.

Received on Monday, 17 May 2010 22:38:51 UTC