Ontologies, metamodels, and vocabularies for architectural knowledge graphs

Core

Foundation ontology and shared infrastructure

OWL Ontology

Core Linked.Archi Ontology

https://meta.linked.archi/core#
Core Linked.Archi Ontology for Enterprise and IT Architecture modeling.
v0.3.2
OWL Ontology

Core Linked.Archi Ontology for Diagrams

https://meta.linked.archi/core-vis#
Base Ontology EA modeling.
v0.1
SHACL Shapes

Linked.Archi Core SHACL Shapes

https://meta.linked.archi/core-shapes#
Base SHACL shapes for the Linked.Archi core ontology. These shapes apply to all metamodels that extend the core. Metamodel-specific shapes (e.g., ArchiMate, C4, Backstage) import this file and add type-specific constraints.
v0.1.0
Viewpoint Definitions

Linked.Archi Core Viewpoints

https://meta.linked.archi/core-viewpoints#
Framework-agnostic architecture viewpoints derived from ISO/IEC/IEEE 42010 and common architecture practice. These are universal viewpoints that any modeling language can use — ArchiMate, TOGAF, C4, Backstage, or custom metamodels can specialize or reference them.
v0.1.0
Deliverable Templates

Linked.Archi Core Deliverable Templates

https://meta.linked.archi/core-deliverable-templates#
Framework-agnostic deliverable templates that define the content structure of common architecture documents. Each template specifies which viewpoints are required — the actual views are created when someone instantiates the template into a concrete deliverable (arch:Model). These templates reference core viewpoints. Framework-specific templates (e.g., TOGAF Architecture Definition Document) should be defined in the respective framework's file, referencing framework-specific viewpoints.
v0.1.0

Extensions

Composable extension modules for any metamodel

OWL Ontology

Linked.Archi Architecture Decision Ontology

https://meta.linked.archi/arch-decision#
Extension ontology for modeling architecture decisions, the issues that trigger them, candidate options, influencing forces (requirements, constraints, trends), and the rationale linking forces to chosen options. Use this extension when you need to capture decision records, trace forces to options, or integrate with ADD-style iterative decision processes.
v0.0.5
OWL Ontology

Linked.Archi Architecture Processes Extension

https://meta.linked.archi/arch-processes#
Extension ontology for modeling architecture governance processes, activities, tasks, and their inputs and outputs within architecture models. This extension enables architects to capture process-oriented aspects of architecture work — governance workflows, lifecycle activities, and the artifacts they consume and produce — as first-class elements in architecture models alongside structural and behavioral elements. Use this extension when you need to: * Model architecture governance processes and their decomposition * Capture process inputs (forces, models, information items) and outputs (decisions, deliverables, models) * Trace how architecture activities relate to decisions and deliverables * Integrate process views into architecture descriptions The classes in this extension are practical model elements (subClassOf arch:Element) that can be used in architecture views and governed by metamodels, just like elements from the decisions or reference architecture extensions. The process concepts are aligned with ISO/IEC/IEEE 42020 (architecture governance), ISO/IEC/IEEE 12207 (software lifecycle), and ISO/IEC/IEEE 15288 (system lifecycle). For the normative standard definitions themselves, see the corresponding standard vocabularies under standards/.
v0.1.0
OWL Ontology

Linked.Archi Reference Architecture Ontology

https://meta.linked.archi/ref-arch#
Extension ontology for modeling reference architectures, reference models, architectural patterns, tactics, and building blocks (ABB/SBB). Use this extension to capture reusable architectural knowledge, classify patterns by type (module, integration, deployment), relate tactics to quality attributes, and trace how patterns and tactics interact.
v0.0.5
OWL Ontology

Linked.Archi Tactics Extension Ontology

https://meta.linked.archi/tactics#
Extension ontology providing a taxonomy of architectural tactics organized by quality attribute (availability, interoperability, modifiability, performance, security). Use this extension to classify concrete design techniques that architects employ to achieve specific quality-attribute responses, and to relate them to patterns and decisions.
v0.1.0
OWL Ontology

Linked.Archi Quality Attributes Extension

https://meta.linked.archi/quality-attributes#
Extension providing named quality-attribute individuals (beyond ISO 25010) for use in architecture decision evaluation, tactic mapping, and quality-attribute scenario modeling. Use this extension to reference resilience-oriented quality attributes such as Safety, Survivability, Longevity, and Adaptability that complement the ISO 25010 taxonomy.
v0.1.0

Modeling Languages

Ontologies for specific architecture modeling notations

ArchiMate 4.0 Metamodel →
OWL Ontology

Linked.Archi ArchiMate 4.0 Ontology

https://meta.linked.archi/archimate4/onto#
Linked.Archi ArchiMate ontology aligned to the ArchiMate 4.0 specification (the "Hexagonion"). ArchiMate 4.0 replaces the layer-based structure of 3.x with a domain-based organization (Common, Business, Application, Technology, Strategy, Motivation, Implementation & Migration). Behavior elements that were previously duplicated per layer (e.g., BusinessProcess, ApplicationProcess, TechnologyProcess) are merged into single cross-domain elements (Process, Function, Event, Service). New Common Domain elements (Role, Collaboration, Path) are introduced as generic, domain-independent concepts. This is not an official Open Group document.
v4.0
Metamodel Manifest

Linked.Archi ArchiMate 4.0 Metamodel Definition

https://meta.linked.archi/archimate4/metamodel#
Metamodel manifest for ArchiMate 4.0. This file ties together all the ArchiMate 4.0 semantic resources — the element/relationship ontology, SKOS taxonomy, viewpoints, and future SHACL shapes — into a single arch:Metamodel instance. This is the entry point for tools that need to discover all resources that make up the ArchiMate 4.0 modeling language definition.
v4.0
SKOS Taxonomy

Linked.Archi ArchiMate 4.0 Taxonomy

https://meta.linked.archi/archimate4/tax#
Pure SKOS taxonomy classifying ArchiMate 4.0 elements by domain and by aspect. ArchiMate 4.0 replaces the layer-based structure of 3.x with a domain-based organization (Common, Business, Application, Technology, Strategy, Motivation, Implementation & Migration). For OWL abstract classes used in SHACL constraint checking, see archimate4-onto.ttl.
v4.0
Viewpoint Definitions

Linked.Archi ArchiMate 4.0 Viewpoints

