language en

Linked.Archi LeanIX Meta Model v4 Ontology

Release: 2025-01-01

Modified on: 2026-08-16
This version:
https://meta.linked.archi/leanix/onto/v4#
Previous version:
https://meta.linked.archi/leanix/v3/onto#
Revision:
4.0.0
Authors:
Kalin Maldzhanski
Publisher:
Linked.Archi
Imported Ontologies:
arch-processes#
core#
See also:
https://help.sap.com/docs/leanix/ea/fact-sheets
https://help.sap.com/docs/leanix/ea/general-modeling-guidelines
https://help.sap.com/docs/leanix/ea/meta-model
Download serialization:
JSON-LD RDF/XML N-Triples TTL
License:
http://creativecommons.org/licenses/by/4.0/
Visualization:
Visualize with WebVowl
Cite as:
Kalin Maldzhanski. Linked.Archi LeanIX Meta Model v4 Ontology. Revision: 4.0.0. Retrieved from: https://meta.linked.archi/leanix/onto/v4#
Provenance of this page
draft

Linked.Archi LeanIX Meta Model v4 Ontology: Overview back to ToC

This ontology has the following classes and properties.

Classes

Object Properties

Data Properties

Annotation Properties

Named Individuals

Linked.Archi LeanIX Meta Model v4 Ontology: Description back to ToC

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

Cross-reference for Linked.Archi LeanIX Meta Model v4 Ontology classes, object properties and data properties back to ToC

This section provides details for each class and property defined by Linked.Archi LeanIX Meta Model v4 Ontology.

Classes

Applicationc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Application

Applications are the software systems or programs that process or analyze business data to support business tasks, processes, or aspects of your organization's business model. They are the central entities in SAP LeanIX because they link business and IT.
Example
"SAP S/4HANA Finance" or "Salesforce Sales Cloud" represented as Application fact sheets.
has super-classes
Fact Sheet c
has sub-classes
Business Application c, Deployment c, Microservice c

Business Applicationc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#BusinessApplication

Application subtype representing business‑facing applications used directly by end users in business processes.
Example
A "CRM Core" system used by sales representatives to manage opportunities.
has super-classes
Application c

Business Capabilityc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#BusinessCapability

Business capabilities (also called domains) model what your applications do to support your business goals.
Example
Business capabilities like "Customer Management", "Order Processing" that model what applications do to support business goals.
has super-classes
Fact Sheet c

Business Contextc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#BusinessContext

Business contexts capture the specific activities your organization performs to achieve its business goals.
Example
Activities like "Customer Onboarding", "Order Fulfillment" that your organization performs to achieve business goals.
has super-classes
Fact Sheet c
has sub-classes
Process c, Product c, Value Stream c

Capability Targetingc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#CapabilityTargeting

A targeting relationship from an objective to the business capability it aims to improve.
editorial note
Term name is this ontology's — see :targetsCapability.
Source
https://help.sap.com/docs/leanix/ea/objective-modeling-guidelines
has super-classes
qualified relationship
is in range of
qualified targets capability op

Categorizationc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Categorization

A categorization relationship from an IT component to a tech category.
has super-classes
qualified relationship
is in range of
qualified categorized by op

Context Realizationc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#ContextRealization

A realization relationship from a business context to a business capability.
editorial note
Term name is this ontology's — see :contextRealizes.
Source
https://help.sap.com/docs/leanix/ea/business-context-modeling-guidelines
has super-classes
qualified relationship
is in range of
qualified context realizes op

Context Supportc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#ContextSupport

A supporting relationship from an application to a business context.
editorial note
Term name is this ontology's — see :supportsContext.
Source
https://help.sap.com/docs/leanix/ea/business-context-modeling-guidelines
has super-classes
qualified relationship
is in range of
qualified supports context op

Data Objectc back to ToC or Class ToC

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

Data objects provide an overview of general data processed and exchanged by specific applications.
Example
General data like "Customer Profile", "Invoice Data" processed and exchanged by applications.
has super-classes
Fact Sheet c

Data Usagec back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#DataUsage

A usage relationship from an application or an interface to a data object.
Source
https://help.sap.com/docs/leanix/ea/data-object-modeling-guidelines
has super-classes
qualified relationship
is in range of
qualified uses data op

