[SCXML] Rejected: allowing only a single <final> state

We have provisionally decided to reject the following change request.  Now that we have decided to allow <onentry> and <onexit> as children of <final>, there are legitimate uses for multiple <final> children since they may contain different executable content.  

 

>From Torbjorn Lager:
 
Since two <final> states can differ only in ID (since they have no children) it
doesn't make much sense to allow more than one <final> as a child of <scxml>.