https://meta.linked.archi/archimate4/viewpoints#
ArchiMate 4.0 viewpoints as arch:Viewpoint individuals. Each viewpoint specifies allowed element types (arch:includesConcept), target stakeholders (arch:targetsStakeholder), and framed concerns (arch:viewpointFramesConcern). ArchiMate 4.0 uses domain-based organization; viewpoints reference the merged cross-domain elements (Process, Function, Event, Service) from the Common Domain. Organizations may define additional custom viewpoints.
v4.0
SHACL Shapes

Linked.Archi ArchiMate 4.0 SHACL Shapes

https://meta.linked.archi/archimate4/shapes#
SHACL shapes for validating ArchiMate 4.0 model data. Generated from the ArchiMate 4.0 relationship validity matrix (Appendix B). Validates qualified relationship instances. Pure SHACL core.
v4.0
SHACL Shapes

Linked.Archi ArchiMate 4.0 Element & Metamodel Shapes

https://meta.linked.archi/archimate4/element-shapes#
SHACL shapes for validating ArchiMate 4.0 element instances and metamodel patterns. Adapted from 3.2 shapes for the domain-based structure of 4.0. Draft — needs validation against the ArchiMate 4.0 relationship validity matrix.
v4.0
SHACL Shapes

Linked.Archi ArchiMate 4.0 Architecture Principle Shapes

https://meta.linked.archi/archimate4/principle-shapes#
SHACL shapes encoding common enterprise architecture principles as executable constraints. Adapted from 3.2 principle shapes for ArchiMate 4.0 domain-based structure.
v4.0
SHACL Shapes

Linked.Archi ArchiMate 4.0 Viewpoint Conformance Shapes

https://meta.linked.archi/archimate4/viewpoint-shapes#
SHACL shapes for validating that architecture Views conform to their declared Viewpoints. Data-driven — reads viewpoint definitions from the loaded graph.
v4.0
SHACL Shapes

Linked.Archi ArchiMate 4.0 Derivation Rules

https://meta.linked.archi/archimate4/derivation#
SHACL Rules (sh:SPARQLRule) implementing ArchiMate 4.0 derivation rules. Derived relationships are annotated with confidence level and provenance. Draft — the full derivation matrix needs validation against the ArchiMate 4.0 spec.
v4.0
Deliverable Templates

archimate4-deliverable-templates.ttl

https://meta.linked.archi/archimate4/deliverable-templates#
SKOS Taxonomy

ArchiMate 4.0 Reference Data

https://meta.linked.archi/archimate4/reference-data#
Controlled vocabularies commonly used in ArchiMate 4.0 models.
SKOS Taxonomy

ArchiMate 4.0 Reference Models

https://meta.linked.archi/archimate4/reference-models#
Catalog of reference architectures and patterns for ArchiMate 4.0 models.
SKOS Taxonomy

ArchiMate 4.0 Presentation Contexts

https://meta.linked.archi/archimate4/presentation-contexts#
Stakeholder-specific presentation themes for ArchiMate 4.0 views.
ArchiMate 3.2 Metamodel →
OWL Ontology

Linked.Archi ArchiMate 3.2 Ontology

https://meta.linked.archi/archimate3/onto#
Linked.Archi ArchiMate ontology aligned to the ArchiMate 3.2 specification, modernized to conform to Linked.Archi core ontology conventions, the qualified relationship pattern, and RDF 1.2. This is not an official Open Group document.
v3.2
Metamodel Manifest

Linked.Archi ArchiMate 3.2 Metamodel Definition

https://meta.linked.archi/archimate3/metamodel#
Metamodel manifest for ArchiMate 3.2. This file ties together all the ArchiMate semantic resources — the element/relationship ontology, SKOS taxonomy, SHACL shapes, derivation rules, viewpoints, deliverable templates, reference data, reference models, and presentation contexts — into a single arch:Metamodel instance. This is the entry point for tools that need to discover all resources that make up the ArchiMate modeling language definition.
v3.2
SKOS Taxonomy

Linked.Archi ArchiMate 3.2 Taxonomy

https://meta.linked.archi/archimate3/tax#
Pure SKOS taxonomy classifying ArchiMate elements by layer and by aspect, and relationship types by category. For OWL abstract classes used in SHACL constraint checking, see archimate3.2-onto.ttl.
v3.2
Viewpoint Definitions

Linked.Archi ArchiMate 3.2 Example Viewpoints

https://meta.linked.archi/archimate3/viewpoints#
ArchiMate 3.2 example viewpoints as arch:Viewpoint individuals. Each viewpoint specifies allowed element types (arch:includesConcept), target stakeholders (arch:targetsStakeholder), and framed concerns (arch:viewpointFramesConcern). Organizations may define additional custom viewpoints.
v3.2
SHACL Shapes

Linked.Archi ArchiMate 3.2 SHACL Shapes

https://meta.linked.archi/archimate3/shapes#
SHACL shapes for validating ArchiMate model data. Generated from the ArchiMate relationship validity matrix (Archi tool, MIT license). Validates both qualified relationship instances and unqualified direct triples. Pure SHACL core — no SPARQL.
v3.2
SHACL Shapes

Linked.Archi ArchiMate 3.2 Element & Metamodel Shapes

https://meta.linked.archi/archimate3/element-shapes#
SHACL shapes for validating ArchiMate element instances and metamodel patterns. Covers structural integrity, assignment/access/serving direction, cross-layer constraints, specialization rules, junction homogeneity, motivation realization direction, strategy realization targets, and deep specialization warnings. Based on ArchiMate 3.2 spec Figures 5, 34, 45, 46, 51, 52, 70, 82, 99, 104-106. For relationship pair validation, see archimate3.2-relationship-shapes.ttl.
v3.2
SHACL Shapes

Linked.Archi Architecture Principle Shapes

https://meta.linked.archi/archimate3/principle-shapes#
SHACL shapes encoding common enterprise architecture principles and best practices as executable constraints. These shapes validate architecture models against governance patterns such as redundancy avoidance, single authoritative source, separation of concerns, stewardship, and technology standardization. Inspired by the ontology-based EA principle validation approach described in: Montecchiari, D.; Hinkelmann, K. (2026) "Ontology-Based Validation of Enterprise Architecture Principles", Applied Sciences, 16(7):3352. These shapes are designed to be loaded alongside the standard ArchiMate element and relationship shapes. They operate on instance data (architecture models) and detect violations of common governance principles. All shapes use sh:severity sh:Warning by default — organizations should promote specific shapes to sh:Violation based on their governance policies. Usage: ./validate.sh --shacl archimate-principles Or load manually alongside other shapes: core-shapes.ttl + archimate3.2-principle-shapes.ttl + your-model-data.ttl
v0.1.0
SHACL Shapes