Deploymentc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Deployment

Application subtype representing a concrete deployed instance or environment of an application, such as production or test.
Example
"CRM Core – Production (EU)" and "CRM Core – Test" modeled as Deployments of the same logical application.
has super-classes
Application c

Drivingc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Driving

A driving relationship from an objective to an initiative.
has super-classes
qualified relationship
is in range of
qualified drives op

Fact Sheetc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#FactSheet

Abstract supertype for all LeanIX fact sheet instances in Meta Model v4.
Example
Any Application, Business Capability or Platform fact sheet is also an instance of :FactSheet.
has super-classes
element
has sub-classes
Application c, Business Capability c, Business Context c, Data Object c, IT Component c, Initiative c, Interface c, Objective c, Organization c, Platform c, Provider c, System (optional) c, Tech Category c

Fact Sheet Hierarchyc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#FactSheetHierarchy

A hierarchical relationship from a parent fact sheet to a child fact sheet of the same type.
Source
https://help.sap.com/docs/leanix/ea/general-modeling-guidelines
has super-classes
qualified relationship
is in range of
qualified parent of op

Fact Sheet Statusc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#FactSheetStatus

The state of a fact sheet as a record in the workspace — whether it is live, archived, or in an inconsistent state.
Source
https://help.sap.com/docs/leanix/ea/fact-sheets
has members
Active ni, Archived ni, Broken ni

Impactc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Impact

An impact relationship from an initiative to an application or a platform.
Source
https://help.sap.com/docs/leanix/ea/initiative-modeling-guidelines
has super-classes
qualified relationship
is in range of
qualified impacts op

Initiativec back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Initiative

Initiatives capture the planned projects or programs within your organization that impact its enterprise architecture and are aimed at achieving specific goals or objectives.
Example
"ERP Consolidation Program 2026–2028" that rationalizes the finance application landscape.
has super-classes
Fact Sheet c

Interfacec back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Interface

Interfaces are the connections between applications that illustrate how data exchange occurs.
Example
An "Order export API" interface between an e‑commerce front end and the ERP system.
has super-classes
Fact Sheet c

Interface Consumptionc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#InterfaceConsumption

A consumption relationship from an application to an interface provided by another application.
Source
https://help.sap.com/docs/leanix/ea/interface-modeling-guidelines
has super-classes
qualified relationship
is in range of
qualified consumes interface op

Interface Ownershipc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#InterfaceOwnership

An ownership relationship from the application that provides an interface to that interface.
Source
https://help.sap.com/docs/leanix/ea/interface-modeling-guidelines
has super-classes
qualified relationship
is in range of
qualified has interface op

IT Componentc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#ITComponent

IT components represent the technology or services that your applications depend on. They can provide information on both development and operations. They are used to model operating costs as well as technological risks.
Example
"PostgreSQL 15", "Kubernetes cluster", "Azure Functions" or "Red Hat Enterprise Linux" modeled as IT Components.
has super-classes
Fact Sheet c

Lifecycle Phasec back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#LifecyclePhase

One dated phase of a fact sheet's lifecycle — a lifecycle stage together with the date the subject entered it.
Source
https://help.sap.com/docs/leanix/ea/lifecycle
Example
<…/element/app-1>
    a                     lmm:Application ;
    ap:atLifecycleStage   ap:Active ;                    # lifecycle.asString
    lmm:hasLifecyclePhase <…/element/app-1/phase/plan>,
                          <…/element/app-1/phase/active> .

<…/element/app-1/phase/active>
    a                   lmm:LifecyclePhase ;
    ap:atLifecycleStage ap:Active ;
    lmm:phaseStart      "2021-04-01"^^xsd:date .

Microservicec back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Microservice

Application subtype representing a fine‑grained, independently deployable service that contributes to a larger application or platform.
Example
Microservices such as "Pricing Service", "Customer Profile Service" or "Notification Service" used by multiple channels.
has super-classes
Application c

Objectivec back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Objective

Objectives capture the goals that your organization aims to achieve. These drive initiatives to improve business capabilities and transform the IT landscape.
Example
"Reduce IT run cost by 20% by 2027" modeled as an Objective.
has super-classes
Fact Sheet c

