BACM11 — OWL translation does not handle ordered associations

Some composition ("owns_") associations are ordered but ordering does not translate to any OWL theorems.

Ordered associations are removed from the metamodel

All ordered associations have been removed from the metamodel. ValueStreamStage ordering is specified by a class (static) attribute whose value is undefined in the metamodel. Modelers should specify a value when creating instances/subclasses. This defines a strict ordering for presentation.
CustomerJourneyStages are ordered by a follows_2 relation that is many-to-many in the metamodel. In the case of many follows_2 successors, the metamodel does not allow criteria to specify which groups of successors are entered. It also does not allow criteria to specify which groups of predecessors are allowed to enter a successor. The modeler is expected to provide descriptive text and/or annotation text to describe the expected behavior. The alternative resolutions were deemed too complex for business architects and can be specified in execution-oriented models such as BPMN.
AbstractProcesses are ordered by the follows_1 relation with semantics and usage as described for follows_2.
Touchpoints can be ordered by the follows_3 relationship.