Linked.Archi — Enterprise Architecture as a Queryable Knowledge Graph¶
Architecture knowledge is scattered across tools that don't talk to each other. ArchiMate models sit in Archi, service catalogues in Backstage, decisions in Confluence, and nobody can answer cross-cutting questions without days of manual research.
Linked.Archi solves this with a shared semantic layer — OWL ontologies, SHACL validation shapes, and SKOS taxonomies that turn disconnected architecture data into a single queryable graph. This documentation covers every module in the ecosystem: how to use them, how to compose them, and how to build your own.
Getting Started — Find What You Need¶
| If you want to... | Read |
|---|---|
| Understand what Linked.Archi is | What is Linked.Archi? |
| Get started quickly | Quick Start Guide |
| Understand the philosophy | Architecture & Approach |
| See how the pipeline works end-to-end | How Linked.Archi Bridges the Gap |
| Choose and combine modelling languages | Modelling Languages Guide |
| Understand the extensions | Extensions Guide |
| Model governance processes | Processes Modelling Guide |
| Understand the frameworks | Frameworks Guide |
| Design a metamodel | Relationship Modelling Guide |
| Explore the ontology catalogue | Ontology Reference |
| Visual notation and palettes | Visual Notation Guide |
| Understand modelling choices | Design Decisions |
| Validate ontologies and models | Validation Guide |
| Author models as code | Semantic Architecture as Code |
| Evaluate DSL options | ArchiMate in Structurizr DSL and Beyond |
| See real-world scenarios | Use Cases |
Key Concepts — The Core Ontology Building Blocks¶
| Concept | What it is |
|---|---|
arch:ModelConcept |
Base class for everything in a model: elements, relationships, views |
arch:Element |
Nodes in the architecture (subclassed per metamodel) |
arch:QualifiedRelationship |
First-class relationship resources (subclassed per metamodel) |
arch:View / arch:Viewpoint |
Stakeholder-specific representations |
arch:Metamodel |
Manifest aggregating all resources for a modelling language (see DD-13) |
arch:DeliverableTemplate |
Template defining document structure via viewpoint placeholders |
arch:PresentationFormat |
Output format for rendering deliverables (Markdown, HTML, PDF) |
arch:unqualifiedForm |
Schema-level mapping from qualified form to direct predicate |
Namespace Reference — OWL Ontology IRIs and Prefixes¶
| Prefix | Namespace |
|---|---|
arch: |
https://meta.linked.archi/core# |
amate: |
https://meta.linked.archi/archimate3/onto# |
ad: |
https://meta.linked.archi/arch-decision# |
ap: |
https://meta.linked.archi/arch-processes# |
refa: |
https://meta.linked.archi/ref-arch# |
togaf: |
https://meta.linked.archi/togaf/metamodel# |
timefw: |
https://meta.linked.archi/time-framework/onto# |
Building the Documentation Locally¶
The documentation is built with MkDocs Material. Run these commands to serve the site on your machine:
Then open http://127.0.0.1:8000/.
To build a static site for deployment:
The GitLab CI pipeline (.gitlab-ci.yml) builds and deploys to GitLab Pages automatically on changes to doc/.
Additional Resources¶
Architecture practice guidance — comparisons, positioning, and strategy for using the metamodels alongside other modelling approaches — is in doc/practice/. See the practice README for the full list.