language en

Linked.Archi ArchiMate 3.2 Ontology

Release: 2019-03-17

Modified on: 2025-12-01
This version:
https://meta.linked.archi/archimate3/onto/3.2#
Previous version:
https://meta.linked.archi/archimate3/onto/3.1#
Revision:
3.2
Issued on:
2019-03-17
Authors:
Kalin Maldzhanski
Publisher:
Linked.Archi
Source:
http://www.opengroup.org/xsd/archimate/3.1/archimate3_Model.xsd
https://pubs.opengroup.org/architecture/archimate3-doc
See also:
https://www.w3.org/TR/rdf12-concepts/
Download serialization:
JSON-LD RDF/XML N-Triples TTL
License:
http://creativecommons.org/licenses/by/4.0/
Visualization:
Visualize with WebVowl
Cite as:
Linked.Archi ArchiMate Ontology
Provenance of this page
draft

Abstract

Linked.Archi ArchiMate ontology based on the ArchiMate 3.2 specification. Represents ArchiMate elements, relationship types (using the three-declaration qualified relationship pattern), and composite/connector concepts as RDF/OWL. Version 3.2 modernizes the ontology to current Linked.Archi conventions and RDF 1.2 rdf:reifies.

Linked.Archi ArchiMate 3.2 Ontology: Overview back to ToC

This ontology has the following classes and properties.

Classes

Object Properties

Data Properties

Annotation Properties

Linked.Archi ArchiMate 3.2 Ontology: Description back to ToC

Linked.Archi ArchiMate ontology aligned to the ArchiMate 3.2 specification, modernized to conform to Linked.Archi core ontology conventions, the qualified relationship pattern, and RDF 1.2. This is not an official Open Group document.

Cross-reference for Linked.Archi ArchiMate 3.2 Ontology classes, object properties and data properties back to ToC

This section provides details for each class and property defined by Linked.Archi ArchiMate 3.2 Ontology.

Classes

Accessc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Access

An access relationship indicates that a behavior element may access a business or data object. The accessType property specifies read, write, read-write, or unspecified.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Access-Relationship
has super-classes
qualified relationship c
is in domain of
Access Type dp
is in range of
qualified Accesses op

ActiveStructureElementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#ActiveStructureElement

Active structure elements are the subjects that can perform behavior.
has super-classes
StructureElement c
has sub-classes
Communication Network c, Distribution Network c, ExternalActiveStructureElement c, InternalActiveStructureElement c, Path c

Aggregationc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Aggregation

An aggregation relationship indicates that an element combines one or more other elements. Unlike composition, the aggregated element can exist independently.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Aggregation-Relationship
has super-classes
qualified relationship c
is in range of
qualified Aggregates op

And Junctionc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Junction_And

An and junction is used to connect relationships of the same type where all must be satisfied.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Junction
has super-classes
element c

Application Collaborationc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#ApplicationCollaboration

An application collaboration represents an aggregate of two or more application components that work together to perform collective application behavior.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Application-Layer.html#sec-Application-Collaboration
has super-classes
ApplicationLayerElement c, Collaboration c

Application Componentc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#ApplicationComponent

An application component represents an encapsulation of application functionality aligned to implementation structure, which is modular and replaceable.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Application-Layer.html#sec-Application-Component
has super-classes
ApplicationLayerElement c, InternalActiveStructureElement c

Application Eventc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#ApplicationEvent

An application event is an application behavior element that denotes a state change.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Application-Layer.html#sec-Application-Event
has super-classes
ApplicationLayerElement c, Event c

Application Functionc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#ApplicationFunction

An application function represents automated behavior that can be performed by an application component.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Application-Layer.html#sec-Application-Function
has super-classes
ApplicationLayerElement c, InternalBehaviorElement c

Application Interactionc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#ApplicationInteraction

An application interaction represents a unit of collective application behavior performed by (a collaboration of) two or more application components.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Application-Layer.html#sec-Application-Interaction
has super-classes
ApplicationLayerElement c, Interaction c

Application Interfacec back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#ApplicationInterface

An application interface represents a point of access where application services are made available to a user, another application component, or a node.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Application-Layer.html#sec-Application-Interface
has super-classes
ApplicationLayerElement c, ExternalActiveStructureElement c

Application Processc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#ApplicationProcess

An application process represents a sequence of application behaviors that achieves a specific outcome.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Application-Layer.html#sec-Application-Process
has super-classes
ApplicationLayerElement c, InternalBehaviorElement c