Linked.Archi ArchiMate 3.2 Viewpoint Conformance Shapes

https://meta.linked.archi/archimate3/viewpoint-shapes#
SHACL shapes for validating that architecture Views conform to their declared Viewpoints. These shapes enforce: 1. Element conformance — elements exposed in a View must be instances of types listed in the viewpoint's arch:includesConcept. 2. View type conformance — a View's rdf:type must match one of the viewpoint's arch:viewType values (Diagram, Catalog, Matrix). 3. Viewpoint declaration — every View must declare which viewpoint it conforms to via arch:viewConformsToViewpoint. These shapes are data-driven: they read the viewpoint definitions from the loaded graph (arch:includesConcept, arch:viewType) rather than hardcoding per-viewpoint rules. This means they work for any viewpoint — ArchiMate example viewpoints, custom viewpoints, or viewpoints from other frameworks — as long as the viewpoint data is loaded. Shapes use sh:severity sh:Warning by default. Organizations may promote specific shapes to sh:Violation based on governance policies. Usage: .scripts/validate.sh --shacl archimate-viewpoints Or load manually: core-shapes.ttl + archimate3.2-viewpoint-shapes.ttl + archimate3.2-viewpoints.ttl + your-model-data.ttl
v3.2
SHACL Shapes

Linked.Archi ArchiMate 3.2 Derivation Rules

https://meta.linked.archi/archimate3/derivation#
SHACL Rules (sh:SPARQLRule) implementing ArchiMate derivation rules DR1-DR8 (valid) and PDR1-PDR12 (potential) from the ArchiMate 3.2 specification Appendix B. Derived relationships are annotated with confidence level and provenance via RDF 1.2 reification.
v3.2
Deliverable Templates

archimate3.2-deliverable-templates.ttl

https://meta.linked.archi/archimate3/deliverable-templates#
SKOS Taxonomy

ArchiMate Reference Data

https://meta.linked.archi/archimate3/reference-data#
Controlled vocabularies commonly used in ArchiMate models for classifying and annotating architecture elements.
SKOS Taxonomy

ArchiMate Reference Models

https://meta.linked.archi/archimate3/reference-models#
Catalog of reference architectures, patterns, and building blocks that can be used as starting points for ArchiMate models.
SKOS Taxonomy

ArchiMate Presentation Contexts

https://meta.linked.archi/archimate3/presentation-contexts#
Stakeholder-specific presentation themes for ArchiMate views. Each context defines the appropriate level of detail, visual notation style, and terminology for a target audience.
BPMN 2.0.2 Metamodel →
OWL Ontology

linkedarchi-bpmn-onto.ttl

https://meta.linked.archi/bpmn/onto#
OWL mapping of the OMG BPMN 2.0.2 semantic model.
v2.0.2
Metamodel Manifest

Linked.Archi BPMN Metamodel Definition

https://meta.linked.archi/bpmn/metamodel#
Metamodel manifest for BPMN 2.0.2. Ties together the BPMN element/relationship ontologies, SHACL shapes, alignment axioms, and diagram interchange modules into a single discoverable resource. Derived from the OMG BPMN 2.0.2 specification XMI.
v0.1.0
Viewpoint Definitions

Linked.Archi BPMN 2.0.2 Viewpoints

https://meta.linked.archi/bpmn/viewpoints#
BPMN 2.0.2 viewpoints corresponding to the four diagram types defined by the OMG specification: Process, Collaboration, Choreography, and Conversation.
v0.1.0
OWL Ontology

linkedarchi-bpmn-infra-onto.ttl

https://meta.linked.archi/bpmn/infra#
OWL mapping of the BPMN 2.0.2 infrastructure package (Definitions, Import).
v2.0.2
OWL Ontology

linkedarchi-bpmndi-onto.ttl

https://meta.linked.archi/bpmn/di#
OWL mapping of the OMG BPMN 2.0.2 Diagram Interchange (BPMNDI) package.
v2.0.2
OWL Ontology

linkedarchi-di-onto.ttl

https://meta.linked.archi/bpmn/di-core#
OWL mapping of the OMG DD Diagram Interchange (DI) abstract classes.
v2.0.2
OWL Ontology

linkedarchi-dc-onto.ttl

https://meta.linked.archi/bpmn/dc#
OWL mapping of the OMG DD Diagram Common (DC) datatypes.
v2.0.2
Deliverable Templates

bpmn-deliverable-templates.ttl

https://meta.linked.archi/bpmn/deliverable-templates#
C4 Model + Structurizr Metamodel →
OWL Ontology

Linked.Archi C4 Model Ontology

https://meta.linked.archi/c4/onto#
An RDF/OWL ontology for the C4 model — the abstract, notation-independent software architecture visualization model created by Simon Brown. Defines the four core abstraction levels (Person, Software System, Container, Component) and their relationships. This ontology covers the C4 model itself, not any specific tooling implementation. For Structurizr-specific concepts (deployment nodes, infrastructure nodes, deployment environments), see the Structurizr extension ontology (structurizr-onto.ttl) which imports this ontology.
v0.3.0
Metamodel Manifest

Linked.Archi C4 Model Metamodel Definition

https://meta.linked.archi/c4/metamodel#
Metamodel manifest for the C4 model. Ties together the C4 element/relationship ontology, SHACL shapes, SKOS taxonomy, viewpoints, deliverable templates, and reference data into a single discoverable resource.
v0.1.0
SKOS Taxonomy

Linked.Archi C4 Model Taxonomy

https://meta.linked.archi/c4/tax#
SKOS taxonomy classifying C4 model elements by abstraction level and relationship types by category.
Viewpoint Definitions

Linked.Archi C4 Model Viewpoints

https://meta.linked.archi/c4/viewpoints#
C4 model viewpoints corresponding to the four abstraction levels defined by Simon Brown. Each level zooms into the previous one, providing progressively more detail. The Deployment diagram is an additional cross-cutting viewpoint.
v0.1.0
SHACL Shapes

Linked.Archi C4 Model SHACL Shapes

https://meta.linked.archi/c4/shapes#
SHACL shapes for validating C4 model data. Covers the abstract C4 model relationships (Using, ContainerContainment, ComponentContainment). For Structurizr deployment shapes, see structurizr-shapes.ttl.
v0.2.0
OWL Ontology

Linked.Archi Structurizr Extension Ontology