Organizationc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Organization

Organizations represent your organization's hierarchical business architecture, detailing departments and teams.
Example
Departments like "Finance", "Sales EMEA" or teams like "IT Operations" that represent hierarchical business architecture.
has super-classes
Fact Sheet c
has sub-classes
Organization Unit c

Organization Unitc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#OrganizationUnit

Subtype of Organization used for internal structures such as departments, teams or cost centers.
Example
"Accounting Shared Services" team within the Finance organization modeled as an OrganizationUnit.
has super-classes
Organization c

Organizational Usagec back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#OrganizationalUsage

A usage relationship from an organization to an application.
has super-classes
qualified relationship
is in range of
qualified used by org op

Platformc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Platform

Platforms are groupings of business capabilities, applications, and technologies that provide common functionalities.
Example
Platforms like "Customer Data Platform" that group capabilities, applications and technologies providing common functionalities.
has super-classes
Fact Sheet c

Platform Membershipc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#PlatformMembership

A membership relationship from a fact sheet to the platform that groups it.
editorial note
Term name is this ontology's — see :partOfPlatform.
Source
https://help.sap.com/docs/leanix/ea/platform-modeling-guidelines
has super-classes
qualified relationship
is in range of
qualified part of platform op

Processc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Process

Repeatable sequence of activities or tasks that realizes one or more value stream stages and capabilities.
Example
Processes such as "Create Customer Invoice", "Approve Purchase Order" or "Handle Returns".
has super-classes
Business Context c

Productc back to ToC or Class ToC

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

Market‑facing or internal product or service bundle that is offered to customers or users.
Example
"Gold Credit Card", "Premium Current Account" or "Field Service Mobile App" modeled as Products.
has super-classes
Business Context c

Providerc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Provider

Providers are the companies or entities that supply IT solutions, services, or technologies to support your organization in achieving its objectives and operational efficiency.
Example
External providers such as "SAP", "Salesforce", "Microsoft Azure", or an internal "Shared Services IT" provider.
has super-classes
Fact Sheet c

Provisionc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Provision

A provision relationship from an IT component to a provider.
has super-classes
qualified relationship
is in range of
qualified provided by op

Requiringc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Requiring

A dependency relationship from an application to an IT component.
has super-classes
qualified relationship
is in range of
qualified requires op

Subscriptionc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Subscription

A person's registered responsibility for a fact sheet, of a given subscription type and covering one or more roles.
Source
https://help.sap.com/docs/leanix/ea/fact-sheet-subscription

Subscription Typec back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#SubscriptionType

The level of responsibility a subscription carries: responsible, accountable, or observer.
Source
https://help.sap.com/docs/leanix/ea/fact-sheet-subscription
has members
Accountable ni, Observer ni, Responsible ni

Supportingc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Supporting

A supporting relationship from an application to a business capability.
has super-classes
qualified relationship
is in range of
qualified supports op

System (optional)c back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#System

Systems represent the technical environment underlying applications, such as a server or virtual machine with its operating system, database, runtime configurations, and more.
Example
"SAP ERP Central System (ECC PROD)" modeled as a System composed of several applications and technologies.
has super-classes
Fact Sheet c

System Compositionc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#SystemComposition

A composition relationship from a system to an application or IT component that constitutes it.
editorial note
Term name is this ontology's — see :composedOf.
Source
https://help.sap.com/docs/leanix/ea/system-modeling-guidelines
has super-classes
qualified relationship
is in range of
qualified composed of op

Tagc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#Tag

A LeanIX tag applied to a fact sheet, in the tag group that scopes it.
Source
https://help.sap.com/docs/leanix/ea/tags

Tech Categoryc back to ToC or Class ToC

IRI: https://meta.linked.archi/leanix/onto#TechCategory

Tech categories are used to group IT components into different categories of technology.
Example
Technology categories like "Database", "Middleware", "Cloud Platform" used to group IT components.
has super-classes
Fact Sheet c

Value Streamc back to ToC or Class ToC

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

End‑to‑end sequence of stages that collectively create value for an internal or external customer.
Example
Value streams such as "Lead to Cash", "Idea to Market" or "Acquire to Retire".
has super-classes
Business Context c