Application Servicec back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#ApplicationService

An application service represents an explicitly defined exposed application behavior.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Application-Layer.html#sec-Application-Service
has super-classes
ApplicationLayerElement c, ExternalBehaviorElement c

ApplicationLayerElementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#ApplicationLayerElement

has super-classes
CoreLayerElement c
has sub-classes
Application Collaboration c, Application Component c, Application Event c, Application Function c, Application Interaction c, Application Interface c, Application Process c, Application Service c, Data Object c

Artifactc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Artifact

An artifact represents a piece of data that is used or produced in a software development process, or by deployment and operation of an IT system.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Technology-Layer.html#sec-Artifact
has super-classes
PassiveStructureElement c, TechnologyLayerElement c

Assessmentc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Assessment

An assessment represents the result of an analysis of the state of affairs of the enterprise with respect to some driver.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Motivation-Elements.html#sec-Assessment
has super-classes
MotivationElement c

Assignmentc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Assignment

An assignment relationship indicates the allocation of responsibility, performance of behavior, storage, or execution.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Assignment-Relationship
has super-classes
qualified relationship c
is in range of
qualified Assigned To op

Associationc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Association

An association relationship indicates an unspecified relationship, or one that is not represented by another ArchiMate relationship.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Association-Relationship
has super-classes
qualified relationship c
is in range of
qualified Associated With op

BehaviorElementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#BehaviorElement

Behavior elements represent the dynamic aspects of the enterprise.
has super-classes
element c
has sub-classes
Capability c, Course of Action c, Event c, ExternalBehaviorElement c, InternalBehaviorElement c, Value Stream c

Business Actorc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#BusinessActor

A business actor is a business entity that is capable of performing behavior.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Business-Layer.html#sec-Business-Actor
has super-classes
BusinessLayerElement c, InternalActiveStructureElement c

Business Collaborationc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#BusinessCollaboration

A business collaboration is an aggregate of two or more business internal active structure elements that work together to perform collective behavior.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Business-Layer.html#sec-Business-Collaboration
has super-classes
BusinessLayerElement c, Collaboration c

Business Eventc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#BusinessEvent

A business event is a business behavior element that denotes an organizational state change.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Business-Layer.html#sec-Business-Event
has super-classes
BusinessLayerElement c, Event c

Business Functionc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#BusinessFunction

A business function is a collection of business behavior based on a chosen set of criteria, closely aligned to an organization, but not necessarily explicitly governed by the organization.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Business-Layer.html#sec-Business-Function
has super-classes
BusinessLayerElement c, InternalBehaviorElement c

Business Interactionc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#BusinessInteraction

A business interaction is a unit of collective business behavior performed by (a collaboration of) two or more business roles.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Business-Layer.html#sec-Business-Interaction
has super-classes
BusinessLayerElement c, Interaction c

Business Interfacec back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#BusinessInterface

A business interface is a point of access where a business service is made available to the environment.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Business-Layer.html#sec-Business-Interface
has super-classes
BusinessLayerElement c, ExternalActiveStructureElement c

Business Objectc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#BusinessObject

A business object represents a concept used within a particular business domain.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Business-Layer.html#sec-Business-Object
has super-classes
BusinessLayerElement c, PassiveStructureElement c
has sub-classes
Contract c

Business Processc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#BusinessProcess

A business process represents a sequence of business behaviors that achieves a specific outcome such as a defined set of products or business services.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Business-Layer.html#sec-Business-Process
has super-classes
BusinessLayerElement c, InternalBehaviorElement c

Business Rolec back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#BusinessRole

A business role represents the responsibility for performing specific behavior, to which an actor can be assigned, or the part an actor plays in a particular action or event.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Business-Layer.html#sec-Business-Role
has super-classes
BusinessLayerElement c, InternalActiveStructureElement c

Business Servicec back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#BusinessService

A business service represents an explicitly defined exposed business behavior.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Business-Layer.html#sec-Business-Service
has super-classes
BusinessLayerElement c, ExternalBehaviorElement c

BusinessLayerElementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#BusinessLayerElement

has super-classes
CoreLayerElement c
has sub-classes
Business Actor c, Business Collaboration c, Business Event c, Business Function c, Business Interaction c, Business Interface c, Business Object c, Business Process c, Business Role c, Business Service c, Product c, Representation c

