QVT14 — QVTr: checkonly PropertyTemplateItems

Given an enforced pattern such as:

a:A { b = b:B

}

there is an ambiguity as to whether the target of a.b is to be enforced remotely and then re-used here (checked) or enforced locally, so it is enforced locally.

This may perhaps be worked around using a Key, but the user must elaborate the pattern to redundantly define all the Key parts.

This may be worked around using a when pattern that relates "b" to its enforcement elsewhere.

Both the workarounds are tedious.

It is possible that there is some smart related to containment relationships that can do better, but more likely it just adds confusion and requires deeper user insight.

Suggest that remotely enforced PropertyTemplateItems can be annotated as checkonly to make the intent explicit.

a:A { checkonly b = b:B

}