Difference between revisions of "Design principles: Clone names"
Revision as of 00:09, 31 July 2006
The v3 design principle states that when it comes to the interpretation of RIM-derived models one should be able to derive the full computable semantics of the model without having to look at the names of cloned classes. The purpose of the clone names is to both ensure unique type names for code generation and instance validation, as well as to make those semantics clear to the average human reader.
Two open issues:
- The above lore needs to be formally voted upon to document it, or if already ahs been voted upon we need a link to a document that contains the description.
- The description needs to be clarified to state that this extents to all RIM classes, and not (as some say) just those classes that are part of the normative or "upper" part of the RIM.