UML241 — UML 2.4: NamedElement.ownedRule could be ordered

Graphically, Constraints appear independently so the unordered
characteristric of NamedElement.ownRule seems sensible. However in a textual
rendering ordering is appropriate.

For instance, Constraints may sensibly be layered so that simple Constraints
come first and act as guards against redundant evaluation of later
Constraints.

For instance, when auto-generating a specification such as the OCL
specification, a specific ordering is required in the generated output.

Please change to

.

The ownedRule property is actually on Namespace, not NamedElement.
In general, it is not appropriate to add constraints to the abstract syntax in order to capture presentation issues, like the
textual rendering of an order. Further, the UML semantics provide no requirement that ownedRules be evaluated in
any particular order, so, as far as UML is concerned, there is no underlying meaning to such ordering.
Disposition: Closed - No Change