-
Key: BACM-17
-
Status: closed
-
Source: Thematix Partners LLC ( Mr. James Rhyne)
-
Summary:
The categorization mechanism was removed from the specification draft and replaced by requiring MEF, which effectively allows the specification of stereotypes in a conforming tool. As in UML, these stereotypes may carry properties not present in the model instances. Mentions of category and categorization remain present in the beta specification document.
-
Reported: BACM 1.0a1 — Wed, 19 Oct 2022 17:00 GMT
-
Disposition: Closed; No Change — BACM 1.0b2
-
Disposition Summary:
This issue was resolved prior to publication of the beta specification
The categorization mechanism was replaced prior to AB approval of the beta specification. The issue was recorded to preserve the history of changes. The beta specification requires MEF, which can be used to create profiles allowing for the categorization of BACM model elements by the definition of stereotypes and application of these stereotypes to model elements.
An issue has been created to address compliance requirements for MEF -
Updated: Mon, 2 Oct 2023 12:56 GMT
BACM — Remove or replace mentions of category and categorization
- Key: BACM-17
- OMG Task Force: Business Architecture Core Metamodel (BACM) 1.0 FTF