1) Creative.... and I think it can be defended if is is just explained in enough detail in the docs. 2) First of all, I did not use superstates once (did not have the real need), secondly and IANAE, BPMN has the notion of embedded and reusable subprocesses (the latter are renamed to call activity if I am informed correctly). Though there is no relation between the type and the way they should be displayed, I think that can be leveraged: - collapsed can be either subprocess or superstate. - expanded inline: superstate - 'new tab/page': the content of the subprocess node Where e.g. a doubleclick on a collapsed one opens it expanded inline or on a new tab... Bruce Silver writes about this in http://www.brsilver.com/wordpress/2008/09/15/concepts-and-terminology-in-... Regarding the connection of a sequenceflow into a node I have no clear picture yet... if I find the time I'll try to read about it. Terminology wise: 1) & 2) Yes, I agree and it might be nothing more than 'getting used to' or pose a real problem. Not sure yet 3) I often 'abused' the task node, since in many of the processes I worked on could be either 'signalled' via an incomming b2b message or a from a form on a web page that was completed by a human. So this to me is no problem... this 'abuse' will continue I think after reading about the private, abstract, global processes and the B2B arena. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205961#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...