SACM11 — Events should be able to be Associated with all Kinds of ModelElements

Not just exhibits have events that affect them or otherwise relate to them. This is also relavent to what the elements represent.

An event might be associated with more than one element
For example, one bug fix that simultaneously change several code exhibits/artifacts.

Deferred as still valid for SACM

There needs to be a clear distinction between properties of model elements and properties (assertions) concerning domain objects being represented. It also may be worth thinking in terms of contestable vs. uncontestable assertions. (There may be some fluidity between these two concepts depending on context.) Are properties merely uncontestable assertions? This issue should be taken forward with the resolution of the change management and version control issue (16281) and the resolution of the property vs. assertion issue (16506), which were both deferred in Ballot 4 (the 2nd Ballot of the SACM 1.1 RTF).