Capabilityc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Capability

A capability represents an ability that an active structure element, such as an organization, person, or system, possesses.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Strategy-Layer.html#sec-Capability
has super-classes
BehaviorElement c, StrategyLayerElement c

Collaborationc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Collaboration

An aggregate of two or more internal active structure elements working together.
has super-classes
InternalActiveStructureElement c
has sub-classes
Application Collaboration c, Business Collaboration c, Technology Collaboration c

Communication Networkc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#CommunicationNetwork

A communication network represents a set of structures that connects computer systems or other electronic devices for transmission, routing, and reception of data.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Technology-Layer.html#sec-Communication-Network
has super-classes
ActiveStructureElement c, TechnologyLayerElement c

CompositeElementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#CompositeElement

Composite elements consist of other concepts, possibly from multiple aspects or layers.
has super-classes
element c
has sub-classes
Grouping c, Location c, Plateau c, Product c

Compositionc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Composition

A composition relationship indicates that an element consists of one or more other elements. The contained element exists only within the context of the container.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Composition-Relationship
has super-classes
qualified relationship c
is in range of
qualified Composed Of op

Constraintc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Constraint

A constraint represents a factor that prevents or obstructs the realization of goals.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Motivation-Elements.html#sec-Constraint
has super-classes
Requirement c

Contractc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Contract

A contract represents a formal or informal specification of an agreement between a provider and a consumer that specifies the rights and obligations associated with a product.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Business-Layer.html#sec-Contract
has super-classes
Business Object c

CoreLayerElementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#CoreLayerElement

Core layers are Business, Application, and Technology (including Physical).
has super-classes
element c
has sub-classes
ApplicationLayerElement c, BusinessLayerElement c, PhysicalLayerElement c, TechnologyLayerElement c

Course of Actionc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#CourseOfAction

A course of action is an approach or plan for configuring some capabilities and resources of the enterprise, undertaken to achieve a goal.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Strategy-Layer.html#sec-Course-of-Action
has super-classes
BehaviorElement c, StrategyLayerElement c

Data Objectc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#DataObject

A data object represents data structured for automated processing.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Application-Layer.html#sec-Data-Object
has super-classes
ApplicationLayerElement c, PassiveStructureElement c

Deliverablec back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Deliverable

A deliverable represents a precisely-defined outcome of a work package.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Implementation-and-Migration-Layer.html#sec-Deliverable
has super-classes
ImplementationAndMigrationLayerElement c, PassiveStructureElement c

Devicec back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Device

A device is a physical IT resource upon which system software and artifacts may be stored or deployed for execution.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Technology-Layer.html#sec-Device
has super-classes
Node c

Distribution Networkc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#DistributionNetwork

A distribution network represents a physical network used to transport materials or energy.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Technology-Layer.html#sec-Distribution-Network
has super-classes
ActiveStructureElement c, PhysicalLayerElement c

Driverc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Driver

A driver represents an external or internal condition that motivates an organization to define its goals and implement the changes necessary to achieve them.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Motivation-Elements.html#sec-Driver
has super-classes
MotivationElement c

Equipmentc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Equipment

Equipment represents one or more physical machines, tools, or instruments that can create, use, store, move, or transform materials.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Technology-Layer.html#sec-Equipment
has super-classes
Node c, PhysicalLayerElement c

Eventc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Event

An event represents a state change.
has super-classes
BehaviorElement c
has sub-classes
Application Event c, Business Event c, Implementation Event c, Technology Event c

ExternalActiveStructureElementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#ExternalActiveStructureElement

An external active structure element (interface) represents a point of access.
has super-classes
ActiveStructureElement c
has sub-classes
Application Interface c, Business Interface c, Technology Interface c

ExternalBehaviorElementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#ExternalBehaviorElement

An external behavior element (service) represents explicitly defined exposed behavior.
has super-classes
BehaviorElement c
has sub-classes
Application Service c, Business Service c, Technology Service c

Facilityc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Facility

A facility represents a physical structure or environment.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Technology-Layer.html#sec-Facility
has super-classes
Node c, PhysicalLayerElement c

Flowc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Flow

A flow relationship indicates transfer from one element to another.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Flow-Relationship
has super-classes
qualified relationship c
is in range of
qualified Flows To op

Gapc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Gap

A gap represents a statement of difference between two plateaus.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Implementation-and-Migration-Layer.html#sec-Gap
has super-classes
ImplementationAndMigrationLayerElement c, PassiveStructureElement c

