Categorisation of tool

[max-melb]

The page is useful as a very basic list on the tools that use BPMN. It would be more useful to have another column showing the categorisation of a tool, i.e whether the tool is a process diagram tool, process modelling tool (able to define all attributes of the elements as BPMN specification), and/or a process orchestration tool (able to implement executable BPMN).

[dialogik]

Yes, this would be a very handy enhancement!

If you already have precise ideas on how to enhance the data model (data.json) or about the implementation in HTML/JavaScript, feel free to hand in your enhancements as a pull request.

[max-melb]

Looking at the XML, I would suggest to have a data field for "Category" with the domain of "mapping, modelling, simulation, execution" and combination of these values. Difference between mapping and modelling is mapping only act as drawing tool like Visio, whereas modelling allows entering of BPMN related attributes. Simulation and execution are both self explanatory.

[dialogik]

I struggle with the words and the combination mapping/modeling, but I like the idea of these four categories. What do you think about sketching (modeling with visual output only, e.g. Visio) and modeling (deep modeling with attributes and relations, export of models e.g. as XML, etc.)?