Object Properties

Categorized Byop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#categorizedBy

IT component is categorized by a tech category.

Composed Ofop back to ToC or Object Property ToC

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

System is composed of an application or an IT component.
editorial note
Term name is this ontology's. System's definition describes a system as composed of several applications and technologies without naming the relation. System is an optional fact sheet type, so a workspace may never export this.
Source
https://help.sap.com/docs/leanix/ea/system-modeling-guidelines

Consumes Interfaceop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#consumesInterface

Application consumes an interface provided by another application.
Source
https://help.sap.com/docs/leanix/ea/interface-modeling-guidelines

Context Realizesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#contextRealizes

Business context realizes a business capability.
editorial note
Term name is this ontology's. The business context modeling guidelines say a Business Context links Capabilities without naming the relation.
Source
https://help.sap.com/docs/leanix/ea/business-context-modeling-guidelines

Drivesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#drives

Objective drives an initiative.

Fact Sheet Statusop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#factSheetStatus

The state of the fact sheet as a record in the workspace.
Source
https://help.sap.com/docs/leanix/ea/fact-sheets

Has Interfaceop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#hasInterface

Application provides an interface.
Source
https://help.sap.com/docs/leanix/ea/interface-modeling-guidelines

Has Lifecycle Phaseop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#hasLifecyclePhase

Relates a fact sheet to one dated phase of its lifecycle.
Source
https://help.sap.com/docs/leanix/ea/lifecycle

Has Subscriptionop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#hasSubscription

Relates a fact sheet to a subscription registered against it.
Source
https://help.sap.com/docs/leanix/ea/fact-sheet-subscription

Has Tagop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#hasTag

Relates a fact sheet to a tag applied to it.
Source
https://help.sap.com/docs/leanix/ea/tags

Impactsop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#impacts

Initiative impacts an application or a platform.
Source
https://help.sap.com/docs/leanix/ea/initiative-modeling-guidelines

Parent Ofop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#parentOf

Fact sheet is the hierarchical parent of another fact sheet of the same type.
Source
https://help.sap.com/docs/leanix/ea/general-modeling-guidelines

Part Of Platformop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#partOfPlatform

Application, business capability or IT component is part of a platform.
editorial note
Term name is this ontology's. SAP's platform modeling guidelines describe a platform as a grouping of business capabilities, applications and technologies without naming the relation.
Source
https://help.sap.com/docs/leanix/ea/platform-modeling-guidelines

Provided Byop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#providedBy

IT component is provided by a provider.

qualified categorized byop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedCategorizedBy

has range
Categorization c

qualified composed ofop back to ToC or Object Property ToC

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

has range
System Composition c

qualified consumes interfaceop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedConsumesInterface

has range
Interface Consumption c

qualified context realizesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedContextRealizes

has range
Context Realization c

qualified drivesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedDrives

has range
Driving c

qualified has interfaceop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedHasInterface

has range
Interface Ownership c

qualified impactsop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedImpacts

has range
Impact c

qualified parent ofop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedParentOf

has range
Fact Sheet Hierarchy c

qualified part of platformop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedPartOfPlatform

has range
Platform Membership c

qualified provided byop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedProvidedBy

has range
Provision c

qualified requiresop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedRequires

has range
Requiring c

qualified supportsop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedSupports

has range
Supporting c

qualified supports contextop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedSupportsContext

has range
Context Support c

qualified targets capabilityop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedTargetsCapability

has range
Capability Targeting c

qualified used by orgop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedUsedByOrg

has range
Organizational Usage c

qualified uses dataop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#qualifiedUsesData

has range
Data Usage c

Requiresop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#requires

Application requires an IT component.

Subscriberop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#subscriber

The person the subscription belongs to.
Source
https://help.sap.com/docs/leanix/ea/fact-sheet-subscription

Subscription Typeop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#subscriptionType

The level of responsibility this subscription carries.
Source
https://help.sap.com/docs/leanix/ea/fact-sheet-subscription

Supportsop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#supports

Application supports a business capability.

Supports Contextop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#supportsContext

