-
Key: BACM-68
-
Status: closed
-
Source: Thematix Partners LLC ( Mr. James Rhyne)
-
Summary:
This issue arises from the resolution of
BACM-45andBACM-43. Taken together these proposals create an interpretation of the BACM model elements that does not syntactically distinguish elements representing sets from elements representing individuals. Rather, it represents individuals by an OCL constraint that allows only a single model element to have a given metaclass. This solution works for the only case in the current BACM spec, but does not resolve the underlying issue of the inability to represent individuals and make assertions about them. -
Reported: BACM 1.0a1 — Thu, 8 Dec 2022 21:14 GMT
-
Disposition: Deferred — BACM 1.0b2
-
Disposition Summary:
Resolution requires substantial change to the BACM metamodel
Implementing a domain of individuals and assertions (e.g. OWL 2) would require adding many more classes and associations to the metamodel with consequences unanalyzed at this time.
-
Updated: Mon, 9 Oct 2023 15:16 GMT
BACM — The BACM metamodel does not have a domain of individuals
- Key: BACM-68
- OMG Task Force: Business Architecture Core Metamodel (BACM) 1.0 FTF