bpmn-miwg/bpmn-i18n

Internationalization Extension for BPMN, CMMN and DMN

bpmn-i18n's Issues

Idea: specify language for all default attributes

The proposal should include some way to specify which language the default attributes represent. Otherwise importing tools will have to guess which language to map these values to.
Maybe as an attribute of the 'definitions' node or as an extension element to that node (not sure if that is allowed).

Suggest declaring available languages

There are almost 200 two letter language codes in ISO 639. There are several scenarios in which knowing which ones are intended to be available may be useful, for example:

1. Rendering process diagrams in all available languages by just checking if there is at least one translation element for each language is not very efficient ;
2. Validating which languages are expected and therefore detecting missing translations is much more helpful to users than just having to check every element.

In fact, I notice Trisotech already include a triso:translationLanguagesattribute on the definitions element. I suggest we bring this into the existing extension.