Ah, namespaced attributes - a great idea, I never even thought of it. However I'm not a big fan of squeezing many data items into a single attribute. I think that for multiple data items we'd still need separate attributes. But I could totally see something like this (note that I put <gpd:bendpoint> right within - there's no need to add another level of nesting that I can see): | <process-definition | xmlns="urn:jbpm.org:jpdl-3.2" | xmlns:gpd="urn:jbpm.org:jpdl-gpd-3.2" | name="simple" | gpd:width="469" gpd:height="439"> | <start-state name="start" gpd:x="150" gpd:y="25" gpd:width="140" gpd:height="40"> | <transition name="to_state" to="first"> | <gpd:bendpoint x="23" y="45"/> | <gpd:bendpoint x="45" y="67"/> | <gpd:bendpoint x="22" y="11"/> | <action name="action" class="com.sample.action.MessageActionHandler"> | <message>Going to the first state!</message> | </action> | </transition> | </start-state> | <state name="first" gpd:x="150" gpd:y="125" gpd:width="140" gpd:height="40"> | <transition name="to_end" to="end"> | .... and so on .... | I don't think separate sections are a good idea. This is XML, I mean we're not talking rocket science here. In addition, forms.xml could (and should, in my opinion) be merged in - the form declarations can go right with the task node declarations. If it were me I'd even merge in the task forms themselves (they are XHTML after all), though I think that might be pushing the limits of popular acceptance. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043467#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...