Goalc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Goal

A goal represents a high-level statement of intent, direction, or desired end state for an organization and its stakeholders.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Motivation-Elements.html#sec-Goal
has super-classes
MotivationElement c

Groupingc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Grouping

The grouping element aggregates or composes concepts that belong together based on some common characteristic.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Generic-Metamodel.html#sec-Grouping
has super-classes
CompositeElement c

Implementation Eventc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#ImplementationEvent

An implementation event is a behavior element that denotes a state change related to implementation or migration.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Implementation-and-Migration-Layer.html#sec-Implementation-Event
has super-classes
Event c, ImplementationAndMigrationLayerElement c

ImplementationAndMigrationLayerElementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#ImplementationAndMigrationLayerElement

has super-classes
element c
has sub-classes
Deliverable c, Gap c, Implementation Event c, Plateau c, Work Package c

Influencec back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Influence

An influence relationship indicates that an element affects the implementation or achievement of some motivation element. The influenceStrength property specifies the degree.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Influence-Relationship
has super-classes
qualified relationship c
is in domain of
Influence Strength dp
is in range of
qualified Influences op

Interactionc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Interaction

A unit of collective behavior performed by two or more active structure elements.
has super-classes
InternalBehaviorElement c
has sub-classes
Application Interaction c, Business Interaction c, Technology Interaction c

InternalActiveStructureElementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#InternalActiveStructureElement

An internal active structure element represents an entity capable of performing behavior.
has super-classes
ActiveStructureElement c
has sub-classes
Application Component c, Business Actor c, Business Role c, Collaboration c, Node c

InternalBehaviorElementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#InternalBehaviorElement

An internal behavior element represents a unit of activity.
has super-classes
BehaviorElement c
has sub-classes
Application Function c, Application Process c, Business Function c, Business Process c, Interaction c, Technology Function c, Technology Process c, Work Package c

Locationc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Location

A location is a place or position where structure elements can be located or behavior can be performed.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Generic-Metamodel.html#sec-Location
has super-classes
CompositeElement c

Materialc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Material

Material represents tangible physical matter or physical elements.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Technology-Layer.html#sec-Material
has super-classes
PassiveStructureElement c, PhysicalLayerElement c

Meaningc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Meaning

Meaning represents the knowledge or expertise present in, or the interpretation given to, a core element in a particular context.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Motivation-Elements.html#sec-Meaning
has super-classes
MotivationElement c

MotivationElementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#MotivationElement

A motivation element represents the context of or reason behind the architecture.
has super-classes
element c
has sub-classes
Assessment c, Driver c, Goal c, Meaning c, Outcome c, Principle c, Requirement c, Stakeholder c, Value c

Nodec back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Node

A node represents a computational or physical resource that hosts, manipulates, or interacts with other computational or physical resources.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Technology-Layer.html#sec-Node
has super-classes
InternalActiveStructureElement c, TechnologyLayerElement c
has sub-classes
Device c, Equipment c, Facility c, System Software c

Or Junctionc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Junction_Or

An or junction is used to connect relationships of the same type where one or more must be satisfied.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Junction
has super-classes
element c

Outcomec back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Outcome

An outcome represents an end result that has been achieved.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Motivation-Elements.html#sec-Outcome
has super-classes
MotivationElement c

PassiveStructureElementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#PassiveStructureElement

Passive structure elements can be accessed by behavior elements.
has super-classes
StructureElement c
has sub-classes
Artifact c, Business Object c, Data Object c, Deliverable c, Gap c, Material c, Representation c

Pathc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Path

A path represents a link between two or more nodes, through which these nodes can exchange data or material.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Technology-Layer.html#sec-Path
has super-classes
ActiveStructureElement c, TechnologyLayerElement c

PhysicalLayerElementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#PhysicalLayerElement

has super-classes
CoreLayerElement c
has sub-classes
Distribution Network c, Equipment c, Facility c, Material c

Plateauc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Plateau

A plateau represents a relatively stable state of the architecture that exists during a limited period of time.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Implementation-and-Migration-Layer.html#sec-Plateau
has super-classes
CompositeElement c, ImplementationAndMigrationLayerElement c

Principlec back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Principle

A principle represents a qualitative statement of intent that should be met by the architecture.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Motivation-Elements.html#sec-Principle
has super-classes
MotivationElement c

