BACM semantic specification unclear
-
Key: BACM-31
-
Status: open
-
Source: Thematix Partners LLC ( James Rhyne)
-
Summary:
7.2.1 states the following “UML visual modeling is used in this specification as a visual notation for an underlying graphical predicate model. The underlying model can be given a concrete form in RDF* (https://arxiv.org/pdf/1406.3399.pdf) or a property graph language (e.g. Cypher openCypher_V9). Most of the semantics of the metamodel (except for shortcuts and co-occurrence constraints) can be specified in OWL 2.” Which is not really true since those forms are not actually provided and what is specified is a MOF metamodel, which has different semantics than UML. Though the ODM specification does provide an interpretation and a profile for use of UML for RDF, this has not been referenced in this specification.
-
Reported: BACM 1.0a1 — Thu, 20 Oct 2022 16:20 GMT
-
Updated: Tue, 27 Jun 2023 16:00 GMT