UML24 — bodyCondition and isQuery

Constraint [7] in Kernel::Operation says:

"A bodyCondition can only be specified for a query operation"

Let us look at the definition of isQuery and bodyCondition:

bodyCondition: Constraint[0..1]
An optional Constraint on the result values of an invocation of this Operation.

isQuery : Boolean
Specifies whether an execution of the BehavioralFeature leaves the state of the system unchanged (isQuery=true) or whether side effects may occur (isQuery=false).

Question:

I am not sure why specifying a condition on the result of an operation is only limited to operations with no side effects. What is wrong with specifying a condition on the result of a non-query operation?

Body conditions are already a major source of logical uncertainty and inconsistency between OCL and UML. Relaxing
their usage would only make this worse: the OCL spec states “An OCL expression may be used to indicate the result
of a query operation”.
This also resolves 15768.
Disposition: Closed - No Change