Productc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Product

A product represents a coherent collection of services and/or passive structure elements, accompanied by a contract/set of agreements, which is offered as a whole to customers.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Business-Layer.html#sec-Product
has super-classes
BusinessLayerElement c, CompositeElement c

Realizationc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Realization

A realization relationship indicates that an entity plays a critical role in the creation, achievement, sustenance, or operation of a more abstract entity.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Realization-Relationship
has super-classes
qualified relationship c
is in range of
qualified Realizes op

Representationc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Representation

A representation represents a perceptible form of the information carried by a business object.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Business-Layer.html#sec-Representation
has super-classes
BusinessLayerElement c, PassiveStructureElement c

Requirementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Requirement

A requirement represents a statement of need that must be met by the architecture.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Motivation-Elements.html#sec-Requirement
has super-classes
MotivationElement c
has sub-classes
Constraint c

Resourcec back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Resource

A resource represents an asset owned or controlled by an individual or organization.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Strategy-Layer.html#sec-Resource
has super-classes
StrategyLayerElement c, StructureElement c

Servingc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Serving

A serving relationship indicates that an element provides its functionality to another element.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Serving-Relationship
has super-classes
qualified relationship c
is in range of
qualified Serves op

Specializationc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Specialization

A specialization relationship indicates that an element is a particular kind of another element.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Specialization-Relationship
has super-classes
qualified relationship c
is in range of
qualified Specializes op

Stakeholderc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Stakeholder

A stakeholder is the role of an individual, team, or organization (or classes thereof) that represents their interests in the outcome of the architecture.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Motivation-Elements.html#sec-Stakeholder
has super-classes
MotivationElement c

StrategyLayerElementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#StrategyLayerElement

has super-classes
element c
has sub-classes
Capability c, Course of Action c, Resource c, Value Stream c

StructureElementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#StructureElement

Abstract superclass for all structure elements.
has super-classes
element c
has sub-classes
ActiveStructureElement c, PassiveStructureElement c, Resource c

System Softwarec back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#SystemSoftware

System software represents software that provides or contributes to an environment for storing, executing, and using software or data deployed within it.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Technology-Layer.html#sec-System-Software
has super-classes
Node c

Technology Collaborationc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#TechnologyCollaboration

A technology collaboration represents an aggregate of two or more nodes that work together to perform collective technology behavior.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Technology-Layer.html#sec-Technology-Collaboration
has super-classes
Collaboration c, TechnologyLayerElement c

Technology Eventc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#TechnologyEvent

A technology event is a technology behavior element that denotes a state change.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Technology-Layer.html#sec-Technology-Event
has super-classes
Event c, TechnologyLayerElement c

Technology Functionc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#TechnologyFunction

A technology function represents a collection of technology behavior that can be performed by a node.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Technology-Layer.html#sec-Technology-Function
has super-classes
InternalBehaviorElement c, TechnologyLayerElement c

Technology Interactionc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#TechnologyInteraction

A technology interaction represents a unit of collective technology behavior performed by (a collaboration of) two or more nodes.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Technology-Layer.html#sec-Technology-Interaction
has super-classes
Interaction c, TechnologyLayerElement c

Technology Interfacec back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#TechnologyInterface

A technology interface represents a point of access where technology services offered by a node can be accessed.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Technology-Layer.html#sec-Technology-Interface
has super-classes
ExternalActiveStructureElement c, TechnologyLayerElement c

Technology Processc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#TechnologyProcess

A technology process represents a sequence of technology behaviors that achieves a specific outcome.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Technology-Layer.html#sec-Technology-Process
has super-classes
InternalBehaviorElement c, TechnologyLayerElement c

Technology Servicec back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#TechnologyService

A technology service represents an explicitly defined exposed technology behavior.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Technology-Layer.html#sec-Technology-Service
has super-classes
ExternalBehaviorElement c, TechnologyLayerElement c

TechnologyLayerElementc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#TechnologyLayerElement

has super-classes
CoreLayerElement c
has sub-classes
Artifact c, Communication Network c, Node c, Path c, Technology Collaboration c, Technology Event c, Technology Function c, Technology Interaction c, Technology Interface c, Technology Process c, Technology Service c

Triggeringc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Triggering

A triggering relationship indicates a temporal or causal relationship between elements.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Triggering-Relationship
has super-classes
qualified relationship c
is in range of
qualified Triggers op

Valuec back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#Value