https://meta.linked.archi/c4/structurizr#
Structurizr-specific extensions to the C4 model ontology. Adds deployment modeling concepts (deployment nodes, infrastructure nodes, deployment environments, container instances) that are part of the Structurizr tooling but not part of the abstract C4 model. Imports the C4 model ontology (c4-onto.ttl) — all C4 core concepts are available via the c4: namespace.
v0.1.0
SHACL Shapes

Linked.Archi Structurizr SHACL Shapes

https://meta.linked.archi/c4/structurizr-shapes#
SHACL shapes for validating Structurizr deployment model data. Imports c4-shapes for base C4 model validation.
v0.1.0
Deliverable Templates

c4-deliverable-templates.ttl

https://meta.linked.archi/c4/deliverable-templates#
SKOS Taxonomy

C4 Reference Data

https://meta.linked.archi/c4/reference-data#
Controlled vocabularies for C4 model annotations.
SKOS Taxonomy

C4 Presentation Contexts

https://meta.linked.archi/c4/presentation-contexts#
Stakeholder-specific rendering themes for C4 diagrams.
Backstage Catalog Metamodel →
OWL Ontology

Linked.Archi Backstage Metamodel Ontology

https://meta.linked.archi/backstage/onto#
An RDF/OWL ontology for Backstage catalog entities and their relationships, extending the Linked.Archi core ontology.
v0.2.0
Metamodel Manifest

Linked.Archi Backstage Metamodel Definition

https://meta.linked.archi/backstage/metamodel#
Metamodel manifest for the Backstage Software Catalog. Ties together the Backstage element/relationship ontology, SHACL shapes, SKOS taxonomy, viewpoints, deliverable templates, reference data, and presentation contexts into a single discoverable resource.
v0.1.0
SKOS Taxonomy

Linked.Archi Backstage Taxonomy

https://meta.linked.archi/backstage/tax#
SKOS taxonomy classifying Backstage Software Catalog entities by category (software entities, organizational entities) and relationship types.
Viewpoint Definitions

Linked.Archi Backstage Viewpoints

https://meta.linked.archi/backstage/viewpoints#
Backstage Software Catalog viewpoints for visualizing service ownership, system dependencies, API landscapes, and domain organization. Each viewpoint maps to a common Backstage use case.
v0.1.0
SHACL Shapes

Linked.Archi Backstage SHACL Shapes

https://meta.linked.archi/backstage/shapes#
SHACL shapes for validating Backstage catalog data. Imports core-shapes for base QualifiedRelationship validation. Adds Backstage-specific domain/range constraints per relationship type.
v0.1.0
Deliverable Templates

backstage-deliverable-templates.ttl

https://meta.linked.archi/backstage/deliverable-templates#
SKOS Taxonomy

Backstage Reference Data

https://meta.linked.archi/backstage/reference-data#
Controlled vocabularies for Backstage catalog entity annotations.
SKOS Taxonomy

Backstage Presentation Contexts

https://meta.linked.archi/backstage/presentation-contexts#
Stakeholder-specific rendering themes for Backstage catalog views.
SAP LeanIX Metamodel →
OWL Ontology

Linked.Archi LeanIX Meta Model v4 Ontology

https://meta.linked.archi/leanix/onto#
OWL ontology representing the SAP LeanIX Meta Model v4 — the fact sheet types and relationships used by SAP LeanIX for enterprise architecture management. Models 12 default fact sheet types (Objective, Initiative, Business Capability, Organization, Business Context, Application, Interface, Data Object, IT Component, Tech Category, Platform, Provider) plus one optional type (System), organized across Strategy & Transformation, Business, Application & Data, and Technical architecture layers. Relationships follow the Linked.Archi qualified relationship pattern. This is not an official SAP document.
v4.0.0
Metamodel Manifest

Linked.Archi LeanIX Meta Model Metamodel Definition

https://meta.linked.archi/leanix/metamodel#
Metamodel manifest for the SAP LeanIX Meta Model v4. Ties together the LeanIX fact sheet ontology, viewpoints, and taxonomy into a single discoverable resource. Shapes, deliverable templates, reference data, and presentation contexts can be added later.
v0.1.0
SKOS Taxonomy

Linked.Archi LeanIX Taxonomy

https://meta.linked.archi/leanix/tax#
SKOS taxonomy classifying LeanIX Meta Model v4 fact sheet types by architecture layer and relationship types by category.
Viewpoint Definitions

Linked.Archi LeanIX Viewpoints

https://meta.linked.archi/leanix/viewpoints#
Viewpoints for the SAP LeanIX Meta Model v4, covering application portfolio management, technology landscape, interface mapping, capability mapping, and transformation roadmaps.
v0.1.0
Deliverable Templates

leanIX-deliverable-templates.ttl

https://meta.linked.archi/leanix/deliverable-templates#
Business Model Canvas Metamodel →
SKOS Taxonomy

Linked.Archi Business Model Canvas Vocabulary

https://meta.linked.archi/bmc/onto#
SKOS vocabulary representing the nine building blocks of the Business Model Canvas by Alexander Osterwalder.
v0.2.0
Metamodel Manifest

Linked.Archi Business Model Canvas Metamodel Definition

https://meta.linked.archi/bmc/metamodel#
Metamodel manifest for the Business Model Canvas. The BMC is a pure SKOS vocabulary (no OWL elements or relationships) representing the nine building blocks defined by Alexander Osterwalder.
v0.1.0

Frameworks

Enterprise architecture framework integrations

TOGAF
OWL Ontology

Linked.Archi TOGAF Content Metamodel

https://meta.linked.archi/togaf/onto#
Linked.Archi ontology aligned to the TOGAF Content Metamodel as defined in TOGAF 9.2 Chapter 30 and TOGAF 10 Architecture Content Chapter 3. Models the entity types and relationships of the Content Metamodel as OWL classes and properties, conforming to Linked.Archi core ontology conventions. This is not an official Open Group document.
v10.0
Metamodel Manifest

Linked.Archi TOGAF Metamodel Definition

https://meta.linked.archi/togaf/metamodel#
Metamodel manifest for TOGAF. Ties together the Content Metamodel ontology, ADM taxonomy, viewpoints, deliverable templates, and SHACL shapes into a single discoverable resource.
v10.0
SKOS Taxonomy

Linked.Archi TOGAF Taxonomy

https://meta.linked.archi/togaf/tax#
SKOS taxonomy classifying TOGAF Content Metamodel entities by architecture domain and ADM phase.
v10.0
Viewpoint Definitions

TOGAF Architecture Viewpoints (Catalogs, Matrices, Diagrams)

