Linked.Archi UML 2.5.1 Metamodel Definition
Metamodel manifest for UML 2.5.1. Ties together the UML element/relationship ontology, SHACL shapes, alignment axioms, SKOS taxonomy, viewpoints, and reference data into a single discoverable resource. This metamodel formalizes the OMG Unified Modeling Language as a Linked.Archi modeling language, enabling UML model data to participate in the unified architecture knowledge graph alongside ArchiMate, C4, BPMN, and Backstage. The mapping from the MOF-based UML metamodel to OWL/RDF is informed by the OMG Ontology Definition Metamodel (ODM, formal/2014-09-02) Annex D mapping rules, with Linked.Archi conventions (three-declaration qualified relationships, SHACL validation, SKOS classification) applied on top. ODM maps UML model instances (M1) to OWL for dataset use; this metamodel represents the UML metamodel itself (M2) in OWL for architecture knowledge graph use.
Linked.Archi
UML 2.5.1
The Unified Modeling Language (UML) 2.5.1 — the OMG standard general-purpose modeling language for software-intensive systems. Provides 14 diagram types covering structural and behavioral modeling. Standardized as ISO/IEC 19505-1:2012 (Infrastructure) and ISO/IEC 19505-2:2012 (Superstructure). UML is defined using the Meta Object Facility (MOF) as its meta-metamodel (M3 layer). The OMG Ontology Definition Metamodel (ODM) defines MOF metamodels for OWL/RDF and provides UML profiles for ontology authoring in UML tools. Its Annex D mapping rules are used as an informative reference for how UML constructs surface in OWL.
MOF 2.5.1
The Meta Object Facility (MOF) 2.5.1 — the OMG meta-metamodel that defines the abstract syntax used to specify UML and other modeling languages. MOF is the M3 layer in the four-layer metamodel architecture.
ODM 1.1
The Ontology Definition Metamodel (ODM) 1.1 — the OMG specification that defines MOF metamodels for RDF, OWL, Common Logic, and Topic Maps, along with mappings to and from UML and profiles for UML-based ontology authoring tools. ODM is relevant for building data models and vocabularies for datasets using UML tools. Its Annex D mapping rules (informative, not normative) remain a useful reference for how UML constructs should surface in OWL — even though Linked.Archi uses OWL directly rather than authoring through UML profiles. Key ODM Annex D mapping rules used as reference in this metamodel: - UML Package → owl:Ontology (Annex D.3.2) - UML Class → owl:Class (Annex D.3.3) - UML Generalization → rdfs:subClassOf (Annex D.3.3) - UML Property → owl:DatatypeProperty or owl:ObjectProperty (Annex D.3.4) - UML Association → owl:ObjectProperty (Annex D.3.5) - UML AssociationClass → owl:Class + functional properties (Annex D.3.6) - UML Multiplicity → owl:minCardinality/maxCardinality (Annex D.3.7) - UML Enumeration → SKOS ConceptScheme (Linked.Archi convention; ODM D.3.9 uses owl:oneOf)
UML 2.5.1 Metamodel
The complete UML 2.5.1 metamodel definition for Linked.Archi, aggregating the element/relationship ontology, SHACL shapes, alignment axioms, SKOS taxonomy, viewpoints, and reference data. Covers structural classifiers (Class, Interface, Component, Package), behavioral elements (Activity, StateMachine, Interaction), deployment concepts (Node, Artifact), and use cases (Actor, UseCase). This metamodel enables UML model data to coexist with ArchiMate, C4, BPMN, and Backstage models in the same knowledge graph, queryable with the same SPARQL, validatable with the same SHACL, and navigable through the same tools.