-
Key: BACM12-14
-
Status: open
-
Source: Thematix Partners LLC ( Mr. James Rhyne)
-
Summary:
In MOF, the instance association represents the relation between a meta-entity and its model instances. BACM allows model instances to be classes and associations, effectively making an instance a specialization of the meta-entity. BACM also allows the modeler to create specialization relations between model elements.
To support the metamodeling notion in OWL-based tools, it is necessary to be able to distinguish specialization created by the modeler from meta-entity specialization that is created by the tool, e.g. when creating a model instance of the meta-class "Capability". The instancing process in a tool can be complex. For example, instancing a BACMBinDirRelation such as "expects_o" requires the creation of a subclass of "expects_0" (and noting that it is a meta-class relation), and creating two ObjectProperties that are sub-ObjectProperties of "expects_0.to_expects_0" and "expects_0.from_expects_0". The tool should prevent the modeler from changing any of the these specialization relations or to deleting any of the created elements. The tool should only allow the modeler to delete the entire instance or to add axioms and assertions that do not change the semantics of the instance with respect to its meta-entity. Consequently, the tool must be aware of these specializations. -
Reported: BACM 1.1b1 — Wed, 25 Jun 2025 17:00 GMT
-
Updated: Wed, 25 Jun 2025 17:00 GMT
BACM12 — Define an annotation property to capture the meta relation in models
- Key: BACM12-14
- OMG Task Force: Business Architecture Core Metamodel (BACM) 1.2 RTF