https://meta.linked.archi/togaf/viewpoints#
TOGAF architecture viewpoints organized by ADM phase. Each viewpoint corresponds to a catalog, matrix, or diagram defined in the TOGAF Architecture Content Framework. Consistent across TOGAF 9.2 (Chapter 31) and TOGAF 10 (Architecture Content, Chapter 3).
v10.0
Deliverable Templates

togaf-deliverable-templates.ttl

https://meta.linked.archi/togaf/deliverable-templates#
ADMIT Metamodel →
OWL Ontology

Linked.Archi ADMIT Design Forces Ontology

https://meta.linked.archi/admit/onto#
The ADMIT Design Forces Ontology contains the 20 ADMIT architecture design forces as OWL classes extending ad:Force.
v0.1.0
Metamodel Manifest

Linked.Archi ADMIT Metamodel Definition

https://meta.linked.archi/admit/metamodel#
Metamodel manifest for ADMIT. Ties together the ADMIT ontology and concept taxonomy into a single discoverable resource.
v0.1.0
SKOS Taxonomy

Linked.Archi ADMIT Framework Taxonomy

https://meta.linked.archi/admit/tax#
SKOS taxonomy of ADMIT framework concepts — architecture levels, domains, resource dimensions, design forces classification, and the architecture development lifecycle (ADLC) with its phases and processes.
v0.1.0
Zachman Framework
SKOS Taxonomy

Linked.Archi Zachman Framework Taxonomy

https://meta.linked.archi/zachman#
SKOS taxonomy of the Zachman Framework for Enterprise Architecture. Models the six interrogatives (columns) and six reification transformations (rows) that form the 6x6 classification matrix for enterprise architecture artifacts. The Zachman Framework is not a methodology — it is a schema for organizing architectural artifacts based on the intersection of stakeholder perspective and descriptive focus.
v0.2.0
TIME Framework Metamodel →
OWL Ontology

Linked.Archi TIME Framework Ontology

https://meta.linked.archi/time-framework/onto#
Ontology for representing application portfolio fit assessments and Gartner TIME dispositions (Tolerate, Invest, Migrate, Eliminate), including functional fit, technical fit, and cost fitness dimensions. Provides classes for applications, fit assessments, criteria scoring, evidence tracking, and OWL enumeration types with automatic quadrant classification. This is the OWL layer of the TIME framework. Use together with: * time-shapes.ttl (SHACL) — validates completeness and value constraints * time-tax.ttl (SKOS) — organizes controlled vocabularies for navigation
v0.1.1
Metamodel Manifest

Linked.Archi TIME Framework Metamodel Definition

https://meta.linked.archi/time-framework/metamodel#
Metamodel manifest for the TIME (Tolerate, Invest, Migrate, Eliminate) framework. Ties together the TIME ontology and controlled vocabularies into a single discoverable resource for application portfolio rationalization.
v0.1.0
SKOS Taxonomy

Linked.Archi TIME Framework Taxonomy

https://meta.linked.archi/time-framework/tax#
SKOS concept scheme for the TIME framework controlled vocabularies, classifying TIME dispositions, fit ratings, fit dimensions, assessment statuses, evidence types, and lifecycle states under a single scheme with multiple top concepts. Individuals are defined in the companion ontology (time-onto.ttl) and referenced here via skos:narrower. This is the SKOS layer of the TIME framework. Use together with: * time-onto.ttl (OWL) — defines classes, properties, and enumeration individuals * time-shapes.ttl (SHACL) — validates completeness and value constraints
v0.2.0
SHACL Shapes

Linked.Archi TIME Framework SHACL Shapes

https://meta.linked.archi/time-framework/shapes#
SHACL shapes for validating TIME framework model data. Ensures applications have required metadata, fit assessments are complete, and controlled vocabulary values are valid. This is the SHACL layer of the TIME framework. Use together with: * time-onto.ttl (OWL) — defines classes, properties, and OWL reasoning rules * time-tax.ttl (SKOS) — organizes controlled vocabularies for navigation
v0.1.0
Platform Design
SKOS Taxonomy

Linked.Archi Platform Design Taxonomy

https://meta.linked.archi/platform-design#
SKOS taxonomy for platform design concepts based on the Platform Design Toolkit methodology. Covers stakeholders (consumer, producer, enabler, keystone), assets, capabilities, stories, needs, solutions, touchpoints, value exchange, compensation, and channels.
v0.2.0
EA on a Page Metamodel →
OWL Ontology

Linked.Archi EA on a Page Ontology

https://meta.linked.archi/eaonapage/onto#
Ontology for the Enterprise Architecture on a Page framework by Svyatoslav Kotusev. Models the CSVLOD artifact taxonomy (Considerations, Standards, Visions, Landscapes, Outlines, Designs), the three core EA processes (Strategic Planning, Initiative Delivery, Technology Optimization), process phases and governance activities, EA practice participants, governance bodies and tiers, maturity stages, and the 24 empirically validated EA artifacts. Based on peer-reviewed research across 27+ organizations, this framework describes how EA practices actually work rather than prescribing how they should work.
v0.1.0
Metamodel Manifest

Linked.Archi EA on a Page Metamodel Definition

https://meta.linked.archi/eaonapage/metamodel#
Metamodel manifest for EA on a Page. Ties together the CSVLOD ontology, artifact taxonomy, maturity model, governance classification, viewpoints, deliverable templates, and SHACL validation shapes into a single discoverable resource.
v0.3.0
SKOS Taxonomy

Linked.Archi EA on a Page Taxonomy

https://meta.linked.archi/eaonapage/tax#
SKOS taxonomy of the 24 EA artifacts identified by Kotusev across 27+ organizations, classified by the CSVLOD types and usage frequency. Also includes the EA Maturity Model (Stage Zero through Stage Three) and the EA Governance classification (architecture tiers, governance bodies, governance activities).
v0.1.0
Viewpoint Definitions

Linked.Archi EA on a Page Viewpoints

https://meta.linked.archi/eaonapage/viewpoints#
Viewpoints for the EA on a Page framework. Each viewpoint specifies the artifact types it includes, the stakeholders it targets, and the purpose it serves. Derived from the CSVLOD artifact taxonomy and the three core EA processes described by Kotusev. EA on a Page does not formally define viewpoints, but its artifact types and processes imply a natural set of viewpoints that practitioners use in practice. These viewpoints formalize those implicit conventions.
v0.1.0
Deliverable Templates

Linked.Archi EA on a Page Deliverable Templates

