BPMN as config: one vocabulary runs the model, the runtime, and the analytics

BPMN 2.0 lets you put arbitrary attributes in your own namespace on any element. The established BPM runtimes — Camunda and Flowable — both preserve those attributes through parsing and make them accessible at runtime. That's table stakes for the spec; neither engine violates it. What differs is how those attributes reach your code. In Camunda, a Java delegate pulls the current BPMN model instance, walks to the element in question, and reads the namespaced attribute through the generic model API