Value represents the relative worth, utility, or importance of a core element or an outcome.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Motivation-Elements.html#sec-Value
has super-classes
MotivationElement c

Value Streamc back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#ValueStream

A value stream represents a sequence of activities that create an overall result for a customer, stakeholder, or end user.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Strategy-Layer.html#sec-Value-Stream
has super-classes
BehaviorElement c, StrategyLayerElement c

Work Packagec back to ToC or Class ToC

IRI: https://meta.linked.archi/archimate3/onto#WorkPackage

A work package represents a series of actions identified and designed to achieve specific results within specified time and resource constraints.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Implementation-and-Migration-Layer.html#sec-Work-Package
has super-classes
ImplementationAndMigrationLayerElement c, InternalBehaviorElement c

Object Properties

Accessesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#accesses

Indicates that a behavior element may access a business or data object.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Access-Relationship

Aggregatesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#aggregates

Indicates that an element combines one or more other elements.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Aggregation-Relationship

Assigned Toop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#assignedTo

Indicates the allocation of responsibility, performance of behavior, storage, or execution.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Assignment-Relationship

Associated Withop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#associatedWith

Indicates an unspecified relationship, or one that is not represented by another ArchiMate relationship.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Association-Relationship

Composed Ofop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#composedOf

Indicates that an element consists of one or more other elements.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Composition-Relationship

Flows Toop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#flowsTo

Indicates transfer from one element to another.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Flow-Relationship

Influencesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#influences

Indicates that an element affects the implementation or achievement of some motivation element.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Influence-Relationship

qualified Accessesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#qualifiedAccesses

Navigates from a source element to an Access qualified relationship resource. The Access resource carries the accessType (Read, Write, ReadWrite).
Example
ex:OrderProcess am:qualifiedAccesses ex:qr-006 .
ex:qr-006 a am:Access ;
    arch:source ex:OrderProcess ;
    arch:target ex:CustomerData ;
    am:accessType "ReadWrite" .
has range
Access c

qualified Aggregatesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#qualifiedAggregates

Navigates from a source element to an Aggregation qualified relationship resource.
Example
ex:Department1 am:qualifiedAggregates ex:qr-002 .
ex:qr-002 a am:Aggregation ;
    arch:source ex:Department1 ;
    arch:target ex:Team1 .
has range
Aggregation c

qualified Assigned Toop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#qualifiedAssignedTo

Navigates from a source element to an Assignment qualified relationship resource. Assignment links active structure elements with behavior they perform, or actors with roles they fulfill.
Example
ex:DevTeam am:qualifiedAssignedTo ex:qr-003 .
ex:qr-003 a am:Assignment ;
    arch:source ex:DevTeam ;
    arch:target ex:DeploymentProcess .
has range
Assignment c

qualified Associated Withop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#qualifiedAssociatedWith

Navigates from a source element to an Association qualified relationship resource. Association is the most generic relationship — used when no more specific type applies.
Example
ex:Stakeholder1 am:qualifiedAssociatedWith ex:qr-011 .
ex:qr-011 a am:Association ;
    arch:source ex:Stakeholder1 ;
    arch:target ex:Driver1 .
has range
Association c

qualified Composed Ofop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#qualifiedComposedOf

Navigates from a source element to a Composition qualified relationship resource. Use this to reach the full relationship object with metadata, provenance, and lifecycle state.
Example
ex:System1 am:qualifiedComposedOf ex:qr-001 .
ex:qr-001 a am:Composition ;
    arch:source ex:System1 ;
    arch:target ex:Module1 .
has range
Composition c

qualified Flows Toop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#qualifiedFlowsTo

Navigates from a source element to a Flow qualified relationship resource. Flow indicates transfer of information, goods, or money.
Example
ex:Invoicing am:qualifiedFlowsTo ex:qr-009 .
ex:qr-009 a am:Flow ;
    arch:source ex:Invoicing ;
    arch:target ex:Payment ;
    skos:prefLabel "Invoice data flow"@en .
has range
Flow c

qualified Influencesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#qualifiedInfluences

Navigates from a source element to an Influence qualified relationship resource. The Influence resource carries the influenceStrength (+, ++, -, --).
Example
ex:CostReduction am:qualifiedInfluences ex:qr-007 .
ex:qr-007 a am:Influence ;
    arch:source ex:CostReduction ;
    arch:target ex:Profitability ;
    am:influenceStrength "++" .