https://meta.linked.archi/eaonapage/deliverable-templates#
Deliverable templates for the EA on a Page framework. Each template defines the structure and required viewpoints for a common EA deliverable. Based on the artifact types and typical structures described by Kotusev. EA on a Page explicitly says templates should be adapted rather than copied. These templates capture the typical structure observed across organizations and should be customized to local context.
v0.1.0
SHACL Shapes

Linked.Archi EA on a Page SHACL Shapes

https://meta.linked.archi/eaonapage/shapes#
SHACL validation shapes for the EA on a Page framework. Validates artifact instances, process-artifact mappings, governance arrangements, and maturity stage consistency. These shapes encode the structural rules implicit in the EA on a Page framework.
v0.1.0
ATAM Metamodel →
OWL Ontology

Linked.Archi ATAM Ontology

https://meta.linked.archi/atam/onto#
Ontology for the Architecture Tradeoff Analysis Method (ATAM) from the Software Engineering Institute (SEI) at Carnegie Mellon University. Models the evaluation-specific concepts that ATAM adds beyond the core decision and quality attribute vocabulary: utility trees, sensitivity points, tradeoff points, risks, non-risks, and risk themes. ATAM is a method for evaluating software architectures relative to quality attribute goals. It exposes architectural risks that potentially inhibit the achievement of business goals by systematically analyzing quality attribute scenarios against architectural approaches. Use together with: * ad:arch-decision — for decisions, forces, options, and QA scenarios * refa:ref-arch — for patterns and tactics (architectural approaches) * iso25010 — for quality attribute definitions
v0.1.0
Metamodel Manifest

Linked.Archi ATAM Metamodel Definition

https://meta.linked.archi/atam/metamodel#
Metamodel manifest for ATAM. Ties together the ATAM evaluation ontology into a single discoverable resource.
v0.1.0

Standards Alignment

Reference vocabularies from ISO/IEC/IEEE standards that the Linked.Archi ontologies align to

Architecture & Systems Engineering
OWL Ontology

Linked.Archi ISO/IEC/IEEE 42010 Architecture Description Concepts

https://meta.linked.archi/iso42010#
SKOS taxonomy of architecture description concepts from ISO/IEC/IEEE 42010:2022. This is the architecture description standard that the Linked.Archi core ontology aligns to. Covers the key concepts of system, architecture, architecture description, stakeholder, concern, architecture viewpoint, architecture view, architecture model, architecture decision, architecture rationale, correspondence, and correspondence rule.
v0.1.0
OWL Ontology

Linked.Archi ISO/IEC/IEEE 42020 Architecture Governance Processes

https://meta.linked.archi/iso42020#
SKOS taxonomy and OWL classes for architecture governance processes from ISO/IEC/IEEE 42020:2019. Covers the processes for governing and managing the architecture of systems and software, including architecture conceptualization, evaluation, elaboration, and transition under an overarching architecture governance framework.
v0.1.0
OWL Ontology

Linked.Archi ISO/IEC/IEEE 12207 Software Lifecycle Processes

https://meta.linked.archi/iso12207#
SKOS taxonomy and OWL classes for software lifecycle processes from ISO/IEC/IEEE 12207:2017. Covers the framework of processes for the software life cycle, including agreement, organizational project-enabling, technical management, and technical processes applicable to software systems.
v0.1.0
OWL Ontology

Linked.Archi ISO/IEC/IEEE 15288 System Lifecycle Processes

https://meta.linked.archi/iso15288#
SKOS taxonomy and OWL classes for system lifecycle processes from ISO/IEC/IEEE 15288:2023. Establishes a common framework of process descriptions for the life cycle of systems created by humans, covering agreement, organizational project-enabling, technical management, and technical processes.
v0.1.0
Quality Models (SQuaRE)
OWL Ontology

Linked.Archi ISO/IEC 25010 Software Product Quality Model

https://meta.linked.archi/iso25010#
Ontology of software product quality characteristics from ISO/IEC 25010:2023. Top-level characteristics (Functional Suitability, Reliability, etc.) are owl:Class categories. Leaf sub-characteristics (Functional Completeness, Time Behaviour, etc.) are owl:NamedIndividual instances of their parent class — vocabulary terms referenced by arch:QualityMeasure and ad:QualityAttributeRequirement.
v0.2.0
OWL Ontology

Linked.Archi ISO/IEC 25011 IT Service Quality Model

https://meta.linked.archi/iso25011#
Ontology of IT service quality characteristics from ISO/IEC 25011. ITServiceQuality is the root owl:Class (subClassOf arch:QualityAttribute). The nine service quality characteristics are owl:NamedIndividual instances of ITServiceQuality — vocabulary terms referenced by arch:QualityMeasure and ad:QualityAttributeRequirement.
v0.2.0
OWL Ontology

Linked.Archi ISO/IEC 25012 Data Quality Model

https://meta.linked.archi/iso25012#
Ontology of data quality characteristics from ISO/IEC 25012. DataQuality is the root owl:Class (subClassOf arch:QualityAttribute). The fifteen data quality characteristics are owl:NamedIndividual instances of DataQuality — vocabulary terms referenced by arch:QualityMeasure and ad:QualityAttributeRequirement. Grouped into inherent, system-dependent, and inherent/system-dependent categories via skos:note.
v0.2.0

Other

Assets not listed in the index configuration

OWL Ontology

Acme Corp EA-as-a-Service — Worked Example

https://model.example.com/acme-ea#
Worked example demonstrating the EA-as-a-Service extension. Models a 4-person EA team operating as an internal consultancy at a mid-size financial services company. Shows service catalog, engagements, outcomes, satisfaction tracking, capability portfolio, and maturity assessment.
OWL Ontology

Simple Example Ontology

https://meta.linked.archi/simple-example#
Simplest possible Linked.Archi metamodel example.
Viewpoint Definitions

Cloud Platform Viewpoints

https://meta.linked.archi/examples/cloudplatform/viewpoints#
SKOS Taxonomy

Cloud Platform Reference Data

https://meta.linked.archi/examples/cloudplatform/reference-data#
SHACL Shapes

Cloud Platform SHACL Shapes

https://meta.linked.archi/examples/cloudplatform/shapes#
Validation rules for the Cloud Platform Architecture metamodel.
SKOS Taxonomy

Cloud Platform Taxonomy

https://meta.linked.archi/examples/cloudplatform/tax#
OWL Ontology

Cloud Platform Architecture Ontology

https://meta.linked.archi/examples/cloudplatform/onto#
Example custom metamodel extending ArchiMate 4.0 with cloud platform concepts — microservices, containers, message brokers, API gateways, and observability components. Demonstrates how to build an organization-specific modeling language on top of the Linked.Archi foundation.
Deliverable Templates

Cloud Platform Deliverable Templates

https://meta.linked.archi/examples/cloudplatform/deliverable-templates#
Metamodel Manifest

Cloud Platform Architecture Metamodel

https://meta.linked.archi/examples/cloudplatform/metamodel#
Metamodel manifest for the Cloud Platform Architecture example.
OWL Ontology

Component and Connector Example Ontology

https://meta.linked.archi/CnC#
Component and Connector Example Ontology based on Linked.Archi Core Ontology.
OWL Ontology

Minimal Metamodel

https://meta.linked.archi/basic
Minimal Metamodel.
OWL Ontology

Fraud Detection ML-Enabled System — Example Model

https://model.example.com/fraud-detection#
Example architecture model for a real-time fraud detection system that demonstrates the ML-Enabled Systems extension. Shows how ML components (models, pipelines, feature stores) integrate with traditional software components (payment service, transaction database, notification service).
OWL Ontology

Linked.Archi ArchiMate 3.0 Ontology

https://meta.linked.archi/archimate3/onto/3.0#
Linked.Archi ArchiMate 3.0 Ontology.
SKOS Taxonomy

archimate3-tax.ttl

https://meta.linked.archi/archimate3-tax#
OWL Ontology

Linked.Archi ArchiMate Ontology

https://meta.linked.archi/archimate3-shapes
Linked.Archi ArchiMate 3.0 Ontology.
SKOS Taxonomy

archimate3.1-tax.ttl

https://meta.linked.archi/archimate3.1-tax#
OWL Ontology

Linked.Archi ArchiMate 3.1 Ontology

https://meta.linked.archi/archimate3/onto/3.1#
Linked.Archi ArchiMate 3.1 Ontology. based on ArchiMate 3.1 specification
SHACL Shapes

linkedarchi-bpmn-shacl.ttl

https://meta.linked.archi/bpmn/onto#shacl
SHACL Shapes

linkedarchi-bpmndi-shacl.ttl

https://meta.linked.archi/bpmn/di#shacl
SHACL Shapes

linkedarchi-di-shacl.ttl

https://meta.linked.archi/bpmn/di-core#shacl
OWL Ontology

linkedarchi-bpmn-suite-shapes.ttl

https://meta.linked.archi/bpmn/suite#shapes
OWL Ontology

linkedarchi-bpmn-suite-imports.ttl

https://meta.linked.archi/bpmn/suite#
SHACL Shapes

linkedarchi-dc-shacl.ttl

https://meta.linked.archi/bpmn/dc#shacl
SHACL Shapes

linkedarchi-bpmn-infra-shacl.ttl

https://meta.linked.archi/bpmn/infra#shacl
OWL Ontology

linkedarchi-bpmn-suite-alignment.ttl

https://meta.linked.archi/bpmn/suite#alignment
OWL Ontology

Linked.Archi LeanIX Meta Model v3 Ontology

https://meta.linked.archi/leanix/v3-onto#
Ontology representation of SAP LeanIX Meta Model v3 fact sheets and relations.
Metamodel Manifest

Linked.Archi DoDAF Metamodel Definition

https://meta.linked.archi/dodaf/metamodel#
Metamodel manifest for DoDAF 2.02. Ties together the DoDAF entity ontology, viewpoint taxonomy, and viewpoint definitions into a single discoverable resource. DoDAF 2.0 shifted from rigid "products" to a data-centric approach with "Fit-for-Purpose" presentation. This metamodel captures the underlying data model that the 8 viewpoints and 52 DoDAF-described Models present.
Viewpoint Definitions

DoDAF 2.02 Architecture Viewpoints (DoDAF-described Models)

https://meta.linked.archi/dodaf/viewpoints#
DoDAF 2.02 viewpoints modeled as arch:Viewpoint individuals. Each viewpoint corresponds to a DoDAF-described Model (AV, CV, DIV, OV, PV, SvcV, StdV, SV). DoDAF 2.0 uses "Fit-for-Purpose" presentation — these viewpoints define the data content, not rigid visual templates.
OWL Ontology

Linked.Archi DoDAF Ontology

https://meta.linked.archi/dodaf/onto#
Linked.Archi ontology aligned to the U.S. Department of Defense Architecture Framework (DoDAF) version 2.02. Models the core entity types used across DoDAF viewpoints as OWL classes extending arch:Element, and the key relationships as owl:ObjectProperty. DoDAF 2.0 shifted focus from static products to architectural data — this ontology captures the underlying data model that the viewpoints present. This is not an official U.S. Department of Defense document.
SKOS Taxonomy

Linked.Archi DoDAF Taxonomy

https://meta.linked.archi/dodaf/tax#
SKOS taxonomy classifying DoDAF 2.02 entities by viewpoint.
Metamodel Manifest

Linked.Archi EA-as-a-Service Metamodel Definition

https://meta.linked.archi/ea-service/metamodel#
Metamodel manifest for the EA-as-a-Service extension. Ties together the EA service ontology, SKOS taxonomy, SHACL shapes, and reference data into a single discoverable resource. Designed to compose with the Architecture Decisions extension (tracing engagements to decisions) and the Financial Architecture extension (cost-aware service delivery).
SHACL Shapes

Linked.Archi EA-as-a-Service SHACL Shapes

https://meta.linked.archi/ea-service/shapes#
SHACL shapes for validating EA-as-a-Service models. Enforces governance rules: every service must declare required capabilities, every engagement must have an assigned architect and status, and every EA service must have a label.
Viewpoint Definitions

Linked.Archi EA-as-a-Service Extension

https://meta.linked.archi/ea-service/onto#
Extension ontology for modeling the EA function as an internal management consultancy. Provides vocabulary for EA service catalogs, service engagements, stakeholder satisfaction, EA capability portfolios, and maturity assessment. Addresses the Gartner 2025 prediction that by 2028, half of EA teams will rebrand themselves to emphasize their strategic role as business partners. Formalizes the shift from "architecture practice" to "architecture services" by making service offerings, engagements, outcomes, and satisfaction into queryable elements in the knowledge graph. Designed to be lightweight and adaptable — organizations customize the service catalog and maturity model to their operating model.
SKOS Taxonomy

Linked.Archi EA-as-a-Service Taxonomy

https://meta.linked.archi/ea-service/tax#
SKOS taxonomy classifying EA-as-a-Service concepts by service type, engagement duration, stakeholder type, and maturity level.
OWL Ontology

Linked.Archi EA-as-a-Service Reference Data

https://meta.linked.archi/ea-service/reference-data#
Reference data for EA-as-a-Service — service types, engagement statuses, and maturity levels.
OWL Ontology

Linked.Archi AI Governance Reference Data

https://meta.linked.archi/ai-governance/reference-data#
Reference data for AI governance — EU AI Act risk levels, OECD AI Principles, human oversight modes, and assessment statuses.
Metamodel Manifest

Linked.Archi AI Ethics & Governance Metamodel Definition

https://meta.linked.archi/ai-governance/metamodel#
Metamodel manifest for the AI Ethics & Governance extension. Ties together the AI governance ontology, SKOS taxonomy, SHACL shapes, and reference data into a single discoverable resource. This is the entry point for tools that need to discover all resources that make up the AI Ethics & Governance modeling vocabulary. Designed to compose with the ML-Enabled Systems extension — the ML extension provides the technical layer (models, pipelines, serving), while this extension provides the governance layer (risk classification, conformity assessment, bias assessment, human oversight).
SHACL Shapes

Linked.Archi AI Governance SHACL Shapes

https://meta.linked.archi/ai-governance/shapes#
SHACL shapes for validating AI governance models. Enforces governance rules: every AI system must have a risk classification, high-risk systems must have conformity assessments and human oversight plans, and all AI systems must have explainability documentation.
Viewpoint Definitions

Linked.Archi AI Ethics & Governance Extension

https://meta.linked.archi/ai-governance/onto#
Extension ontology for AI ethics and governance. Provides element types, properties, and reference data for managing AI system risk classification, conformity assessment, bias assessment, explainability documentation, human oversight plans, and governance policies. Builds on the ML-Enabled Systems extension (mlsys:) by adding the governance layer that connects ML components to regulatory frameworks (EU AI Act), ethical principles (OECD AI Principles), and organizational AI governance policies. Motivated by Gartner 2025 Leadership Vision identifying AI ethics and governance as a critical gap in EA teams, and by the EU AI Act (Regulation 2024/1689) requiring formal risk classification and conformity assessment for high-risk AI systems.
SKOS Taxonomy

Linked.Archi AI Governance Taxonomy

https://meta.linked.archi/ai-governance/tax#
SKOS taxonomy classifying AI governance concepts by risk level, principle, lifecycle phase, and assessment type.
SHACL Shapes

Linked.Archi Financial Architecture SHACL Shapes

https://meta.linked.archi/financial-architecture/shapes#
SHACL shapes for validating financial architecture models. Enforces governance rules: every cost model must have a currency and at least one cost item, every investment case must have a type and projected ROI, and every cost-benefit analysis must have cost, benefit, and NPV.
SKOS Taxonomy

Linked.Archi Financial Architecture Taxonomy

https://meta.linked.archi/financial-architecture/tax#
SKOS taxonomy classifying financial architecture concepts by cost type, investment type, and analysis type.
OWL Ontology

Linked.Archi Financial Architecture Reference Data

https://meta.linked.archi/financial-architecture/reference-data#
Reference data for financial architecture — cost categories, investment types, and cost periods.
Metamodel Manifest

Linked.Archi Financial Architecture Metamodel Definition

https://meta.linked.archi/financial-architecture/metamodel#
Metamodel manifest for the Financial Architecture extension. Ties together the financial architecture ontology, SKOS taxonomy, SHACL shapes, and reference data into a single discoverable resource. This is the entry point for tools that need to discover all resources that make up the Financial Architecture modeling vocabulary. Designed to compose with the TIME framework for cost-aware portfolio rationalization, and with the Architecture Decisions extension for cost-informed decision making.
Viewpoint Definitions

Linked.Archi Financial Architecture Extension

https://meta.linked.archi/financial-architecture/onto#
Extension ontology for financial aspects of enterprise architecture. Provides vocabulary for Total Cost of Ownership (TCO) models, cost allocation to business capabilities and value streams, investment case tracking (Run/Grow/Transform), cost-benefit analysis for architecture decision options, and FinOps cloud cost management. Not intended to replace financial planning tools — the goal is to make cost a queryable dimension of the architecture knowledge graph, enabling questions like "What is the annual run cost of all applications supporting this capability?" or "Which decision option has the best NPV?" Motivated by Gartner 2025 Leadership Vision identifying lack of financial acumen as one of the five mistakes EA teams make.
SHACL Shapes

Linked.Archi ML-Enabled Systems SHACL Shapes

https://meta.linked.archi/ml-systems/shapes#
SHACL shapes for validating ML-enabled system architecture models. Enforces governance rules: every ML model must have versioning, monitoring, and dataset lineage; every serving infrastructure must have latency SLAs.
OWL Ontology

Linked.Archi ML-Specific Quality Attributes

https://meta.linked.archi/ml-systems/quality-attributes#
Quality attribute individuals specific to ML-enabled systems. Extends the base quality-attributes extension with ML-specific concerns identified by Moin et al. (2023) and Lewis et al. (2021).
Metamodel Manifest

Linked.Archi ML-Enabled Systems Metamodel Definition

https://meta.linked.archi/ml-systems/metamodel#
Metamodel manifest for the ML-Enabled Systems extension. Ties together the ML element/relationship ontology, SKOS taxonomy, and SHACL shapes into a single discoverable resource. This is the entry point for tools that need to discover all resources that make up the ML-Enabled Systems modeling vocabulary.
SKOS Taxonomy

Linked.Archi ML-Enabled Systems Taxonomy

https://meta.linked.archi/ml-systems/tax#
SKOS taxonomy classifying ML-enabled system concepts by lifecycle phase and component role.
Viewpoint Definitions

Linked.Archi ML-Enabled Systems Extension

https://meta.linked.archi/ml-systems/onto#
Extension ontology for modeling ML-enabled system architectures. Provides element types, relationship types, stakeholders, concerns, and viewpoints for describing the ML aspects of software systems — training pipelines, model serving, feature engineering, data lineage, and the integration boundary between ML and non-ML components. Motivated by the gap identified in Moin et al. (2023): existing architecture frameworks lack stakeholders, viewpoints, and model kinds for data scientists, data engineers, and ML engineers. This extension addresses that gap within the Linked.Archi ecosystem.
SKOS Taxonomy

common-tax.ttl

https://meta.linked.archi/core-tax#