allowing <onentry> and <onexit> inside <final>

We have provisionally decided to accept the following change request for
inclusion in the next draft of the spec.  The <final> element will be
allowed to have <onentry> and <onexit> children:

 

>From Serge Voloshenyuk:
 
Hi
It could be useful to have <onentry> and <onexit> in <final> state.
<onentry>: for send results
<onexit>: for data cleanups.
 
Regards, Serge.