[news.eclipse.modeling.mdt.uml2.ocl] Built-in validation for read-only o

[Andreas Maier <maiera@xxxxxxxxxx>]

Hi,
in our CIM mapping to UML, we are mapping the Write qualifier in CIM to
the isReadOnly UML attribute. In CIM, associations have ends that do not
have the Write qualifier set. This consequently results in UML
association ends that have isReadOnly set to true.

When I run model validation, the following built-in validation rule pops
up due to this:

Non-navigable property '<<property_Constraints, cIM_Reference>>
<Property> UserOfService : CIM_LogicalFile [0..*]' is marked as read-only.

It may be that the semantics of writeability is slightly different
between CIM and UML. In CIM, it means that a client application should
expect to be able to modify the property value.

My questions are:

- What is the purpose of this built-in validation rule ?

- What is the exact semantics of isReadOnly in UML ? (i.e. unmodifiable
  vs. not volatile)

Andy