has range
Influence c

qualified Realizesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#qualifiedRealizes

Navigates from a source element to a Realization qualified relationship resource. Realization links a concrete element with a more abstract element it realizes.
Example
ex:PaymentSvc am:qualifiedRealizes ex:qr-004 .
ex:qr-004 a am:Realization ;
    arch:source ex:PaymentSvc ;
    arch:target ex:PaymentCapability .
has range
Realization c

qualified Servesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#qualifiedServes

Navigates from a source element to a Serving qualified relationship resource. Serving indicates that an element provides its functionality to another.
Example
ex:AppSvc1 am:qualifiedServes ex:qr-005 .
ex:qr-005 a am:Serving ;
    arch:source ex:AppSvc1 ;
    arch:target ex:BizProc1 ;
    rdf:reifies <<( ex:AppSvc1 am:serves ex:BizProc1 )>> ;
    prov:wasDerivedFrom ex:diagramEdge-81 .
has range
Serving c

qualified Specializesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#qualifiedSpecializes

Navigates from a source element to a Specialization qualified relationship resource. Specialization indicates that an element is a particular kind of another.
Example
ex:OnlineBanking am:qualifiedSpecializes ex:qr-010 .
ex:qr-010 a am:Specialization ;
    arch:source ex:OnlineBanking ;
    arch:target ex:BankingService .
has range
Specialization c

qualified Triggersop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#qualifiedTriggers

Navigates from a source element to a Triggering qualified relationship resource. Triggering indicates a temporal or causal dependency.
Example
ex:OrderReceived am:qualifiedTriggers ex:qr-008 .
ex:qr-008 a am:Triggering ;
    arch:source ex:OrderReceived ;
    arch:target ex:FulfillmentProcess .
has range
Triggering c

Realizesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#realizes

Indicates that an entity plays a critical role in the creation, achievement, sustenance, or operation of a more abstract entity.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Realization-Relationship

Servesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#serves

Indicates that an element provides its functionality to another element.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Serving-Relationship

Specializesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#specializes

Indicates that an element is a particular kind of another element.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Specialization-Relationship

Triggersop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/archimate3/onto#triggers

Indicates a temporal or causal relationship between elements.
Source
https://pubs.opengroup.org/architecture/archimate3-doc/ch-Relationships-and-Relationship-Connectors.html#sec-Triggering-Relationship

Data Properties

Access Typedp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/archimate3/onto#accessType

Specifies the type of access: read, write, read-write, or unspecified.
has domain
Access c
has range
string

Influence Strengthdp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/archimate3/onto#influenceStrength

Specifies the strength or sign of an influence (e.g., +, ++, -, --).
has domain
Influence c
has range
string

Annotation Properties

abstractap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/abstract

alt labelap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#altLabel

change noteap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#changeNote

citationap back to ToC or Annotation Property ToC

IRI: http://schema.org/citation

createdap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/created

creatorap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/creator

definitionap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#definition

descriptionap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/description

domain includesap back to ToC or Annotation Property ToC

IRI: https://meta.linked.archi/core#domainIncludes

exampleap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#example

history noteap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#historyNote

is abstract classap back to ToC or Annotation Property ToC

IRI: https://meta.linked.archi/core#isAbstractClass

issuedap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/issued

licenseap back to ToC or Annotation Property ToC

IRI: http://creativecommons.org/ns#license

modifiedap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/modified

pref labelap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#prefLabel

pref vis notationap back to ToC or Annotation Property ToC

IRI: https://meta.linked.archi/core#prefVisNotation

preferred namespace prefixap back to ToC or Annotation Property ToC

IRI: http://purl.org/vocab/vann/preferredNamespacePrefix

preferred namespace uriap back to ToC or Annotation Property ToC

IRI: http://purl.org/vocab/vann/preferredNamespaceUri

publisherap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/publisher

range includesap back to ToC or Annotation Property ToC

IRI: https://meta.linked.archi/core#rangeIncludes

scope noteap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#scopeNote

sourceap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/source

statusap back to ToC or Annotation Property ToC

IRI: http://purl.org/ontology/bibo/status

titleap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/title

unqualified formap back to ToC or Annotation Property ToC

IRI: https://meta.linked.archi/core#unqualifiedForm

was derived fromap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/ns/prov#wasDerivedFrom

Legend back to ToC

c: Classes
op: Object Properties
dp: Data Properties

Changes from last version

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.