Adjust Drupal terminology

Problem/Motivation

We have some naming inconsistencies between BPMN.iO and what we use in Drupal so far. Here is a list of the main components and what they are called in BPMN.iO:

The whole thing is called a Process and the building blocks are:

1. Sequence? - I don't know what that's called but I'd like to define a name for that.
2. Event
3. Sequence Flow
4. Task

What BPMN.IO calls "Process" is currently called "Model" in ECA/Drupal.

"Event" is similar, that's OK.

"Sequence Flow" is OK, that can have a condition or not, there is no naming conflict at all.

"Task" is what we tend to call "Action" in ECA/Drupal, but we could also conclude, that a task in the process is what executes an action.

In our team meeting yesterday, we open this issue to change the label "Process" into "Model" and "Task" into "Action". But before we do that, we may want to think about that again. Maybe, it's the better choice to adjust our Drupal terminology and switch over to what BPMN.iO uses?

The reason I'm asking this now is because of several reasons:

• This is the domain of the modeller. Maybe BPMN specific or generic - but certainly not a Drupal domain.
• When we link to Camunda and BPMN.iO documentation, their text and screenshots will use their terms, not ours.
• When ECA users head over to BPMN.iO issue queues, their forum or other discussions, they will probably cause confusion, when they use Drupal specific terminology instead of BPMN terminology.

Those arguments seem strong reasons to change our terminology to what BPMN.iO uses instead of changing their labels. But as that terminology swaps over into ECA as well, I wonder on the other hand if we then become to BPMN focused or if those terms are generic enough that we can assume they could be OK for potentially other modellers too?

A lot to think about, but for our communications, that's very important to decide now - not after launch.