Application supports a business context — a process, product or value stream.
editorial note
Term name is this ontology's. The business context modeling guidelines say a Business Context links Applications without naming the relation.
Source
https://help.sap.com/docs/leanix/ea/business-context-modeling-guidelines

Targets Capabilityop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#targetsCapability

Objective targets improvement of a business capability.
editorial note
Term name is this ontology's. Objective's own definition says objectives drive initiatives to improve business capabilities, without naming the relation.
Source
https://help.sap.com/docs/leanix/ea/objective-modeling-guidelines

Used by Organizationop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#usedByOrg

Application is used by an organization.

Uses Dataop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/leanix/onto#usesData

Application or interface uses, processes or exchanges a data object.
Source
https://help.sap.com/docs/leanix/ea/data-object-modeling-guidelines

Data Properties

Completiondp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/leanix/onto#completion

Completion ratio between 0 and 1, computed by LeanIX from the weights assigned to the fields, subsections and sections of the fact sheet type.
Source
https://help.sap.com/docs/leanix/ea/fact-sheet-completeness
has range
decimal

Phase Startdp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/leanix/onto#phaseStart

The date the subject entered this lifecycle phase.
Source
https://help.sap.com/docs/leanix/ea/lifecycle
has range
date

Subscriber Emaildp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/leanix/onto#subscriberEmail

The email address LeanIX holds for the subscriber.
Source
https://help.sap.com/docs/leanix/ea/managing-fact-sheet-subscriptions
has range
string

Subscription Roledp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/leanix/onto#subscriptionRole

The name of a role the subscription covers, such as Application Owner or Technical Lead.
Source
https://help.sap.com/docs/leanix/ea/subscription-roles
has range
string

Tag Groupdp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/leanix/onto#tagGroup

The name of the tag group that scopes the tag.
Source
https://help.sap.com/docs/leanix/ea/tags
has range
string

Tag Namedp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/leanix/onto#tagName

The tag's name, as the workspace writes it.
Source
https://help.sap.com/docs/leanix/ea/tags
has range
string

Annotation Properties

change noteap back to ToC or Annotation Property ToC

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

notationap back to ToC or Annotation Property ToC

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

Named Individuals

Accountableni back to ToC or Named Individual ToC

IRI: https://meta.linked.archi/leanix/onto#Accountable

The subscriber who answers for the fact sheet and its data quality.
Source
https://help.sap.com/docs/leanix/ea/managing-fact-sheet-subscriptions
belongs to
Subscription Type c

Activeni back to ToC or Named Individual ToC

IRI: https://meta.linked.archi/leanix/onto#StatusActive

The fact sheet is live in the workspace and can be read and edited.
Source
https://help.sap.com/docs/leanix/ea/fact-sheets
belongs to
Fact Sheet Status c

Archivedni back to ToC or Named Individual ToC

IRI: https://meta.linked.archi/leanix/onto#StatusArchived

The fact sheet has been archived. It remains readable and reportable, but LeanIX refuses updates to it.
Source
https://help.sap.com/docs/leanix/ea/fact-sheets
belongs to
Fact Sheet Status c

Brokenni back to ToC or Named Individual ToC

IRI: https://meta.linked.archi/leanix/onto#StatusBroken

The fact sheet is in an inconsistent state, typically after a failed import or an interrupted change.
Source
https://help.sap.com/docs/leanix/ea/fact-sheets
belongs to
Fact Sheet Status c

Observerni back to ToC or Named Individual ToC

IRI: https://meta.linked.archi/leanix/onto#Observer

A subscriber who follows the fact sheet without responsibility for its data.
Source
https://help.sap.com/docs/leanix/ea/managing-fact-sheet-subscriptions
belongs to
Subscription Type c

Responsibleni back to ToC or Named Individual ToC

IRI: https://meta.linked.archi/leanix/onto#Responsible

The subscriber who keeps the fact sheet's data accurate and up to date — the subject-matter expert for it.
Source
https://help.sap.com/docs/leanix/ea/managing-fact-sheet-subscriptions
belongs to
Subscription Type c

Legend back to ToC

c: Classes
op: Object Properties
dp: Data Properties
ni: Named Individuals

Changes from last version

Classes

Added classes
Deleted classes

Object Properties

Added object properties

Data Properties

Added data properties

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.