You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a lot of tools exchanging BPMN files in our demo scenarios. It is essential for compatibility that every tool keep intact or even proceed correctly extensions provided by another tool.
To achieve this goal we should start with consistent documentation on respective extensions provided by every tool. We should agree on common format of this documentation and then ask every vendor to fill respective document for a tool.
It will be reasonable to create separate Git repository under BPMN MIWG space to hold this documentation and track its development.
Please everybody comment and give your suggestions.
The text was updated successfully, but these errors were encountered:
We have a lot of tools exchanging BPMN files in our demo scenarios. It is essential for compatibility that every tool keep intact or even proceed correctly extensions provided by another tool.
To achieve this goal we should start with consistent documentation on respective extensions provided by every tool. We should agree on common format of this documentation and then ask every vendor to fill respective document for a tool.
It will be reasonable to create separate Git repository under BPMN MIWG space to hold this documentation and track its development.
Please everybody comment and give your suggestions.
The text was updated successfully, but these errors were encountered: