Linked.Archi

DCAT Catalog

W3C DCAT Catalog

Linked.Archi — Semantic Assets

Ontologies, metamodels, and vocabularies for architectural knowledge graphs

244 datasets Last updated: 2026-11-16 ⬇ catalog.ttl ⬇ catalog.jsonld

This page is the dereferenceable resource for https://meta.linked.archi/catalog. It lists all semantic assets published in this catalog as W3C DCAT datasets. Machine-readable versions are available as Turtle and JSON-LD, and embedded in this page's <head>.

Dataset Type Version Modified Distributions
4+1 View Model Taxonomy
https://meta.linked.archi/4plus1
Classification scheme based on Philippe Kruchten's 4+1 View Model (IEEE Software, 1995). Organizes architecture descriptions into four concurrent views (Logical, Process, Development, Physical) plus a unifying Scenarios view that validates and illustrates the others.
SKOS Concept Scheme v0.1.0 2026-05-06 text/turtle
4+1 View Model Deliverable Templates
https://meta.linked.archi/4plus1/deliverable-templates
Deliverable templates for the 4+1 Architectural View Model. Defines a Software Architecture Document (SAD) structured around the five views, following the template pattern from Kruchten's original paper and the RUP SAD template.
Deliverable Templates v0.1.0 2026-05-06 text/turtle
4+1 View Model Metamodel Manifest
https://meta.linked.archi/4plus1/metamodel
Metamodel manifest for the 4+1 Architectural View Model. Aggregates the taxonomy, viewpoints, and deliverable templates into a single entry point. The 4+1 model is a viewpoint framework — it does not define its own element types. Custom metamodels reference it for viewpoint structure and document templates.
Metamodel Manifest v0.1.0 2026-05-06 text/turtle
4+1 View Model Viewpoints
https://meta.linked.archi/4plus1/viewpoints
Viewpoint definitions for the 4+1 Architectural View Model. These are language-agnostic viewpoints — they specify concerns and stakeholders but do not prescribe which modeling language to use. A custom metamodel attaches concrete element types via arch:includesConcept.
Viewpoint Definitions v0.1.0 2026-05-06 text/turtle
Component and Connector Example Ontology
https://meta.linked.archi/CnC
Component and Connector Example Ontology based on Linked.Archi Core Ontology.
OWL Ontology v0.0.1 2021-05-18 application/ld+json application/n-triples application/rdf+xml text/turtle
Component and Connector Example Ontology (Variant)
https://meta.linked.archi/CnC-variant
Component and Connector Example Ontology based on Linked.Archi Core Ontology.
OWL Ontology v0.0.1 2021-05-05 application/ld+json application/n-triples application/rdf+xml text/turtle
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.
Metamodel Manifest v0.1.0 2026-05-02 text/turtle
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. This is not an official IASA document.
OWL Ontology v0.1.0 2026-05-02 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi ADMIT Framework Taxonomy
https://meta.linked.archi/admit/tax
Classification of architecture concepts from the ADMIT framework.
SKOS Concept Scheme v0.1.0 2026-05-02 text/turtle
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).
Metamodel Manifest v0.1.0 2026-05-03 text/turtle
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. Trademarked names referenced herein are property of their respective owners.
OWL Ontology v0.1.0 2026-05-03 application/ld+json application/n-triples application/rdf+xml text/turtle
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.
OWL Ontology v0.1.0 2026-05-03 application/ld+json application/n-triples application/rdf+xml text/turtle
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.
SHACL Shapes v0.1.0 2026-05-03 text/turtle
Linked.Archi AI Governance Taxonomy
https://meta.linked.archi/ai-governance/tax
Classification of AI governance concepts by risk level, principle, lifecycle phase, and assessment type.
SKOS Concept Scheme v0.1.0 2026-05-03 text/turtle
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), the rationale linking forces to chosen options, and the lifecycle state of the decision record itself. Use this extension when you need to capture decision records, trace forces to options, separate open deliberations from settled decisions, or integrate with ADD-style iterative decision processes.
OWL Ontology v0.0.8 2026-11-16 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi Architecture Decision SHACL Shapes
https://meta.linked.archi/arch-decision-shapes
SHACL shapes for validating architecture decision records built with the Linked.Archi architecture decision extension. Closes the decision state vocabulary, enforces the structural contract between a Decision and its Issue, Options and Forces, and checks the Quality Attribute Scenario structure on quality attribute requirements. These shapes complement core-shapes: the core file already requires a label on every arch:Element and a source and target on every arch:QualifiedRelationship, so those constraints are not repeated here except where a tighter rule applies.
SHACL Shapes v0.2.0 2026-08-20 text/turtle
Linked.Archi Architecture Decisions Metamodel Definition
https://meta.linked.archi/arch-decision/metamodel
Metamodel manifest for the Architecture Decisions extension. Ties together the decision ontology, the relationship types that draw its links, the SKOS taxonomy and the SHACL shapes into a single discoverable resource. Designed to be added beside a modelling language: a decision record links to the elements of the architecture it decides about.
Metamodel Manifest v0.1.0 2026-11-16 text/turtle
Linked.Archi Architecture Decision Taxonomy
https://meta.linked.archi/arch-decision/tax
Classification of the Architecture Decision element types — the decision record and the forces on it — and of the relationship types that draw its links.
SKOS Concept Scheme 2026-11-16 text/turtle
Linked.Archi Architecture Processes Extension
https://meta.linked.archi/arch-processes
Extension ontology describing architecture governance processes, activities, tasks, and their inputs and outputs. Architecture processes are not constituents of the system being architected — they are the governance and lifecycle infrastructure that acts upon it from the outside. An architecture review board process governs a system; it is not part of the system's architecture. They are elements of a model all the same — of a model of the architecture practice: a process, its activities, tasks, deliverables and milestones are element types (arch:Element), so that a modelling tool can place them in a view beside the architecture they govern. Process concepts relate to the elements of that architecture via linking properties (ap:governs, ap:input, ap:output, ap:consumedBy), never by being one of its components. Use this extension when you need to: * Describe 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 * Link architecture elements to the processes that govern them 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/.
OWL Ontology v0.3.0 2026-11-16 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi Architecture Processes SHACL Shapes
https://meta.linked.archi/arch-processes-shapes
SHACL shapes for the lifecycle concepts in the Architecture Processes extension. Supplies the constraint DD-23 requires but which the ontology deliberately does not assert: at most one lifecycle stage per subject, drawn from a stage vocabulary. The universally-applicable rules are auto-targeting. The rule that closes the value set to the canonical five stages is NOT auto-targeting, because several asset sets legitimately define their own stages — the ISO 12207 stage model, the TIME framework lifecycle states, and any organisation with its own progression. Closing the vocabulary globally would report all of those as violations. Opt in where you want it, per DD-23: the value set is a governance constraint on your data, not a logical truth.
SHACL Shapes v0.1.0 2026-08-10 text/turtle
Linked.Archi Architecture Processes Metamodel Definition
https://meta.linked.archi/arch-processes/metamodel
Metamodel manifest for the Architecture Processes extension. Ties together the process ontology, the relationship types that draw its links, the SKOS taxonomy and the SHACL shapes into a single discoverable resource. Designed to be added beside a modelling language: a governance process is modelled next to the architecture it governs.
Metamodel Manifest v0.1.0 2026-11-16 text/turtle
Linked.Archi Architecture Processes Taxonomy
https://meta.linked.archi/arch-processes/tax
Classification of the Architecture Processes element types — the structure of a process, its deliverables and its roles — and of the relationship types that draw its links.
SKOS Concept Scheme v0.1.0 2026-11-16 text/turtle
ArchiMate — Version-Neutral Framework Identity
https://meta.linked.archi/archimate/framework
The single arch:Framework individual for ArchiMate the language, as distinct from ArchiMate 3.2 and ArchiMate 4.0 the releases. It exists because there was no way to ask a version-independent question. Each version's manifest declared its own :ArchiMateFramework in its own namespace — archimate3/metamodel#ArchiMateFramework and archimate4/metamodel#ArchiMateFramework — with a version in its label, so "ArchiMate, the language" had two IRIs that nothing related, and the natural query returned nothing: SELECT ?model WHERE { ?model arch:modelConformsToMetamodel/arch:basedOnFramework ?fw . FILTER(?fw = amfw:ArchiMateFramework) } Consumers had to enumerate the metamodels instead — VALUES ?mm { ammm:ArchiMate3.2 am4mm:ArchiMate4 } — an explicit list that grows with every release. This file lives at modelingLanguages/archimate/, above the 3.2/ and 4.0/ version directories, and its namespace carries no version, because that is what it is for. Nothing release-specific belongs here: version detail stays on the arch:Metamodel instances, which is where it was already correct. A model still conforms to ArchiMate 3.2, not to ArchiMate in general.
OWL Ontology v0.1.0 2026-08-13 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi ArchiMate 3.2 Deliverable Templates
https://meta.linked.archi/archimate3/deliverable-templates
Deliverable template definitions for generating architecture documents from ArchiMate 3.2 models: each section answers the concerns it names by asking model questions of the model.
Deliverable Templates text/turtle
Linked.Archi ArchiMate 3.2 Derivation Rules
https://meta.linked.archi/archimate3/derivation
SHACL rules (sh:SPARQLRule) implementing the ArchiMate 3.2 derivation rules of Appendix B: DR1–DR8, whose derived relationships are valid in any model, and PDR1–PDR12, whose derived relationships may hold. Each rule is the join its definition states; the restrictions of B.4 and the order of strength are written into each rule. A valid rule derives a statement: the direct triple, the qualified predicate and the resource, a relationship like any other. A potential rule derives a proposition: the resource alone, which reifies the triple (rdf:reifies) without asserting it, for the modeller to confirm by asserting the triple, with its qualified predicate. Either way the resource carries its certainty (:Valid or :Potential), the relationships it was derived from (prov:wasDerivedFrom) — the qualified relationships the rule matched, the modeller's or derived — and the activity that generated it (prov:wasGeneratedBy): the derivation activity, the rule applied to them, whose plan is the rule (prov:qualifiedAssociation, prov:hadPlan). Each rule is a prov:Plan. What runs the rules — an application, a pipeline — records its run: an activity of its own, with its agent and when it ran, of which each derivation activity it produced is part (dcterms:isPartOf). What the modeller stated is told from what a rule derived by the graph, in a store (a derivation is kept in .../graph/derived), and by the resource. Before the rules run, :QualifyRelationships gives each relationship the model states only as a direct triple a resource of its own. The IRIs are in the model's namespace, a derivation's and its derivation activity's from its rule and premises; with no model loaded, or several, in urn:linked-archi:. The rules are SPARQL 1.2. A rule derives only from relationships whose triple is asserted, in the model or by a valid derivation — one that is only :Potential is for the modeller to confirm, as is any other proposition — so the rules give the closure of valid derivations and one layer of potential ones; a valid derivation of a relationship that so far is only :Potential makes it :Valid. A potential rule derives only what the relationship tables of Appendix B.5 permit between the two element types, as archimate3.2-relationship-tables.ttl gives them: load it with the model. Generated from Appendix B (inline style).
SHACL Shapes v3.2 2026-10-16 text/turtle
Linked.Archi ArchiMate 3.2 Element & Metamodel Shapes
https://meta.linked.archi/archimate3/element-shapes
SHACL shapes for validating ArchiMate 3.2 element instances and the metamodel patterns the relationship tables cannot express: element names, self-loops and cycles of composition and aggregation, a part in one whole only, the direction of serving between layers (a warning), a gap associated with plateaus, attribute values, junctions joining relationships of one type, and deep specialization chains. Which element types a relationship may connect is checked by archimate3.2-relationship-shapes.ttl, generated from the specification's relationship tables (Appendix B), and is not repeated here.
SHACL Shapes v3.2 2026-11-06 text/turtle
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.
Metamodel Manifest v3.2 2025-12-01 text/turtle
Linked.Archi ArchiMate 3.2 Visual Notation Set
https://meta.linked.archi/archimate3/notation
Visual notation descriptors for ArchiMate 3.2 elements and relationships. Defines the standard visual appearance (shape, color, icon, line style) for each model concept, enabling palette generation and diagram rendering from structured metadata.
Visual Notation v3.2 2026-11-07 text/turtle
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. Each relationship class has as its skos:notation the letter the relationship tables of Appendix B write it with (c composition, r realization, v serving …). This is not an official Open Group document.
OWL Ontology v3.2 2026-10-10 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi ArchiMate 3.0 Ontology
https://meta.linked.archi/archimate3/onto/3.0
OWL ontology defining ArchiMate 3.0 element types and relationships for Linked.Archi.
OWL Ontology v3.0 2019-11-17 application/ld+json application/n-triples application/rdf+xml text/turtle
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
OWL Ontology v3.1 2020-07-27 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi ArchiMate 3.2 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. Contexts link to NotationSets via arch:usesNotationSet to drive context-aware palette generation.
SKOS Concept Scheme v3.2 text/turtle
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
SHACL Shapes v0.1.0 2026-11-06 text/turtle
Linked.Archi ArchiMate 3.2 Questions
https://meta.linked.archi/archimate3/questions
Questions ArchiMate 3.2 stakeholders ask of a model — impact of change, application dependencies, data access, responsibilities, realisation and traceability — and the findings that show where a concern the ArchiMate 3.2 viewpoints frame is not met. Each is executable SPARQL (see arch:ModelQuestion).
Question Set v0.1.0 2026-10-27 text/turtle
Linked.Archi ArchiMate 3.2 Reference Data
https://meta.linked.archi/archimate3/reference-data
Controlled vocabularies and reference data for ArchiMate 3.2 models, used for classifying and annotating architecture elements.
SKOS Concept Scheme v3.2 text/turtle
Linked.Archi ArchiMate 3.2 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 Concept Scheme v3.2 text/turtle
Linked.Archi ArchiMate 3.2 Relationship Tables
https://meta.linked.archi/archimate3/relationship-tables
The relationship tables of ArchiMate 3.2 (Appendix B.5) as lookups: for each element type, the types each relationship may go to — directly, or as the result of a derivation — as annotations on the element type (am:Artifact :permitsRealization am:BusinessObject), and for each relationship the annotation that holds its permissions (am:realizes :permittedBy :permitsRealization). A relationship permitted to every element type lists arch:Element, and to every element and relationship arch:ModelConcept. Each permission also says whether it is direct: :permitsDirectRealization, a subproperty of :permitsRealization (am:realizes :permittedDirectlyBy :permitsDirectRealization), lists the types the tables print in upper case — a relationship a modeller may draw. A type :permits… but not :permitsDirect… is one the specification sanctions only as the conclusion of a derivation. The relationships to and from relationships, which Table 21 lists without case, are direct, as association is in the tables, and a grouping's aggregation and composition. The same tables as the relationship shapes (archimate3.2-relationship-shapes.ttl), generated from the same matrix, in a form for another use. The shapes validate: SHACL Core, which any SHACL engine runs and which reports a relationship the tables forbid. These answer a lookup — may this relationship go from this type to that one, and may a modeller draw it? — with one triple pattern. A tool may use either: the shapes to validate, and to read the table back out of their sh:or lists; these to look a relationship up, and to tell one a modeller may draw from one only a derivation gives. The derivation rules (archimate3.2-derivation-rules.ttl) use these: a SHACL rule queries the data graph, where the shapes are not, and reading the shapes' lists in SPARQL is slow. A potential rule derives only what these permit from the one element type to the other, so load this file with the model to run them: without it, the potential rules derive nothing. Each relationship the specification's metamodel figures draw is given too: :drawsRealization, a subproperty of :permitsRealization (am:realizes :drawnBy :drawsRealization), lists the types the figures draw a realization to from this type — expanded from the abstract types a figure names to the concrete pairs beneath them that the tables permit directly. They say what the specification illustrates, which a modelling tool may show; the order in which it proposes relationships is the taxonomy's. Each such triple's reifier cites, with dcterms:source, every figure that draws it. The generic figures hold within a layer: across layers the tables give their triggering, flow, access and assignment only as derived (a business process accessing a data object), and the figures of Chapter 12 draw what holds between layers. They leave the implementation and migration elements out too, which 3.2 classifies as internal behaviour, event and passive structure elements: their own figures draw their relationships. A pair a figure names itself is given as the figure draws it: figure 113 draws a work package realizing and influencing a requirement, which the tables give only as derived. This is not an official Open Group document.
OWL Ontology v3.2 2026-10-16 text/turtle
Linked.Archi ArchiMate 3.2 SHACL Shapes
https://meta.linked.archi/archimate3/shapes
SHACL shapes for validating ArchiMate 3.2 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.
SHACL Shapes v3.2.0 2026-10-11 text/turtle
Linked.Archi ArchiMate 3.2 Taxonomy
https://meta.linked.archi/archimate3/tax
Classification of ArchiMate elements by layer and aspect, and relationship types by category, with the order of the layers, of the aspects and of the relationship categories, the grouping of a palette and the order of the groups a diagram keeps in bands.
SKOS Concept Scheme v3.2 2025-12-01 text/turtle
Linked.Archi ArchiMate 3.0 Taxonomy
https://meta.linked.archi/archimate3/tax/3.0
SKOS taxonomy classifying ArchiMate 3.0 elements by layer and aspect, and relationship types by category.
SKOS Concept Scheme v3.0 2019-03-17 text/turtle
Linked.Archi ArchiMate 3.1 Taxonomy
https://meta.linked.archi/archimate3/tax/3.1
SKOS taxonomy classifying ArchiMate 3.1 elements by layer and aspect, and relationship types by category. Adds ValueStream to the Strategy layer (introduced in 3.1).
SKOS Concept Scheme v3.1 2020-07-27 text/turtle
Linked.Archi ArchiMate 3.2 Viewpoint Conformance Shapes
https://meta.linked.archi/archimate3/viewpoint-shapes
Viewpoint conformance for ArchiMate 3.2 models. The rules are in the core shapes, which this document imports, and it adds none of its own: 1. Viewpoint declaration — every View declares exactly one viewpoint, as an arch:Viewpoint individual rather than a literal. 2. View type conformance — a View's rdf:type must match one of the viewpoint's arch:viewType values (Diagram, Catalog, Matrix). 3. Element conformance — elements presented in a View, linked by arch:inView, must be instances of types the viewpoint's arch:includesConcept allows. 4. Relationship endpoint conformance — the endpoints of a relationship drawn on a View should themselves be in the viewpoint's palette. 5. Viewpoint completeness — a viewpoint should declare what it admits, the concerns it frames and which kinds of view realise it. They read the viewpoint definitions from the loaded graph rather than naming any viewpoint, and use no ArchiMate term, so core states them once for every language: ArchiMate example viewpoints, custom viewpoints and other frameworks' alike. A rule that only ArchiMate 3.2 viewpoints need would go here. Usage: load the core shapes with the 3.2 viewpoint catalogue and the model. core-onto.ttl and the 3.2 ontology go in the shapes graph and the data: the shapes target arch:View and arch:Viewpoint, and their SPARQL walks rdfs:subClassOf* in the data.
OWL Ontology v3.2 2026-11-06 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi ArchiMate 3.2 Example Viewpoints
https://meta.linked.archi/archimate3/viewpoints
The ArchiMate 3.2 example viewpoints of Appendix C as arch:Viewpoint individuals. Each states the elements it admits (arch:includesConcept — Grouping and the two junctions in every one, as the specification allows), its stakeholders (arch:targetsStakeholder), the concerns it frames (arch:viewpointFramesConcern) and its purposes (arch:viewpointHasPurpose). The catalogue groups them twice, as SKOS: by the specification's categories and by the scope its tables state (how many layers and aspects a viewpoint spans). The specification calls them examples, not a normative or exhaustive list; organizations may define their own.
Viewpoint Definitions v3.2 2026-10-17 text/turtle
Linked.Archi ArchiMate 4.0 Deliverable Templates
https://meta.linked.archi/archimate4/deliverable-templates
Deliverable template definitions for generating architecture documents from ArchiMate 4.0 models: each section answers the concerns it names by asking model questions of the model.
Deliverable Templates text/turtle
Linked.Archi ArchiMate 4.0 Derivation Rules
https://meta.linked.archi/archimate4/derivation
SHACL rules (sh:SPARQLRule) implementing the ArchiMate 4.0 derivation rules of Appendix B: DR1–DR8, whose derived relationships are valid in any model, and PDR1–PDR12, whose derived relationships may hold. Each rule is the join its definition states; the restrictions of B.4 and the order of strength are written into each rule. A valid rule derives a statement: the direct triple, the qualified predicate and the resource, a relationship like any other. A potential rule derives a proposition: the resource alone, which reifies the triple (rdf:reifies) without asserting it, for the modeller to confirm by asserting the triple, with its qualified predicate. Either way the resource carries its certainty (:Valid or :Potential), the relationships it was derived from (prov:wasDerivedFrom) — the qualified relationships the rule matched, the modeller's or derived — and the activity that generated it (prov:wasGeneratedBy): the derivation activity, the rule applied to them, whose plan is the rule (prov:qualifiedAssociation, prov:hadPlan). Each rule is a prov:Plan. What runs the rules — an application, a pipeline — records its run: an activity of its own, with its agent and when it ran, of which each derivation activity it produced is part (dcterms:isPartOf). What the modeller stated is told from what a rule derived by the graph, in a store (a derivation is kept in .../graph/derived), and by the resource. Before the rules run, :QualifyRelationships gives each relationship the model states only as a direct triple a resource of its own. The IRIs are in the model's namespace, a derivation's and its derivation activity's from its rule and premises; with no model loaded, or several, in urn:linked-archi:. The rules are SPARQL 1.2. A rule derives only from relationships whose triple is asserted, in the model or by a valid derivation — one that is only :Potential is for the modeller to confirm, as is any other proposition — so the rules give the closure of valid derivations and one layer of potential ones; a valid derivation of a relationship that so far is only :Potential makes it :Valid. A potential rule derives only what the relationship tables of Appendix B.5 permit between the two element types, as archimate4-relationship-tables.ttl gives them: load it with the model. Generated from Appendix B (inline style).
SHACL Shapes v4.0 2026-10-14 text/turtle
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 the metamodel patterns the relationship tables cannot express: element names, self-loops and cycles of composition and aggregation, a part in one whole only, attribute values, junctions joining relationships of one type, and deep specialization chains. Which element types a relationship may connect is checked by archimate4-relationship-shapes.ttl, generated from the specification's relationship tables (Appendix B), and is not repeated here.
SHACL Shapes v4.0 2026-11-06 text/turtle
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.
Metamodel Manifest v4.0 2026-04-29 text/turtle
Linked.Archi ArchiMate 4.0 Visual Notation Set
https://meta.linked.archi/archimate4/notation
Visual notation descriptors for ArchiMate 4.0 elements and relationships. Defines the standard visual appearance (shape, color, icon, line style) for each model concept, enabling palette generation and diagram rendering from structured metadata.
Visual Notation v4.0 2026-11-07 text/turtle
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. Each relationship class has as its skos:notation the letter the relationship tables of the specification write it with (g aggregation, r realization, v serving …); composition, which the 4.0 tables write as g too, keeps the c of the 3.2 tables. This is not an official Open Group document.
OWL Ontology v4.0 2026-10-10 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi ArchiMate 4.0 Presentation Contexts
https://meta.linked.archi/archimate4/presentation-contexts
Stakeholder-specific presentation themes for ArchiMate 4.0 views.
SKOS Concept Scheme v4.0 text/turtle
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.
SHACL Shapes v4.0 2026-11-06 text/turtle
Linked.Archi ArchiMate 4.0 Questions
https://meta.linked.archi/archimate4/questions
Questions ArchiMate 4.0 stakeholders ask of a model — impact of change, application dependencies, data access, responsibilities, realisation and traceability — and the findings that show where a concern the ArchiMate 4.0 viewpoints frame is not met. Each is executable SPARQL (see arch:ModelQuestion).
Question Set v0.1.0 2026-10-27 text/turtle
Linked.Archi ArchiMate 4.0 Reference Data
https://meta.linked.archi/archimate4/reference-data
Controlled vocabularies and reference data for ArchiMate 4.0 architecture models.
SKOS Concept Scheme v4.0 text/turtle
Linked.Archi ArchiMate 4.0 Reference Models
https://meta.linked.archi/archimate4/reference-models
Catalog of reference architectures and patterns for ArchiMate 4.0 models.
SKOS Concept Scheme v4.0 text/turtle
Linked.Archi ArchiMate 4.0 Relationship Tables
https://meta.linked.archi/archimate4/relationship-tables
The relationship tables of ArchiMate 4.0 (Appendix B.5) as lookups: for each element type, the types each relationship may go to — directly, or as the result of a derivation — as annotations on the element type (am4:Artifact :permitsRealization am4:BusinessObject), and for each relationship the annotation that holds its permissions (am4:realizes :permittedBy :permitsRealization). A relationship permitted to every element type lists arch:Element, and to every element and relationship arch:ModelConcept: association, which the tables permit between any two. Each permission also says whether it is direct: :permitsDirectRealization, a subproperty of :permitsRealization (am4:realizes :permittedDirectlyBy :permitsDirectRealization), lists the types the tables print in upper case — a relationship a modeller may draw. A type :permits… but not :permitsDirect… is one the specification sanctions only as the conclusion of a derivation. The relationships between relationships of Table B-1 are direct. The same tables as the relationship shapes (archimate4-relationship-shapes.ttl), generated from the same matrix, in a form for another use. The shapes validate: SHACL Core, which any SHACL engine runs and which reports a relationship the tables forbid. These answer a lookup — may this relationship go from this type to that one, and may a modeller draw it? — with one triple pattern. A tool may use either: the shapes to validate, and to read the table back out of their sh:or lists; these to look a relationship up, and to tell one a modeller may draw from one only a derivation gives. The derivation rules (archimate4-derivation-rules.ttl) use these: a SHACL rule queries the data graph, where the shapes are not, and reading the shapes' lists in SPARQL is slow. A potential rule derives only what these permit from the one element type to the other, so load this file with the model to run them: without it, the potential rules derive nothing. Each relationship the specification's metamodel figures draw is given too: :drawsRealization, a subproperty of :permitsRealization (am4:realizes :drawnBy :drawsRealization), lists the types the figures draw a realization to from this type — expanded from the abstract types a figure names to the concrete pairs beneath them that the tables permit directly. They say what the specification illustrates, which a modelling tool may show; the order in which it proposes relationships is the taxonomy's. Each such triple's reifier cites, with dcterms:source, every figure that draws it. A pair a figure names itself is given as the figure draws it: figures 8-1, 9-1 and 11-1 draw an interface serving a business actor, an application component and a facility, which the tables give only as derived. This is not an official Open Group document.
OWL Ontology v4.0 2026-10-15 text/turtle
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), including the relationships between relationships of Table B-1. Validates qualified relationship instances and unqualified direct triples. Pure SHACL core.
SHACL Shapes v4.0 2026-10-11 text/turtle
Linked.Archi ArchiMate 4.0 Taxonomy
https://meta.linked.archi/archimate4/tax
Classification of ArchiMate 4.0 elements by domain and by aspect, of its relationships by category, and of its junctions, with the order of the domains, of the aspects and of the relationship categories, the order of strength the derivation rules apply, the order in which a modelling tool proposes them, the grouping of a palette and the order of the domains a diagram keeps in bands.
SKOS Concept Scheme v4.0 2026-04-29 text/turtle
Linked.Archi ArchiMate 4.0 Viewpoint Conformance Shapes
https://meta.linked.archi/archimate4/viewpoint-shapes
Viewpoint conformance for ArchiMate 4.0 models. The rules are in the core shapes, which this document imports, and it adds none of its own: 1. Viewpoint declaration — every View declares exactly one viewpoint, as an arch:Viewpoint individual rather than a literal. 2. View type conformance — a View's rdf:type must match one of the viewpoint's arch:viewType values (Diagram, Catalog, Matrix). 3. Element conformance — elements presented in a View, linked by arch:inView, must be instances of types the viewpoint's arch:includesConcept allows. 4. Relationship endpoint conformance — the endpoints of a relationship drawn on a View should themselves be in the viewpoint's palette. 5. Viewpoint completeness — a viewpoint should declare what it admits, the concerns it frames and which kinds of view realise it. They read the viewpoint definitions from the loaded graph rather than naming any viewpoint, and use no ArchiMate term, so core states them once for every language: the published 4.0 catalogue, custom viewpoints and other frameworks' alike. A rule that only ArchiMate 4.0 viewpoints need would go here. Usage: load the core shapes with the 4.0 viewpoint catalogue and the model. core-onto.ttl and the 4.0 ontology go in the shapes graph and the data: the shapes target arch:View and arch:Viewpoint, and their SPARQL walks rdfs:subClassOf* in the data.
OWL Ontology v4.0 2026-11-06 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi ArchiMate 4.0 Viewpoints
https://meta.linked.archi/archimate4/viewpoints
The ArchiMate 4.0 example viewpoints of Appendix C as arch:Viewpoint individuals. Each states the elements it admits (arch:includesConcept — Grouping and the two junctions in every one, as the specification allows), its stakeholders (arch:targetsStakeholder), the concerns it frames (arch:viewpointFramesConcern) and its purposes (arch:viewpointHasPurpose). The catalogue groups them twice, as SKOS: by the specification's categories and by the scope its tables state (how many domains and aspects a viewpoint spans). The specification calls them examples, not a normative or exhaustive list; organizations may define their own.
Viewpoint Definitions v4.0 2026-10-11 text/turtle
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.
Metamodel Manifest v0.1.0 2026-05-03 text/turtle
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 This is not an official SEI/Carnegie Mellon document.
OWL Ontology v0.2.0 2026-11-16 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi ATAM SHACL Shapes
https://meta.linked.archi/atam/shapes
SHACL shapes for validating ATAM (Architecture Tradeoff Analysis Method) evaluation records — utility trees, risks, non-risks, sensitivity points and tradeoff points.
SHACL Shapes v0.1.0 2026-08-04 text/turtle
Linked.Archi ATAM Taxonomy
https://meta.linked.archi/atam/tax
Classification of the ATAM element types — the evaluation, the utility tree it builds and the findings it produces — and of the relationship types that draw its links.
SKOS Concept Scheme v0.1.0 2026-11-16 text/turtle
Linked.Archi Backstage Cross-Language Mappings
https://meta.linked.archi/backstage/crossmappings
Cross-language SKOS mappings between Backstage Software Catalog kinds and relations and ArchiMate modeling language concepts, for both ArchiMate 3.2 and ArchiMate 4.0. These mappings are editorial. Backstage documents its catalog model without reference to ArchiMate, and the ArchiMate specification does not mention developer portals. The assertions here express semantic proximity based on the kind definitions in the Backstage catalog model and the concept definitions in the ArchiMate specifications. The catalog describes software as it is owned and operated: what is deployed, who owns it, which APIs it exposes, what infrastructure it needs. ArchiMate describes the same estate at an architectural grain. The closest fit is at the application layer — a Backstage System and an ArchiMate application component are both the unit that architects and owners reason about — so that pair is skos:closeMatch. Elsewhere the kinds are deliberately broad (a Resource can be a database, a bucket, a server or a cluster; a Domain is any grouping) and the mappings are skos:relatedMatch, fanning out to each ArchiMate concept a modeller might choose. These are type-level statements. They do not say that any particular catalog entity corresponds to any particular ArchiMate element; instance-level correspondence is asserted in the catalog itself, through the Linked.Archi catalog index (skos:exactMatch and friends against a shared id namespace). Not mapped, deliberately: bs:Template and bs:Scaffolding (they describe how entities are created, not the architecture), bs:TechDocsDelegation (documentation ownership), and the enumerations for lifecycle, component type and API type, which are reference data rather than concepts.
OWL Ontology v0.1.0 2026-09-25 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi Backstage Deliverable Templates
https://meta.linked.archi/backstage/deliverable-templates
Catalogue of deliverable templates for generating architecture documents from Backstage catalog models — a service catalog, a system architecture document, and an organization structure document. Declares no classes or properties; the vocabulary these individuals instantiate (arch:DeliverableTemplate, arch:TemplateSection) is defined in the core ontology.
Deliverable Templates v0.1.0 text/turtle
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. Note on reference data: since the value vocabularies moved into the ontology as named individuals, backstage-reference-data carries correspondences to other vocabularies rather than values of its own. It stays in the manifest under arch:referenceData because that is still what it is — reference data for the metamodel — but a consumer looking for the lifecycle or type value sets should follow arch:modelConcepts, not this property.
Metamodel Manifest v0.2.0 2026-08-24 text/turtle
Linked.Archi Backstage Visual Notation Set
https://meta.linked.archi/backstage/notation
Visual notation descriptors for Backstage Software Catalog entity types.
Visual Notation v0.2.0 2026-10-10 text/turtle
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. This is not an official Spotify document.
OWL Ontology v0.5.0 2026-08-24 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi Backstage Presentation Contexts
https://meta.linked.archi/backstage/presentation-contexts
Stakeholder-specific presentation contexts for Backstage catalog views.
SKOS Concept Scheme v0.1.0 text/turtle
Linked.Archi Backstage Reference Data
https://meta.linked.archi/backstage/reference-data
Controlled vocabularies and reference data for Backstage catalog models.
SKOS Concept Scheme v0.1.0 text/turtle
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, the Backstage naming rule, and the value-set constraints for the lifecycle, API visibility and status level vocabularies. The value-set shapes are load-bearing rather than belt-and-braces: the ontology declares those vocabularies as DD-23 named individuals with no owl:oneOf, so nothing constrains membership if these shapes are not run.
SHACL Shapes v0.2.0 2026-08-24 text/turtle
Linked.Archi Backstage Taxonomy
https://meta.linked.archi/backstage/tax
Classification of Backstage Software Catalog entities and relationships.
SKOS Concept Scheme v0.2.0 2026-08-24 text/turtle
Linked.Archi Backstage Viewpoints
https://meta.linked.archi/backstage/viewpoints
Backstage Software Catalog viewpoints for visualizing service ownership, system dependencies, API landscapes, domain organization, organizational structure, and lifecycle portfolio. Each viewpoint maps to a common Backstage use case.
Viewpoint Definitions v0.1.0 2026-04-16 text/turtle
Linked.Archi Basic Ontology
https://meta.linked.archi/basic
Concept ontology of the Linked.Archi Basic asset set: three element types (Node, SpecialNode, GroupNode) and three qualified relationship types (Association, Aggregation, Connection), built directly on the core ontology. It is deliberately small, yet enough for examples of meaningful restrictions and inference rules. Connection is the generic relationship: it relates any two elements, of any language, so Basic added beside another language lets a modeller relate what that language has no relationship for. The manifest https://meta.linked.archi/basic/metamodel#Basic ties it to its taxonomy, its presentation contexts and its two notation sets. Version 0.1.0 is the initial release of these element and relationship patterns.
OWL Ontology v0.1.0 2026-10-05 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi Basic Metamodel Definition
https://meta.linked.archi/basic/metamodel
Metamodel manifest for Basic, a minimal Linked.Archi modelling language. This file ties together the Basic semantic resources (the element and relationship ontology, the SKOS taxonomy, the presentation contexts and the default notation set) into a single arch:Metamodel instance. This is the entry point for tools that need to discover all resources that make up the Basic language definition.
Metamodel Manifest v0.1.0 2026-10-06 text/turtle
Linked.Archi Basic Visual Notation Set (rectangle)
https://meta.linked.archi/basic/notation
Default visual notation set of the Linked.Archi Basic asset set, named by the manifest https://meta.linked.archi/basic/metamodel#Basic with arch:notationSet. It has generic descriptors for the two core palette classes, arch:Element and arch:QualifiedRelationship, so a renderer has something to draw for any element or relationship class without a language-specific notation, and descriptors for Basic's own relationship classes, basic:Association and basic:Aggregation. Elements are very light grey-green rectangles with a centred label and no icon. Relationships carry no colour: renderers draw them black, and they differ by line style and end decorations only. The circle-based alternative, https://meta.linked.archi/basic/notation-bubble#, is selected by the Workshop participant context in https://meta.linked.archi/basic/presentation-contexts# and differs only in element geometry.
Visual Notation v0.1.0 2026-10-06 text/turtle
Linked.Archi Basic Visual Notation Set (bubble)
https://meta.linked.archi/basic/notation-bubble
Alternative, circle-based (bubble) visual notation set of the Linked.Archi Basic asset set. The manifest https://meta.linked.archi/basic/metamodel#Basic does not name it: the Workshop participant context in https://meta.linked.archi/basic/presentation-contexts# selects it with arch:usesNotationSet. It has generic descriptors for the two core palette classes, arch:Element and arch:QualifiedRelationship, so a renderer has something to draw for any element or relationship class without a language-specific notation, and descriptors for Basic's own relationship classes, basic:Association and basic:Aggregation. Elements are very light grey-green circles with a centred label and no icon. Relationships carry no colour: renderers draw them black, and they differ by line style and end decorations only. The default, rectangle-based set is published at https://meta.linked.archi/basic/notation# and differs only in element geometry.
Visual Notation v0.1.0 2026-10-06 text/turtle
Linked.Archi Basic Presentation Contexts
https://meta.linked.archi/basic/presentation-contexts
Audiences for Basic diagrams. Each context is an audience, as the core ontology defines a presentation context, and picks one of Basic's two notation sets with arch:usesNotationSet: the Modeller context the rectangle set, the Workshop participant context the bubble set. The Basic manifest, https://meta.linked.archi/basic/metamodel#Basic, names only the rectangle set with arch:notationSet, which keeps it the default; the bubble set is reached through this scheme alone.
SKOS Concept Scheme v0.1.0 2026-10-05 text/turtle
Linked.Archi Basic Taxonomy
https://meta.linked.archi/basic/tax
Classification of the Basic language's concepts. One axis, Basic Concepts, groups them into element types (Node, SpecialNode, GroupNode) and relationship types (Association, Aggregation, Connection). It names every class in https://meta.linked.archi/basic and nothing else, so palette generators can list Basic's types next to another language's.
SKOS Concept Scheme v0.1.0 2026-10-05 text/turtle
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.
Metamodel Manifest v0.1.0 2026-04-16 text/turtle
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.
SKOS Concept Scheme v0.2.0 2026-04-12 text/turtle
Linked.Archi BPMN Lite Metamodel Definition
https://meta.linked.archi/bpmn-lite/metamodel
Metamodel manifest for BPMN Lite — a simplified BPMN profile for enterprise architecture reasoning. Covers the EA-relevant subset of BPMN 2.0.2: processes, tasks, events, gateways, participants, data objects, and message flows. Choose BPMN Lite when: • The goal is cross-model reasoning (BPMN ↔ ArchiMate ↔ C4), not BPMN execution. • You want a "thin lift" — only constructs with EA-level semantic value. • Layout and notation detail stays in the original .bpmn file, referenced by URI. Choose the full BPMN 2.0.2 suite (modelingLanguages/bpmn/) when: • You need full spec fidelity (144 classes, diagram interchange, correlation). • You are building BPMN tooling, round-tripping, or execution engines. • You need SHACL validation against the complete BPMN metamodel.
Metamodel Manifest v0.1.0 2026-05-06 text/turtle
Linked.Archi BPMN Lite Visual Notation Set
https://meta.linked.archi/bpmn-lite/notation
Visual notation descriptors for BPMN Lite elements and relationships, following the BPMN 2.0.2 standard visual appearance.
Visual Notation v0.1.0 2026-10-10 text/turtle
Linked.Archi BPMN Lite Ontology
https://meta.linked.archi/bpmn-lite/onto
A simplified BPMN ontology for enterprise architecture use cases. Covers only the BPMN constructs that carry semantic value at the EA level — processes, tasks, events, gateways, participants, data objects, and message flows. Omits execution-level detail (diagram interchange geometry, waypoints, marker styles, I/O specifications, correlation, loop characteristics) that adds triple density without supporting cross-model reasoning. Use this ontology when the goal is to query, validate, or reason across BPMN and other models (ArchiMate, C4, TOGAF). For full BPMN 2.0.2 fidelity — including diagram interchange and all 144 metamodel classes — use the complete BPMN suite (modelingLanguages/bpmn/). Design rationale: BPMN is execution-oriented and much denser than ArchiMate. A faithful 1:1 lift of every BPMN-XML element creates many triples whose semantic value at EA level is near zero. The value of RDF over native XML materializes only when you intend to query, validate, or reason across BPMN and other models.
OWL Ontology v0.1.0 2026-05-06 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi BPMN Lite SHACL Shapes
https://meta.linked.archi/bpmn-lite/shapes
SHACL validation shapes for the BPMN Lite ontology.
SHACL Shapes v0.1.0 2026-08-04 text/turtle
Linked.Archi BPMN Lite Taxonomy
https://meta.linked.archi/bpmn-lite/tax
Classification of BPMN Lite elements by BPMN category — flow objects, connecting objects, swim lanes, and data.
SKOS Concept Scheme text/turtle
Linked.Archi BPMN Cross-Language Mappings
https://meta.linked.archi/bpmn/crossmappings
Cross-language SKOS mappings between BPMN 2.0.2 concepts and ArchiMate modeling language concepts, for both ArchiMate 3.2 and ArchiMate 4.0. These mappings are editorial. No official document maps BPMN to ArchiMate: the ArchiMate specification notes that BPMN can be used to detail business processes but defines no element-level correspondence, and the OMG BPMN specification does not mention ArchiMate. The assertions here express semantic proximity based on the concept definitions in the two specifications. The dominant predicate is deliberately skos:relatedMatch rather than skos:closeMatch, because the two notations model behaviour at different granularities and for different purposes. BPMN describes executable control flow — order, gateways, message exchange, exception paths. ArchiMate describes architectural behaviour and its relationship to structure, and its finest behavioural grain is coarser than a BPMN task. A mapping that claimed these coincide would overstate what a cross-notation query can conclude. BPMN Lite reaches these mappings through its own concept-level assertions: each bpmnl: class carries skos:exactMatch to its bpmn: counterpart, so a query that follows both hops resolves a BPMN Lite type onto the ArchiMate correspondences below. Not mapped, deliberately: bpmn:EventBasedGateway and bpmn:ComplexGateway (no ArchiMate construct expresses event-driven or condition-driven routing); bpmn:Gateway itself (abstract, with the routing semantics carried by its subclasses); and the BPMN serialization and extension machinery, which describes documents rather than architecture.
OWL Ontology v0.1.0 2026-09-05 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi DC Ontology (OMG DD/DC)
https://meta.linked.archi/bpmn/dc
OWL mapping of the OMG DD Diagram Common (DC) datatypes.
OWL Ontology v2.0.2 2026-07-25 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi DC SHACL Shapes (OMG DD/DC)
https://meta.linked.archi/bpmn/dc-shapes
SHACL shapes validating OMG Diagram Common (DC) value types — Bounds, Point, and Font.
SHACL Shapes v2.0.2 2026-07-25 text/turtle
Linked.Archi BPMN Deliverable Templates
https://meta.linked.archi/bpmn/deliverable-templates
Deliverable template definitions for generating process documentation from BPMN models.
Deliverable Templates text/turtle
Linked.Archi BPMN DI 2.0.2 Ontology
https://meta.linked.archi/bpmn/di
OWL mapping of the OMG BPMN 2.0.2 Diagram Interchange (BPMNDI) package.
OWL Ontology v2.0.2 2026-05-06 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi DI Ontology (OMG DD/DI)
https://meta.linked.archi/bpmn/di-core
OWL mapping of the OMG DD Diagram Interchange (DI) abstract classes.
OWL Ontology v2.0.2 2026-05-06 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi DI SHACL Shapes (OMG DD/DI)
https://meta.linked.archi/bpmn/di-core-shapes
SHACL shapes validating OMG Diagram Interchange (DI) abstract classes — Diagram, DiagramElement, Shape, Edge, Label, and Style.
SHACL Shapes v2.0.2 2026-07-25 text/turtle
Linked.Archi BPMNDI SHACL Shapes
https://meta.linked.archi/bpmn/di-shapes
SHACL shapes validating BPMN 2.0.2 Diagram Interchange classes — BPMNDiagram, BPMNPlane, BPMNShape, BPMNEdge, and BPMNLabel.
SHACL Shapes v2.0.2 2026-07-25 text/turtle
Linked.Archi BPMN Infrastructure Ontology
https://meta.linked.archi/bpmn/infra
OWL mapping of the BPMN 2.0.2 infrastructure package (Definitions, Import).
OWL Ontology v2.0.2 2026-05-06 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi BPMN Infrastructure SHACL Shapes
https://meta.linked.archi/bpmn/infra-shapes
SHACL shapes validating BPMN 2.0.2 infrastructure classes — Definitions container and Import elements.
SHACL Shapes v2.0.2 2026-07-25 text/turtle
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.
Metamodel Manifest v0.1.0 2026-09-05 text/turtle
Linked.Archi BPMN 2.0.2 Visual Notation Set
https://meta.linked.archi/bpmn/notation
Visual notation descriptors for BPMN 2.0.2 elements and relationships, following the standard BPMN visual appearance defined by the OMG specification.
Visual Notation v0.1.0 2026-10-10 text/turtle
Linked.Archi BPMN 2.0.2 Ontology
https://meta.linked.archi/bpmn/onto
OWL mapping of the OMG BPMN 2.0.2 semantic model. This is not an official OMG document.
OWL Ontology v2.0.2 2026-05-06 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi BPMN SHACL Shapes
https://meta.linked.archi/bpmn/onto-shapes
SHACL shapes validating BPMN 2.0.2 core semantic classes — activities, events, gateways, flows, data objects, and their structural constraints. Derived from the OMG BPMN 2.0.2 specification.
SHACL Shapes v2.0.2 2026-08-04 text/turtle
Linked.Archi BPMN Suite Imports (draft)
https://meta.linked.archi/bpmn/suite
Import aggregator that pulls together all five BPMN ontology packages (Core, Infrastructure, BPMNDI, DI, DC) into a single importable unit.
OWL Ontology v2.0.2 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi BPMN Suite Shapes Imports (draft)
https://meta.linked.archi/bpmn/suite-shapes
Shape aggregator that pulls together all SHACL shape modules for the BPMN suite (Core, Infrastructure, BPMNDI, DI, DC) into a single importable unit.
OWL Ontology v2.0.2 2026-07-25 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi BPMN 2.0.2 Taxonomy
https://meta.linked.archi/bpmn/tax
Classification of BPMN 2.0.2 metaclasses by BPMN category — flow objects, connecting objects, swim lanes, artifacts, and collaborations.
SKOS Concept Scheme text/turtle
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.
Viewpoint Definitions v0.1.0 2026-04-16 text/turtle
Linked.Archi C4 Deliverable Templates
https://meta.linked.archi/c4/deliverable-templates
Deliverable template definitions for generating architecture documents from C4 models.
Deliverable Templates text/turtle
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.
Metamodel Manifest v0.1.0 2026-04-16 text/turtle
Linked.Archi C4 Model Visual Notation Set
https://meta.linked.archi/c4/notation
Visual notation descriptors for C4 model elements and relationships. Defines the standard C4 visual appearance — colored boxes with technology labels, person shapes, and dashed dependency arrows. Follows the conventions from c4model.com and Structurizr rendering defaults.
Visual Notation v0.1.0 2026-10-11 text/turtle
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. This is not an official c4model.com document.
OWL Ontology v0.3.0 2026-10-10 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi C4 Presentation Contexts
https://meta.linked.archi/c4/presentation-contexts
Stakeholder-specific rendering themes for C4 diagrams. Each context links to a NotationSet via arch:usesNotationSet to drive context-aware palette generation and diagram rendering.
SKOS Concept Scheme v0.1.0 text/turtle
Linked.Archi C4 Reference Data
https://meta.linked.archi/c4/reference-data
Controlled vocabularies and reference data for annotating C4 architecture model elements.
SKOS Concept Scheme v0.1.0 text/turtle
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.
SHACL Shapes v0.2.0 2026-10-10 text/turtle
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.
OWL Ontology v0.1.0 2026-10-10 application/ld+json application/n-triples application/rdf+xml text/turtle
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.
SHACL Shapes v0.1.0 2026-10-10 text/turtle
Linked.Archi C4 Model Taxonomy
https://meta.linked.archi/c4/tax
Classification of C4 model elements by abstraction level.
SKOS Concept Scheme text/turtle
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.
Viewpoint Definitions v0.1.0 2026-10-10 text/turtle
Linked.Archi Cloud Services Extension
https://meta.linked.archi/cloud-services/onto
Classifies the elements of any model that stand for concrete cloud products and services — a managed database, an object store, a container platform — by a classification common to the cloud providers, so that products of Microsoft Azure, Amazon Web Services, Google Cloud and others can be compared and queried together. Two properties tag an element with a concept of the cloud services taxonomy: its service category (compute, storage, databases…) and its service model (IaaS, PaaS, SaaS). Trademarked names referenced herein are property of their respective owners.
OWL Ontology v0.1.0 2026-11-14 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi Cloud Services Taxonomy
https://meta.linked.archi/cloud-services/tax
Classification of concrete cloud products and services, common to the cloud providers: the service categories — compute, storage, databases and so on — and the service models, infrastructure, platform and software as a service. Each category carries, as alternative labels, the names Microsoft Azure, Amazon Web Services and Google Cloud give it in their product catalogues, so that a product of any of them finds its category under the name it is known by. An element of a model takes them by the cloud services extension's properties, cs:serviceCategory and cs:serviceModel. Trademarked names referenced herein are property of their respective owners.
SKOS Concept Scheme v0.1.0 2026-11-14 text/turtle
Core Linked.Archi Ontology
https://meta.linked.archi/core
Core Linked.Archi Ontology for Enterprise and IT Architecture modeling. Trademarked names (UML, BPMN, ArchiMate, TOGAF, etc.) referenced herein are property of their respective owners.
OWL Ontology v0.6.0 2026-11-16 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi Core Deliverable Templates
https://meta.linked.archi/core-deliverable-templates
Framework-agnostic deliverable templates of common architecture documents, produced from a model in any language: each section answers the concerns it names by asking the core model questions. Also the presentation formats every deliverable template renders in. Language- and framework-specific templates (e.g., the ArchiMate Architecture Definition Document) are defined with their language or framework.
Deliverable Templates text/turtle
Linked.Archi Core Questions
https://meta.linked.archi/core-questions
The questions any Linked.Archi model answers, whatever its modelling language: what it contains, what an element is related to, which views show what, and how sound the description is. Each is executable SPARQL bound to the concerns it informs (see arch:ModelQuestion).
Question Set v0.1.0 2026-10-27 text/turtle
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. Label requirements are deliberately not here. arch:Element means "a node in a model", and several notations have nodes that are legitimately unnamed — BPMN gateways and events, ArchiMate junctions — so each metamodel states its own naming rule in its own shapes. See the labelling contract in this file and DD-24. Viewpoint conformance is here too: a View declares one viewpoint, its type and contents match what that viewpoint admits, and a viewpoint says what it admits. The rules read the viewpoint definitions from the loaded graph (arch:includesConcept, arch:viewType), so they work for any viewpoint — a language's catalogue, a framework's, or your own.
SHACL Shapes v0.4.0 2026-11-08 text/turtle
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.
Viewpoint Definitions v0.1.0 2026-04-15 text/turtle
Core Linked.Archi Ontology for Diagrams and Visual Notation
https://meta.linked.archi/core-vis
Core Linked.Archi Ontology for Diagrams and Visual Notation. Provides vocabulary for diagram interchange (nodes, links, bounds) and visual styling (colors, fonts, shapes, icons). Used both at the instance level (diagram elements) and at the type level (default notation for model concepts via NotationSet).
OWL Ontology v0.8 2026-11-09 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi Core Visual Notation SHACL Shapes
https://meta.linked.archi/core-vis-shapes
SHACL shapes for the Linked.Archi diagram and visual notation layer (core-vis). Constrains the diagram interchange classes — ArchNode, LabelNode, ContainerNode, Link, Point, PointList — and the type-level notation classes NotationSet, VisualNotation and Style. Until 0.1.0 the diagram layer had no shapes at all: a validate run loaded the notation's own shapes and the core shapes, none of which target a core-vis class, so nothing checked that a diagram node referenced a model element, that it belonged to a view, or that an edge had endpoints. A corpus of 447 malformed diagram resources across 20 diagrams validated clean. The two load-bearing rules here are ArchNodeShape (a diagram node that claims to stand for a model element must say which one) and PlacedDiagElementShape (a shape or edge must belong to exactly one view); the remainder is cardinality and datatype hygiene.
SHACL Shapes v0.4.0 2026-11-09 text/turtle
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.
Metamodel Manifest v2.02 2026-05-03 text/turtle
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.
OWL Ontology v2.02 2026-05-03 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi DoDAF SHACL Shapes
https://meta.linked.archi/dodaf/shapes
SHACL shapes for validating DoDAF 2.02 model data. This is not an official U.S. Department of Defense document.
SHACL Shapes v0.1.0 2026-08-04 text/turtle
Linked.Archi DoDAF Taxonomy
https://meta.linked.archi/dodaf/tax
Classification of DoDAF 2.02 entities by viewpoint.
SKOS Concept Scheme v2.02 2026-05-03 text/turtle
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.
Viewpoint Definitions v2.02 2026-05-03 text/turtle
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).
Metamodel Manifest v0.1.0 2026-05-03 text/turtle
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. Trademarked names referenced herein are property of their respective owners.
OWL Ontology v0.1.0 2026-05-03 application/ld+json application/n-triples application/rdf+xml text/turtle
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 v0.1.0 2026-05-03 application/ld+json application/n-triples application/rdf+xml text/turtle
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.
SHACL Shapes v0.1.0 2026-05-03 text/turtle
Linked.Archi EA-as-a-Service Taxonomy
https://meta.linked.archi/ea-service/tax
Classification of EA service concepts by service type, engagement duration, stakeholder type, and maturity level.
SKOS Concept Scheme v0.1.0 2026-05-03 text/turtle
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.
Deliverable Templates v0.1.0 2026-05-03 text/turtle
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, classification dimension facets (nature, focus, scope, lifecycle, frequency), maturity model, governance classification, viewpoints, deliverable templates, and SHACL validation shapes into a single discoverable resource.
Metamodel Manifest v0.3.0 2026-06-15 text/turtle
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. Defines the six CSVLOD artifact types as OWL classes (Consideration, Standard, Vision, Landscape, Outline, Design) with inter-type relationship properties describing how artifact types influence each other within an EA practice. Also defines EA processes (Strategic Planning, Initiative Delivery, Technology Optimization), process phases, governance activities, participants, governance bodies and tiers, and maturity stages. Finer-grained classification of the 24 specific artifact types is handled via eaop:classifiedByType pointing to SKOS concepts in the companion taxonomy (eaonapage-tax.ttl). Based on peer-reviewed research across 27+ organizations, this framework describes how EA practices actually work rather than prescribing how they should work. This is not an official IASA document.
OWL Ontology v0.1.0 2026-05-03 application/ld+json application/n-triples application/rdf+xml text/turtle
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 instances of the six CSVLOD artifact type classes, process structure, governance arrangements, and maturity stages. Shapes are based on the ontology only — taxonomy classification is not enforced by SHACL.
SHACL Shapes v0.1.0 2026-05-03 text/turtle
Linked.Archi EA on a Page Taxonomy
https://meta.linked.archi/eaonapage/tax
Unified classification scheme for the EA on a Page framework. Organizes EA artifacts (CSVLOD taxonomy), maturity stages, governance model, and classification dimensions into a single navigable hierarchy with four top-level grouping concepts.
SKOS Concept Scheme v0.3.0 2026-06-15 text/turtle
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.
Viewpoint Definitions v0.1.0 2026-05-03 text/turtle
Linked.Archi EDGY 23 Deliverable Templates
https://meta.linked.archi/edgy/deliverable-templates
Deliverable template definitions for EDGY 23 enterprise design. Defines document templates for enterprise design outputs — capability maps, journey maps, service blueprints, enterprise overviews, and identity documents.
Deliverable Templates v23 2026-04-17 text/turtle
Linked.Archi EDGY 23 Metamodel Definition
https://meta.linked.archi/edgy/metamodel
Metamodel manifest for EDGY 23 — the Enterprise Design language by Intersection Group. This file ties together all the EDGY semantic resources — the element/relationship ontology and SKOS taxonomy — into a single arch:Metamodel instance. EDGY is an open-source tool for collaborative Enterprise Design that provides a simple but rich visual language of base elements, facet elements, relationships, and labels to describe what an enterprise consists of and how its parts form a whole. This is the entry point for tools that need to discover all resources that make up the EDGY 23 modeling language definition.
Metamodel Manifest v23 2026-10-06 text/turtle
Linked.Archi EDGY 23 Visual Notation Set
https://meta.linked.archi/edgy/notation
Updated visual notation descriptors for EDGY 23 enterprise design elements, relationships, and labels. This set corrects the EDGY base shapes, facet/intersection colours, relationship line semantics, and icon/glyph references for Linked.Archi renderers.
Visual Notation v23 updated draft 2026-10-10 text/turtle
Linked.Archi EDGY 23 Visual Notation Set (v1, circle-based)
https://meta.linked.archi/edgy/notation-v1
Visual notation descriptors for EDGY 23 enterprise design elements and relationships. Alternative, circle-based rendering of the EDGY visual language: all elements are drawn as circles. The default set, https://meta.linked.archi/edgy/notation#, follows the canonical EDGY shapes. Base elements use a neutral grey palette. Facet elements are coloured by facet — yellow for Identity (Purpose, Story, Content), blue for Architecture (Capability, Process, Asset), red for Experience (Task, Journey, Channel). Intersection elements use the colour produced by mixing their two parent facets — green for Organisation (Identity ∩ Architecture), orange for Brand (Identity ∩ Experience), and purple for Product (Architecture ∩ Experience). Every element notation references both a composed icon (arch:prefVisNotation) and a glyph (arch-vis:iconSymbol) so it can be rendered either as a preview or as a shape-with-badge.
Visual Notation v23 2026-10-06 text/turtle
Linked.Archi EDGY 23 Ontology
https://meta.linked.archi/edgy/onto
OWL ontology for the EDGY 23 Enterprise Design language by Intersection Group. Defines the four base elements (People, Outcome, Activity, Object), twelve facet and intersection elements, three relationship types (Link, Flow, Tree), and two label types (Tagging, Metrics). EDGY content is available under CC BY-SA 4.0 license.
OWL Ontology v23 2026-04-17 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi EDGY 23 Presentation Contexts
https://meta.linked.archi/edgy/presentation-contexts
Audiences for EDGY 23 maps. Each context is an audience, as the core ontology defines a presentation context, and picks one of EDGY's two notation sets with arch:usesNotationSet: the Enterprise designer context the default (v2) set, the Overview map reader context the circle-based v1 set. The EDGY manifest, https://meta.linked.archi/edgy/metamodel#EDGY23, names only the v2 set with arch:notationSet, which keeps it the default; the v1 set is reached through this scheme alone.
SKOS Concept Scheme v23 2026-10-05 text/turtle
Linked.Archi EDGY 23 Reference Data
https://meta.linked.archi/edgy/reference-data
Reference data for EDGY 23 enterprise design models — pre-defined tag types for asset classification, metric categories, capability maturity levels, and other enumerated values commonly used in EDGY maps.
SKOS Concept Scheme v23 2026-04-17 text/turtle
Linked.Archi EDGY 23 SHACL Shapes
https://meta.linked.archi/edgy/shapes
SHACL validation shapes for EDGY 23 enterprise design models. Enforces element labeling requirements, relationship source/target constraints, and core link domain/range validity.
SHACL Shapes v23 2026-04-17 text/turtle
Linked.Archi EDGY 23 Taxonomy
https://meta.linked.archi/edgy/tax
Classification of EDGY 23 enterprise elements into base elements, facet elements (by facet category), intersection elements, relationships, and labels.
SKOS Concept Scheme v23 2026-05-17 text/turtle
Linked.Archi EDGY 23 Viewpoints
https://meta.linked.archi/edgy/viewpoints
Viewpoint definitions for EDGY 23 enterprise design models. Defines viewpoints aligned with the three EDGY facets (Identity, Architecture, Experience), their intersections, and cross-cutting enterprise-wide perspectives.
Viewpoint Definitions v23 2026-04-17 text/turtle
Claims handling
https://meta.linked.archi/examples/archimate3.2-questions/
Model text/turtle
Claims handling
https://meta.linked.archi/examples/archimate4-questions/
Model text/turtle
NordFreight Organization
https://meta.linked.archi/examples/archimate4-viewpoint/
Model text/turtle
Atlas Global Bank — Enterprise Architecture Model
https://meta.linked.archi/examples/atlas-bank/
TOGAF 10 enterprise architecture model for Atlas Global Bank — a multinational financial services group executing a cloud-first digital transformation.
Model text/turtle
Cloud Platform Deliverable Templates
https://meta.linked.archi/examples/cloudplatform/deliverable-templates
Deliverable template definitions for generating architecture documents from Custom Metamodel models.
Deliverable Templates v0.1.0 text/turtle
Cloud Platform Architecture Metamodel
https://meta.linked.archi/examples/cloudplatform/metamodel
Metamodel manifest for the Cloud Platform Architecture example.
Metamodel Manifest v0.1.0 text/turtle
Payment Platform
https://meta.linked.archi/examples/cloudplatform/model/
Example architecture model of a payment platform using the Cloud Platform metamodel.
Model text/turtle
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.
OWL Ontology v0.1.0 2026-05-03 application/ld+json application/n-triples application/rdf+xml text/turtle
Cloud Platform Reference Data
https://meta.linked.archi/examples/cloudplatform/reference-data
Controlled vocabularies and reference data for Custom Metamodel architecture models.
SKOS Concept Scheme v0.1.0 text/turtle
Cloud Platform SHACL Shapes
https://meta.linked.archi/examples/cloudplatform/shapes
Validation rules for the Cloud Platform Architecture metamodel.
SHACL Shapes v0.1.0 text/turtle
Cloud Platform Taxonomy
https://meta.linked.archi/examples/cloudplatform/tax
SKOS taxonomy providing a hierarchical classification of Custom Metamodel concepts.
SKOS Concept Scheme v0.1.0 text/turtle
Cloud Platform Viewpoints
https://meta.linked.archi/examples/cloudplatform/viewpoints
Architecture viewpoint definitions for Custom Metamodel.
Viewpoint Definitions v0.1.0 text/turtle
Core-vis Diagram Reference Example
https://meta.linked.archi/examples/diagram/
Reference instance data for the Linked.Archi diagram interchange layer. Two application components connected by a named flow, laid out on one view, with the edge label attached through arch-vis:label — which is only expressible because arch-vis:label has rdfs:domain arch-vis:DiagElement rather than arch-vis:Node.
Model text/turtle
Example presentation contexts
https://meta.linked.archi/examples/labels/
Model text/turtle
SAP LeanIX Meta Model v4 — Documentation Example Landscape
https://meta.linked.archi/examples/leanix-docs-example/
A small LeanIX workspace assembled from the examples SAP's own LeanIX documentation gives for each fact sheet type, wired together with a selection of Meta Model v4 relationships and carrying the fact sheet attributes — status, completion, dated lifecycle phases, subscriptions and tags. Its purpose is to be validated, not admired: it is the data that exercises leanIX-shapes.ttl, which until now had nothing to fire on. It is deliberately small enough to read in one sitting. This is not an official SAP document, and SAP does not publish this landscape. What SAP publishes are the individual examples named below; assembling them into one connected workspace is this repository's doing.
Model v0.2.0 2026-11-16 text/turtle
Meridian Insurance Group — Enterprise Design Model
https://meta.linked.archi/examples/meridian/
EDGY 23 enterprise design model for Meridian Insurance Group — a multinational P&C insurer operating across 12 European markets.
Model text/turtle
NordFreight Logistics — Architecture Model
https://meta.linked.archi/examples/nordfreight/
ArchiMate 4.0 architecture model for NordFreight Logistics — a Scandinavian freight company modernising its tracking platform.
Model 2026-10-11 text/turtle
PayFlow — Backstage Catalog Model
https://meta.linked.archi/examples/payflow/
Backstage software catalog model for PayFlow — a fintech platform providing payment processing, merchant onboarding, and financial reporting.
Model text/turtle
UML Reference Example
https://meta.linked.archi/examples/uml/
Reference instance data for the Linked.Archi UML ontology: a small ordering domain as a class model, and the order lifecycle as a state machine. Exists mainly so the UML shapes are exercised against instances rather than against the ontology's own enumeration individuals.
Model text/turtle
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.
Metamodel Manifest v0.1.0 2026-05-03 text/turtle
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. Trademarked names referenced herein are property of their respective owners.
OWL Ontology v0.1.0 2026-05-03 application/ld+json application/n-triples application/rdf+xml text/turtle
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.
OWL Ontology v0.1.0 2026-05-03 application/ld+json application/n-triples application/rdf+xml text/turtle
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.
SHACL Shapes v0.1.0 2026-05-03 text/turtle
Linked.Archi Financial Architecture Taxonomy
https://meta.linked.archi/financial-architecture/tax
Classification of financial architecture concepts by cost type, investment type, and analysis type.
SKOS Concept Scheme v0.1.0 2026-05-03 text/turtle
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.
OWL Ontology v0.1.0 2020-07-27 application/ld+json application/n-triples application/rdf+xml text/turtle
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.
OWL Ontology v0.1.0 2020-07-27 application/ld+json application/n-triples application/rdf+xml text/turtle
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.
OWL Ontology v0.2.0 2026-05-02 application/ld+json application/n-triples application/rdf+xml text/turtle
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.
OWL Ontology v0.2.0 2026-05-02 application/ld+json application/n-triples application/rdf+xml text/turtle
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.
OWL Ontology v0.2.0 2026-05-02 application/ld+json application/n-triples application/rdf+xml text/turtle
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.
OWL Ontology v0.1.0 2019-03-17 application/ld+json application/n-triples application/rdf+xml text/turtle
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 six architecture processes for governing and managing the architecture of systems and software: architecture governance, architecture management, architecture conceptualization, architecture evaluation, architecture elaboration, and architecture enablement.
OWL Ontology v0.2.0 2026-07-16 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi LeanIX Cross-Language Mappings
https://meta.linked.archi/leanix/crossmappings
Cross-language SKOS mappings between SAP LeanIX Meta Model v4 fact sheet types and relations and ArchiMate modeling language concepts, for both ArchiMate 3.2 and ArchiMate 4.0. These mappings are editorial. SAP LeanIX publishes guidance on how its meta model relates to enterprise architecture practice, but no normative element-level correspondence to ArchiMate, and the ArchiMate specification does not mention LeanIX. The assertions here express semantic proximity based on the fact sheet definitions in the LeanIX documentation and the concept definitions in the ArchiMate specifications. LeanIX is a portfolio tool: a fact sheet is the unit of inventory, ownership and lifecycle, and its relations record support and dependency rather than detailed behaviour. Where a fact sheet type and an ArchiMate concept describe the same kind of thing at the same grain — Business Capability and Capability, Value Stream and Value Stream, Data Object and Data Object — the mapping is skos:closeMatch; exactMatch is avoided throughout because each fact sheet type carries portfolio semantics (lifecycle, subscriptions, completion) that the ArchiMate concept does not. Where LeanIX collapses several ArchiMate concepts into one type (Interface, IT Component) the mappings are skos:relatedMatch and fan out. Relation mappings carry a caveat on direction. LeanIX relations are stored on the fact sheet that owns them (an application requires an IT component; an IT component is part of a platform), which often runs opposite to the ArchiMate reading (the IT component serves the application; the platform aggregates the component). The SKOS assertions relate the relationship types only; a query that translates instances must reverse the direction where the comment says so. These are type-level statements. Instance-level correspondence is asserted in the export's Linked.Archi fact sheet index, against a shared id namespace. Not mapped, deliberately: lmm:FactSheet (abstract), lmm:BusinessContext (broad grouping; its more specific subtypes are mapped), and subscriptions, tags, status and lifecycle phases, which are portfolio metadata rather than architecture.
OWL Ontology v0.2.0 2026-11-16 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi LeanIX Deliverable Templates
https://meta.linked.archi/leanix/deliverable-templates
Deliverable template definitions for generating architecture documents from LeanIX models.
Deliverable Templates text/turtle
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, shapes, viewpoints, taxonomy, notation set and deliverable templates into a single discoverable resource. Reference data and presentation contexts can be added later. Also the home of the version-free arch:Framework individual for SAP LeanIX, which the v3 manifest at leanix/v3/metamodel# points at as well.
Metamodel Manifest v0.2.0 2026-11-16 text/turtle
Linked.Archi LeanIX Visual Notation Set
https://meta.linked.archi/leanix/notation
Visual notation descriptors for LeanIX Meta Model v4 fact sheet types.
Visual Notation v0.2.0 2026-11-16 text/turtle
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) and the optional types System, Data Product, Contract and the Business Context subtype ESG Capability, 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.
OWL Ontology v4.2.0 2026-11-16 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi LeanIX SHACL Shapes
https://meta.linked.archi/leanix/shapes
SHACL shapes for validating SAP LeanIX Meta Model fact sheet data. Covers both published LeanIX ontologies — v4 (lmm:) and v3 (lmm3:) — because both are live namespaces rooted at FactSheet. Fact sheet naming applies to both versions. Value-set and cardinality rules constrain v4 attributes (DD-23), while endpoint shapes constrain v4 relationship pairs. The ontology deliberately does not close the attribute vocabularies in OWL. This is not an official SAP document.
SHACL Shapes v0.3.0 2026-11-16 text/turtle
Linked.Archi LeanIX Taxonomy
https://meta.linked.archi/leanix/tax
Classification of SAP LeanIX types and subtypes by architecture layer, with separate availability collections.
SKOS Concept Scheme 2026-11-16 text/turtle
Linked.Archi LeanIX Meta Model v3 Metamodel Definition
https://meta.linked.archi/leanix/v3/metamodel
Metamodel manifest for the SAP LeanIX Meta Model v3. Gives a workspace still shaped by v3 fact sheet types something to point arch:modelConformsToMetamodel at, which it otherwise lacked: leanix/v3/onto# is published and leanix/shapes# targets it, so v3 is a supported namespace rather than an archive, but there was no arch:Metamodel individual for it. Deliberately thin. v3 publishes fact sheet classes only — no relationships, no taxonomy, no viewpoints, no notation set — so this manifest declares the two resources that exist and omits the rest rather than pointing them at v4 assets that describe different fact sheet types. This is not an official SAP document.
Metamodel Manifest v0.1.0 2026-08-16 text/turtle
Linked.Archi LeanIX Meta Model v3 Visual Notation Set
https://meta.linked.archi/leanix/v3/notation
Visual notation descriptors for LeanIX Meta Model v3 fact sheet types.
Visual Notation v0.1.0 2026-11-16 text/turtle
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. This is not an official SAP document.
OWL Ontology v3 2026-04-12 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi LeanIX Meta Model v3 Taxonomy
https://meta.linked.archi/leanix/v3/tax
Classification of the LeanIX Meta Model v3 fact sheet types by architecture layer.
SKOS Concept Scheme 2026-11-16 text/turtle
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.
Viewpoint Definitions v0.2.0 2026-11-16 text/turtle
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.
Metamodel Manifest v0.1.0 2026-05-03 text/turtle
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. Trademarked names referenced herein are property of their respective owners.
OWL Ontology v0.1.0 2026-05-03 application/ld+json application/n-triples application/rdf+xml text/turtle
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).
OWL Ontology v0.1.0 2026-05-03 application/ld+json application/n-triples application/rdf+xml text/turtle
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.
SHACL Shapes v0.1.0 2026-05-03 text/turtle
Linked.Archi ML-Enabled Systems Taxonomy
https://meta.linked.archi/ml-systems/tax
Classification of ML-enabled system concepts by lifecycle phase and component role.
SKOS Concept Scheme v0.1.0 2026-05-03 text/turtle
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.
SKOS Concept Scheme v0.2.0 2026-05-02 text/turtle
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.
OWL Ontology v0.1.0 2026-04-16 application/ld+json application/n-triples application/rdf+xml text/turtle
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.
OWL Ontology v0.0.5 2026-04-16 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi Reference Architecture Metamodel Definition
https://meta.linked.archi/ref-arch/metamodel
Metamodel manifest for the Reference Architecture extension with the Tactics extension. Ties together the two ontologies and their SKOS taxonomies into a single discoverable resource. Designed to be added beside a modelling language: building blocks, standards and tactics are placed among the elements of the architecture they shape.
Metamodel Manifest v0.1.0 2026-11-16 text/turtle
Linked.Archi Reference Architecture Taxonomy
https://meta.linked.archi/ref-arch/tax
Classification of the Reference Architecture element types: building blocks, standards and tactics.
SKOS Concept Scheme v0.1.0 2026-11-16 text/turtle
Simple Example Ontology
https://meta.linked.archi/simple-example
Simplest possible Linked.Archi metamodel example demonstrating a minimal element type and relationship definition.
OWL Ontology v0.1.0 application/ld+json application/n-triples application/rdf+xml text/turtle
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.
OWL Ontology v0.1.0 2026-04-16 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi Tactics Taxonomy
https://meta.linked.archi/tactics/tax
Classification of the architectural tactics by the quality attribute they serve.
SKOS Concept Scheme v0.1.0 2026-11-16 text/turtle
Linked.Archi Technology Radar Metamodel Definition
https://meta.linked.archi/tech-radar/metamodel
Metamodel manifest for the Technology Radar framework. Ties together the Tech Radar ontology and controlled vocabularies into a single discoverable resource for technology governance.
Metamodel Manifest v0.1.0 2026-06-22 text/turtle
Linked.Archi Technology Radar Ontology
https://meta.linked.archi/tech-radar/onto
Ontology for representing technology governance decisions using the Technology Radar model. Classifies technologies into rings (Adopt, Trial, Assess, Hold) and quadrants (domains), with point-in-time assessments tracking movement over time. Inspired by the ThoughtWorks Technology Radar (est. 2010). Extended with a Retire ring for portfolio lifecycle management. This is the OWL layer of the Tech Radar framework. Use together with: * tech-radar-shapes.ttl (SHACL) — validates completeness and value constraints * tech-radar-tax.ttl (SKOS) — organizes controlled vocabularies for navigation This is not an official ThoughtWorks document.
OWL Ontology v0.1.0 2026-06-22 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi Technology Radar SHACL Shapes
https://meta.linked.archi/tech-radar/shapes
SHACL shapes for validating Technology Radar model data. Ensures technologies have required metadata, assessments are complete, and controlled vocabulary values are valid.
SHACL Shapes v0.1.0 2026-06-22 text/turtle
Linked.Archi Technology Radar Taxonomy
https://meta.linked.archi/tech-radar/tax
Classification of Technology Radar controlled vocabularies: rings, quadrants, and movement directions.
SKOS Concept Scheme v0.1.0 2026-06-22 text/turtle
Linked.Archi TIME Framework Cross-Language Mappings
https://meta.linked.archi/time-framework/crossmappings
Cross-language SKOS mappings between TIME framework concepts and other Linked.Archi modeling languages. These are editorial correspondences — no official mapping exists between the Gartner TIME model and ArchiMate, Backstage, or TOGAF. Mappings express semantic proximity based on concept definitions across frameworks. Usage: a single application IRI can be multi-typed as both a timefw:Application and an am:ApplicationComponent (or bs:Component). These mappings document which concepts are interchangeable for querying purposes.
OWL Ontology v0.1.0 2026-10-11 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi TIME Framework Derivation Rules
https://meta.linked.archi/time-framework/derivation
SHACL Rules (sh:SPARQLRule) implementing disposition movement derivation for the TIME framework. Computes previousDisposition and dispositionMovement from the assessment history of each application, ordered by assessmentDate. Derived triples are annotated with PROV-O provenance: * prov:wasGeneratedBy — the derivation activity that produced the triple: an activity whose plan is the derivation rule (prov:qualifiedAssociation, prov:hadPlan); what runs the rules may record its run, an activity with its agent and when it ran, of which the derivation activity is part (dcterms:isPartOf) * prov:wasDerivedFrom — the source assessments used for derivation This follows the same pattern as the ArchiMate derivation rules (archimate3.2-derivation-rules.ttl) — derived facts are traceable and distinguishable from manually asserted facts. Usage: Run these rules AFTER loading assessment data. Derived triples supplement (do not replace) any manually asserted dispositionMovement or previousDisposition values.
SHACL Shapes v0.1.0 2026-05-05 text/turtle
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.
Metamodel Manifest v0.2.0 2026-05-02 text/turtle
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 This is not an official Gartner document.
OWL Ontology v0.2.0 2026-05-02 application/ld+json application/n-triples application/rdf+xml text/turtle
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. Includes a SPARQL-based consistency guard that verifies timeDisposition matches the implied quadrant when both functionalFitRating and technicalFitRating are present. 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
SHACL Shapes v0.2.0 2026-05-03 text/turtle
Linked.Archi TIME Framework Taxonomy
https://meta.linked.archi/time-framework/tax
Classification of TIME framework controlled vocabularies: dispositions, fit ratings, fit dimensions, assessment statuses, evidence types, and lifecycle states.
SKOS Concept Scheme v0.2.0 2026-05-03 text/turtle
Linked.Archi TOGAF Cross-Language Mappings
https://meta.linked.archi/togaf/crossmappings
Cross-language SKOS mappings between TOGAF Content Metamodel concepts and ArchiMate modeling language concepts. TOGAF ↔ ArchiMate mappings are derived from: The Open Group, "Mapping of the TOGAF Content Metamodel to ArchiMate" https://pubs.opengroup.org/architecture/archimate3-doc/ch-Mapping-TOGAF-Content-Metamodel.html This appendix in the ArchiMate 3.x specification provides an official mapping between TOGAF Content Metamodel entity types and ArchiMate elements. The ArchiMate 4.0 mappings extend this with the updated element names from the 4.0 "Hexagonion" restructuring.
OWL Ontology v0.1.0 2026-05-05 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi TOGAF Deliverable Templates
https://meta.linked.archi/togaf/deliverable-templates
Deliverable template definitions for generating architecture documents from TOGAF models.
Deliverable Templates text/turtle
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.
Metamodel Manifest v10.0 2026-04-24 text/turtle
Linked.Archi TOGAF 10 Enterprise Metamodel
https://meta.linked.archi/togaf/onto
Linked.Archi ontology aligned to the TOGAF Enterprise Metamodel as defined in TOGAF 10 (Architecture Content, Chapter 2). Models the entity types and relationships of the Enterprise Metamodel as OWL classes and properties, conforming to Linked.Archi core ontology conventions. This is not an official Open Group document.
OWL Ontology v10.0 2026-05-11 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi TOGAF SHACL Shapes
https://meta.linked.archi/togaf/shapes
SHACL shapes for validating TOGAF Content Metamodel data. Covers both published TOGAF ontologies — TOGAF 10 (togaf:) and TOGAF 9.2 (togaf9:) — because both are live namespaces with the same abstract element roots. This is not an official Open Group document.
SHACL Shapes v0.1.0 2026-08-04 text/turtle
Linked.Archi TOGAF 10 Taxonomy
https://meta.linked.archi/togaf/tax
Classification of TOGAF 10 entities by architecture domain.
SKOS Concept Scheme v10.0 2026-05-11 text/turtle
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).
Viewpoint Definitions v10.0 2026-04-24 text/turtle
Linked.Archi TOGAF 9.2 Content Metamodel
https://meta.linked.archi/togaf9/onto
Linked.Archi ontology aligned to the TOGAF Content Metamodel as defined in TOGAF 9.2 (Chapter 30). 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.
OWL Ontology v9.2 2026-04-29 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi TOGAF 9.2 Taxonomy
https://meta.linked.archi/togaf9/tax
Classification of TOGAF entities by architecture domain.
SKOS Concept Scheme v9.2 2026-04-24 text/turtle
Linked.Archi UAF Cross-Language Mappings
https://meta.linked.archi/uaf/crossmappings
Cross-language SKOS mappings between UAF 1.2 concepts and other modeling languages in the Linked.Archi knowledge graph. UAF ↔ DoDAF mappings are derived from the OMG UAF 1.2 Specification, Appendix A — Traceability (https://www.omg.org/spec/UAF/1.2/). UAF ↔ ArchiMate mappings are editorial — no official OMG or Open Group document formally maps UAF to ArchiMate. These express semantic proximity based on concept definitions. Mappings are provided for both ArchiMate 3.2 and ArchiMate 4.0.
OWL Ontology v0.2.0 2026-05-05 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi UAF Metamodel Definition
https://meta.linked.archi/uaf/metamodel
Metamodel manifest for the Unified Architecture Framework (UAF) 1.2. Ties together the UAF entity ontology, SHACL shapes, SKOS taxonomy, viewpoint definitions, and alignment axioms into a single discoverable resource. UAF supersedes DoDAF, MODAF, and NAF, providing a unified framework that organizes architectural data across 10 viewpoints and 11 aspects. This is not an official OMG document.
Metamodel Manifest v1.2 2026-02-01 text/turtle
Linked.Archi UAF Ontology
https://meta.linked.archi/uaf/onto
Linked.Archi ontology aligned to the Unified Architecture Framework (UAF) version 1.2, an OMG standard (formal/2025-10-01 through formal/2025-10-07). UAF provides a unified architecture framework superseding DoDAF, MODAF, and NAF. It organizes architectural data across 10 viewpoints and 11 aspects, defining approximately 288 metaclasses across multiple domains. This ontology models the core entity types used across UAF viewpoints as OWL classes extending arch:Element, and the key relationships using the three-declaration pattern (unqualified predicate, qualified class, qualified property). This is not an official OMG document.
OWL Ontology v1.2 2026-02-01 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi UAF SHACL Shapes
https://meta.linked.archi/uaf/shapes
SHACL shapes for validating UAF 1.2 model data. Imports core-shapes for base QualifiedRelationship validation. Adds UAF-specific domain/range constraints per relationship type. This is not an official OMG document.
SHACL Shapes v1.2 2026-08-04 text/turtle
Linked.Archi UAF Taxonomy
https://meta.linked.archi/uaf/tax
Classification of UAF 1.2 metaclasses by viewpoint and aspect.
SKOS Concept Scheme v1.2 2026-02-01 text/turtle
UAF 1.2 Architecture Viewpoints
https://meta.linked.archi/uaf/viewpoints
UAF 1.2 viewpoints modeled as arch:Viewpoint individuals. UAF defines 10 viewpoints that organize architectural concerns. Each viewpoint specifies the concepts it includes, its purpose, and the concerns it frames. This is not an official OMG document.
Viewpoint Definitions v1.2 2026-02-01 text/turtle
Linked.Archi UML 2.5.1 Metamodel Definition
https://meta.linked.archi/uml/metamodel
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.
Metamodel Manifest v0.1.0 2026-02-01 text/turtle
Linked.Archi UML 2.5.1 Visual Notation Set
https://meta.linked.archi/uml/notation
Visual notation descriptors for UML 2.5.1 concrete metaclasses, following the standard UML notation.
Visual Notation v0.1.0 2026-10-10 text/turtle
Linked.Archi UML 2.5.1 Ontology
https://meta.linked.archi/uml/onto
RDF/OWL formalization of the OMG Unified Modeling Language (UML) 2.5.1 metamodel for use in the Linked.Archi architecture knowledge graph. Covers structural classifiers (Class, Interface, Component, Package), behavioral elements (Activity, StateMachine, Interaction), deployment concepts (Node, Artifact), and use cases (Actor, UseCase). Relationship types follow the Linked.Archi three-declaration qualified relationship pattern. This ontology is INFORMED BY the OMG Ontology Definition Metamodel (ODM, formal/2014-09-02) but does NOT apply ODM directly. ODM Annex D maps UML model instances (M1) to OWL; this ontology represents the UML metamodel itself (M2) as OWL classes so that UML model data can be typed in a knowledge graph. We adopt ODM principles (Class→owl:Class, Generalization→rdfs:subClassOf, Package→owl:Ontology) but depart from ODM for associations (three-declaration pattern), enumerations (SKOS), constraints (SHACL), and domain/range (arch:domainIncludes). See the skos:scopeNote for the full comparison. This is not an official OMG document. It is a Linked.Archi interpretation of the UML specification for semantic architecture modeling.
OWL Ontology v0.3.0 2026-08-13 application/ld+json application/n-triples application/rdf+xml text/turtle
Linked.Archi UML Publication SHACL Shapes
https://meta.linked.archi/uml/publication-shapes
Opt-in SHACL shapes for UML models that are going to be read by someone. Requires a language-tagged skos:prefLabel on the UML constructs a reader needs named — classifiers, packages, features, actors, use cases, lifelines — and leaves out the constructs UML draws rather than names. This document is deliberately NOT part of uml/shapes#. UML 2.5.1 §7.4 makes NamedElement::name [0..1], so nothing in UML must be named, and uml/shapes# says what UML is. A naming requirement is a publication policy: reasonable to hold, but not a fact about the language, and not something a conformance check should assert on a modeller's behalf. Load this only when unnamed elements really are a defect for your purpose — generating a document, building a palette, populating a catalogue.
SHACL Shapes v0.1.0 2026-08-13 text/turtle
Linked.Archi UML 2.5.1 SHACL Shapes
https://meta.linked.archi/uml/shapes
SHACL shapes for validating UML model data in the Linked.Archi knowledge graph. Covers relationship domain/range constraints, required properties, and structural integrity rules derived from the UML 2.5.1 specification.
SHACL Shapes v0.3.0 2026-08-13 text/turtle
Linked.Archi UML 2.5.1 Taxonomy
https://meta.linked.archi/uml/tax
Classification of UML metaclasses by diagram type and by metaclass category, plus the enumeration value sets, aligned to the UML 2.5.1 specification structure.
SKOS Concept Scheme text/turtle
Linked.Archi UML 2.5.1 Viewpoints
https://meta.linked.archi/uml/viewpoints
UML 2.5.1 diagram types formalized as Linked.Archi viewpoints. Each of the 14 UML diagram types is represented as an arch:Viewpoint instance with its included concepts, purpose, and framed concerns.
Viewpoint Definitions v0.1.0 2026-02-01 text/turtle
Zachman Framework Deliverable Templates
https://meta.linked.archi/zachman/deliverable-templates
Deliverable templates for the Zachman Framework. Provides an EA Artifact Coverage Report that queries the knowledge graph for artifacts classified by Zachman perspective and interrogative (or directly by cell), identifies gaps, and generates a coverage matrix.
Deliverable Templates v0.3.0 2026-02-17 text/turtle
Zachman Framework Metamodel Manifest
https://meta.linked.archi/zachman/metamodel
Metamodel manifest for the Zachman Framework. Aggregates the taxonomy (6 Aspects, 6 Perspectives, 36 Cells), SHACL validation shapes, and deliverable templates into a single entry point. The Zachman Framework is a classification schema — it does not define element types or viewpoints. It provides a 6x6 grid for classifying descriptive representations produced by other modeling languages.
Metamodel Manifest v0.3.0 2026-02-17 text/turtle
Linked.Archi Zachman Framework Ontology
https://meta.linked.archi/zachman/onto
OWL ontology for the Zachman Framework for Enterprise Architecture. Defines the Framework individual and the properties used to link Zachman Cells to their Aspect (column) and Perspective (row). The SKOS taxonomy of concepts is in the companion file zachman-tax.ttl. The Zachman Framework is not a methodology — it is a classification schema for organizing descriptive representations of an enterprise. This is not an official Zachman International product. "Zachman Framework" is a registered trademark of Zachman International, Inc.
OWL Ontology v0.3.0 2026-02-17 application/ld+json application/n-triples application/rdf+xml text/turtle
Zachman Framework SHACL Shapes
https://meta.linked.archi/zachman/shapes
SHACL validation shapes for viewpoints classified using the Zachman Framework taxonomy. Validates that viewpoints using Zachman cell classification are consistent with their aspect and perspective declarations.
SHACL Shapes v0.3.0 2026-02-17 text/turtle
Linked.Archi Zachman Framework Taxonomy
https://meta.linked.archi/zachman/tax
Classification of enterprise architecture descriptions using the Zachman Framework 6x6 matrix. Organizes concepts into five families: Aspect (the six columns representing what question is being answered), Perspective (the six rows representing at what level of reification and for which audience), Cell (the 36 intersections, each classifying a primitive descriptive representation), Enterprise Type (the category of enterprise description produced by each column), and Model Type (the category of model produced by each row).
SKOS Concept Scheme v0.3.0 2026-02-17 text/turtle
Zachman Framework Viewpoints
https://meta.linked.archi/zachman/viewpoints
Viewpoint definitions for the Zachman Framework. Declares the six Aspects as arch:Aspect individuals, the six Perspectives as arch:Perspective individuals, and 36 viewpoints — one per Zachman Cell — each classified by its cell coordinate.
Viewpoint Definitions v0.3.0 2026-02-17 text/turtle

Content Negotiation

https://meta.linked.archi/catalog answers Accept: text/turtle with catalog.ttl, Accept: application/ld+json with catalog.jsonld, and a browser with this page.