@prefix owl:     <http://www.w3.org/2002/07/owl#> .
@prefix xsd:     <http://www.w3.org/2001/XMLSchema#> .
@prefix rdfs:    <http://www.w3.org/2000/01/rdf-schema#> .
@prefix rdf:     <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix dc:      <http://purl.org/dc/elements/1.1/> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix bibo:    <http://purl.org/ontology/bibo/> .
@prefix vann:    <http://purl.org/vocab/vann/> .
@prefix prov:    <http://www.w3.org/ns/prov#> .
@prefix cc:      <http://creativecommons.org/ns#> .
@prefix skos:    <http://www.w3.org/2004/02/skos/core#> .
@prefix schema:  <http://schema.org/> .

@prefix arch:    <https://meta.linked.archi/core#> .
@prefix :        <https://meta.linked.archi/leanix/onto#> .

#################################################################
# Ontology header – LeanIX Meta Model v4
#################################################################

<https://meta.linked.archi/leanix/onto#>
    a                             owl:Ontology ;
    cc:license                    <http://creativecommons.org/licenses/by/4.0/> ;
    vann:preferredNamespaceUri    "https://meta.linked.archi/leanix/onto#" ;
    vann:preferredNamespacePrefix "lmm" ;
    dc:title                      "Linked.Archi LeanIX Meta Model v4 Ontology"@en ;
    dc:description                '''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.'''@en ;
    dcterms:created               "2025-01-01"^^xsd:date ;
    dcterms:modified              "2026-04-12"^^xsd:date ;
    dc:publisher                  "Linked.Archi"@en,
                                  <https://linked.archi> ;
    dcterms:creator               "Kalin Maldzhanski"^^xsd:string ;
    bibo:status                   "draft" ;
    owl:versionIRI                <https://meta.linked.archi/leanix/onto/v4#> ;
    owl:versionInfo               "4.0.0"@en ;
    owl:priorVersion              <https://meta.linked.archi/leanix/v3-onto#> ;
    skos:changeNote
            "Meta Model v4 revises the set of fact sheet types: introduces Objective, Initiative, Business Context and Platform; replaces v3 User Group, Project, Process and Tech Platform; and adds subtypes for Application and Organization."@en ;
    skos:scopeNote
            '''This namespace (leanix/onto#) covers SAP LeanIX Meta Model v4 with 12 default
fact sheet types plus one optional type. LeanIX Meta Model v3 used a different set of
fact sheet types (User Group, Project, Tech Platform) and is represented separately at
leanix/v3-onto#. A future Meta Model v5 may introduce a separate namespace if the
fact sheet types change substantially.'''@en ;
    rdfs:seeAlso                  <https://help.sap.com/docs/leanix/ea/meta-model>,
                                  <https://help.sap.com/docs/leanix/ea/fact-sheets>,
                                  <https://help.sap.com/docs/leanix/ea/general-modeling-guidelines>
.

#################################################################
# Core abstract concept
#################################################################

:FactSheet
    a               owl:Class ;
    rdfs:subClassOf arch:Element ;
    skos:prefLabel  "Fact Sheet"@en ;
    skos:definition "Abstract supertype for all LeanIX fact sheet instances in Meta Model v4."@en ;
    skos:example    "Any Application, Business Capability or Platform fact sheet is also an instance of :FactSheet."@en ;
    skos:scopeNote  "Abstract supertype for all LeanIX Meta Model v4 fact sheet instances."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/fact-sheets>,
                    <https://help.sap.com/docs/leanix/ea/general-modeling-guidelines>
.

#################################################################
# Strategy & Transformation layer – new in v4
#################################################################

:Objective
    a               owl:Class ;
    rdfs:subClassOf :FactSheet ;
    skos:prefLabel  "Objective"@en ;
    skos:definition "Objectives capture the goals that your organization aims to achieve. These drive initiatives to improve business capabilities and transform the IT landscape."@en ;
    skos:example    "\"Reduce IT run cost by 20% by 2027\" modeled as an Objective."@en ;
    skos:changeNote
            "Introduced in Meta Model v4 as a dedicated fact sheet type for strategic objectives, linked to Capabilities, Initiatives, Organizations and Platforms."@en ;
    skos:scopeNote
            "Use Objective to represent business or IT outcomes (OKRs, strategic goals) that guide Initiatives and constrain architecture decisions."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/objective-modeling-guidelines>
.

:Initiative
    a               owl:Class ;
    rdfs:subClassOf :FactSheet ;
    skos:prefLabel  "Initiative"@en ;
    skos:definition "Initiatives capture the planned projects or programs within your organization that impact its enterprise architecture and are aimed at achieving specific goals or objectives."@en ;
    skos:example    "\"ERP Consolidation Program 2026–2028\" that rationalizes the finance application landscape."@en ;
    skos:changeNote
            "Replaces and generalizes the Project fact sheet type from Meta Model v3. Initiatives in v4 cover projects, programs, epics and other change efforts."@en ;
    skos:scopeNote
            "Use Initiative for work that realizes Objectives and drives changes in Capabilities, Applications, Platforms and IT Components."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/initiative-modeling-guidelines>
.

#################################################################
# Business Architecture layer – reworked User Group / Process / Product
#################################################################

:BusinessCapability
    a               owl:Class ;
    rdfs:subClassOf :FactSheet ;
    skos:prefLabel  "Business Capability"@en ;
    skos:definition "Business capabilities (also called domains) model what your applications do to support your business goals."@en ;
    skos:example    "Business capabilities like \"Customer Management\", \"Order Processing\" that model what applications do to support business goals."@en ;
    skos:scopeNote
            "Capabilities remain conceptually consistent with v3, but are more explicitly connected to Objectives, Initiatives, Platforms and Business Context elements."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/business-capability-modeling-guidelines>
.

:Organization
    a               owl:Class ;
    rdfs:subClassOf :FactSheet ;
    skos:prefLabel  "Organization"@en ;
    skos:definition "Organizations represent your organization's hierarchical business architecture, detailing departments and teams."@en ;
    skos:example    "Departments like \"Finance\", \"Sales EMEA\" or teams like \"IT Operations\" that represent hierarchical business architecture."@en ;
    skos:changeNote
            "Introduced in Meta Model v4 to replace the v3 User Group fact sheet type and provide clearer organizational modeling with subtypes (e.g. Business Unit, Location, Cost Center)."@en ;
    skos:scopeNote
            "Represents organizational structures that own, operate or consume Capabilities and Applications, such as business units, departments and locations."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/organization-modeling-guidelines>
.

:OrganizationUnit
    a               owl:Class ;
    rdfs:subClassOf :Organization ;
    skos:prefLabel  "Organization Unit"@en ;
    skos:definition "Subtype of Organization used for internal structures such as departments, teams or cost centers."@en ;
    skos:example    "\"Accounting Shared Services\" team within the Finance organization modeled as an OrganizationUnit."@en ;
    skos:scopeNote
            "Example subtype of Organization; adjust this list to your actual Organization subtypes in LeanIX v4."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/organization-modeling-guidelines>
.

:BusinessContext
    a               owl:Class ;
    rdfs:subClassOf :FactSheet ;
    skos:prefLabel  "Business Context"@en ;
    skos:definition "Business contexts capture the specific activities your organization performs to achieve its business goals."@en ;
    skos:example    "Activities like \"Customer Onboarding\", \"Order Fulfillment\" that your organization performs to achieve business goals."@en ;
    skos:changeNote
            "New fact sheet type in Meta Model v4 that groups previously separate fact sheet types such as Product, Value Stream and Process."@en ;
    skos:scopeNote
            "Use Business Context to represent contextual business elements (Products, Value Streams, Processes, etc.) that link Capabilities, Applications, Data Objects and Organizations."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/business-context-modeling-guidelines>
.

:Product
    a               owl:Class ;
    rdfs:subClassOf :BusinessContext ;
    skos:prefLabel  "Product"@en ;
    skos:definition "Market‑facing or internal product or service bundle that is offered to customers or users."@en ;
    skos:example    "\"Gold Credit Card\", \"Premium Current Account\" or \"Field Service Mobile App\" modeled as Products."@en ;
    skos:scopeNote
            "Business Product modeled as a subtype of Business Context in v4 instead of a top-level fact sheet type in v3."@en ;
    skos:changeNote "Moved under Business Context in v4 to simplify the meta model and reuse common relations."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/business-context-modeling-guidelines> ;
.


:ValueStream
    a               owl:Class ;
    rdfs:subClassOf :BusinessContext ;
    skos:prefLabel  "Value Stream"@en ;
    skos:definition "End‑to‑end sequence of stages that collectively create value for an internal or external customer."@en ;
    skos:example    "Value streams such as \"Lead to Cash\", \"Idea to Market\" or \"Acquire to Retire\"."@en ;
    skos:scopeNote  "Represents value streams; introduced or consolidated as a Business Context subtype in v4."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/business-context-modeling-guidelines> ;
.

:Process
    a               owl:Class ;
    rdfs:subClassOf :BusinessContext ;
    skos:prefLabel  "Process"@en ;
    skos:definition "Repeatable sequence of activities or tasks that realizes one or more value stream stages and capabilities."@en ;
    skos:example    "Processes such as \"Create Customer Invoice\", \"Approve Purchase Order\" or \"Handle Returns\"."@en ;
    skos:changeNote
            "In v3, Process was a top-level fact sheet type. In Meta Model v4 it becomes a subtype of Business Context, aligning with a simplified meta model and Signavio integration."@en ;
    skos:scopeNote
            "Use this class for business processes; it inherits relations defined for Business Context (e.g. to Capabilities, Applications, Data Objects)."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/business-context-modeling-guidelines> ;
.

#################################################################
# Application & Data Architecture layer – same concepts, more structure
#################################################################

:Application
    a               owl:Class ;
    rdfs:subClassOf :FactSheet ;
    skos:prefLabel  "Application"@en ;
    skos:definition "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."@en ;
    skos:example    "\"SAP S/4HANA Finance\" or \"Salesforce Sales Cloud\" represented as Application fact sheets."@en ;
    skos:changeNote
            "Meta Model v4 introduces subtypes (e.g. Business Application, Deployment, Microservice, AI Agent) to distinguish logical applications from deployments and services."@en ;
    skos:scopeNote
            "Use Application as the logical representation of software supporting Capabilities and Business Context; specialize with subtypes where needed."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/application-modeling-guidelines>
.

:BusinessApplication
    a               owl:Class ;
    rdfs:subClassOf :Application ;
    skos:prefLabel  "Business Application"@en ;
    skos:definition "Application subtype representing business‑facing applications used directly by end users in business processes."@en ;
    skos:example    "A \"CRM Core\" system used by sales representatives to manage opportunities."@en ;
    skos:scopeNote  "Subtype of Application representing business-facing application systems."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/application-modeling-guidelines>
.

:Deployment
    a               owl:Class ;
    rdfs:subClassOf :Application ;
    skos:prefLabel  "Deployment"@en ;
    skos:definition "Application subtype representing a concrete deployed instance or environment of an application, such as production or test."@en ;
    skos:example    "\"CRM Core – Production (EU)\" and \"CRM Core – Test\" modeled as Deployments of the same logical application."@en ;
    skos:scopeNote
            "Subtype of Application representing environment-specific deployments (instances) of applications."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/deployment-modeling-guidelines>
.

:Microservice
    a               owl:Class ;
    rdfs:subClassOf :Application ;
    skos:prefLabel  "Microservice"@en ;
    skos:definition "Application subtype representing a fine‑grained, independently deployable service that contributes to a larger application or platform."@en ;
    skos:example    "Microservices such as \"Pricing Service\", \"Customer Profile Service\" or \"Notification Service\" used by multiple channels."@en ;
    skos:scopeNote  "Subtype of Application for fine-grained services in a microservice architecture."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/microservice-modeling-guidelines>
.

:Interface
    a               owl:Class ;
    rdfs:subClassOf :FactSheet ;
    skos:prefLabel  "Interface"@en ;
    skos:definition "Interfaces are the connections between applications that illustrate how data exchange occurs."@en ;
    skos:example    "An \"Order export API\" interface between an e‑commerce front end and the ERP system."@en ;
    skos:changeNote
            "Semantic role remains similar to v3: models integrations and APIs between applications, now more tightly integrated with Application and Business Context modeling guidelines."@en ;
    skos:scopeNote
            "Represents APIs, message channels or other technical interfaces; used to connect provider and consumer Applications and relate to Data Objects."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/interface-modeling-guidelines>
.

:DataObject
    a               owl:Class ;
    rdfs:subClassOf :FactSheet ;
    skos:prefLabel  "Data Object"@en ;
    skos:definition "Data objects provide an overview of general data processed and exchanged by specific applications."@en ;
    skos:example    "General data like \"Customer Profile\", \"Invoice Data\" processed and exchanged by applications."@en ;
    skos:changeNote
            "Continues the v3 concept of logical data entities, with richer relations to Applications, Processes and Business Context in v4."@en ;
    skos:scopeNote
            "Use Data Object for logical data entities exchanged via Interfaces or used by Applications and Processes."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/data-object-modeling-guidelines>
.

#################################################################
# Technical Architecture layer – Tech Category & Platform changes
#################################################################

:ITComponent
    a               owl:Class ;
    rdfs:subClassOf :FactSheet ;
    skos:prefLabel  "IT Component"@en ;
    skos:definition "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."@en ;
    skos:example    "\"PostgreSQL 15\", \"Kubernetes cluster\", \"Azure Functions\" or \"Red Hat Enterprise Linux\" modeled as IT Components."@en ;
    skos:scopeNote
            "Technologies (software, hardware, cloud services) that support Applications and Platforms; largely compatible with the v3 notion."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/it-component-modeling-guidelines>
.

:TechCategory
    a               owl:Class ;
    rdfs:subClassOf :FactSheet ;
    skos:prefLabel  "Tech Category"@en ;
    skos:definition "Tech categories are used to group IT components into different categories of technology."@en ;
    skos:example    "Technology categories like \"Database\", \"Middleware\", \"Cloud Platform\" used to group IT components."@en ;
    skos:changeNote "Continues the v3 Tech Category concept; still used as a grouping of IT Components."@en ;
    skos:scopeNote  "Use Tech Category to classify IT Components (e.g. database, middleware, PaaS)."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/tech-category-modeling-guidelines>
.

:Platform
    a               owl:Class ;
    rdfs:subClassOf :FactSheet ;
    skos:prefLabel  "Platform"@en ;
    skos:definition "Platforms are groupings of business capabilities, applications, and technologies that provide common functionalities."@en ;
    skos:example    "Platforms like \"Customer Data Platform\" that group capabilities, applications and technologies providing common functionalities."@en ;
    skos:changeNote
            "New fact sheet type in Meta Model v4 replacing the v3 Tech Platform fact sheet with a broader concept that groups Capabilities, Applications and IT Components."@en ;
    skos:scopeNote
            "Use Platform to model composable platforms that aggregate business capabilities, applications and technologies delivering shared functionality."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/platform-modeling-guidelines>
.

:Provider
    a               owl:Class ;
    rdfs:subClassOf :FactSheet ;
    skos:prefLabel  "Provider"@en ;
    skos:definition "Providers are the companies or entities that supply IT solutions, services, or technologies to support your organization in achieving its objectives and operational efficiency."@en ;
    skos:example    "External providers such as \"SAP\", \"Salesforce\", \"Microsoft Azure\", or an internal \"Shared Services IT\" provider."@en ;
    skos:scopeNote
            "Vendors or external providers of Applications, Platforms and IT Components; conceptually similar to v3 Provider."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/provider-modeling-guidelines>
.

#################################################################
# Optional System fact sheet type (if enabled)
#################################################################

:System
    a               owl:Class ;
    rdfs:subClassOf :FactSheet ;
    skos:prefLabel  "System (optional)"@en ;
    skos:definition "Systems represent the technical environment underlying applications, such as a server or virtual machine with its operating system, database, runtime configurations, and more."@en ;
    skos:example    "\"SAP ERP Central System (ECC PROD)\" modeled as a System composed of several applications and technologies."@en ;
    skos:changeNote
            "Optional fact sheet type in Meta Model v4, used in some modeling guidelines to represent SAP or legacy systems; not part of the 12 default fact sheet types."@en ;
    skos:scopeNote
            "Enable and use System if you need an intermediate concept between Applications and technical infrastructure for specific ERP or legacy stacks."@en ;
    rdfs:seeAlso    <https://help.sap.com/docs/leanix/ea/system-modeling-guidelines>
.

# As with v3, you can now define relations (object properties) and
# additional v4-specific attributes on top of these classes as needed.


#################################################################
# Relationship Types
#################################################################

## supports — Application → BusinessCapability ─────────────────

:supports
    a                    owl:ObjectProperty ;
    skos:prefLabel       "Supports"@en ;
    skos:definition      "Application supports a business capability."@en ;
    arch:domainIncludes  :Application ;
    arch:rangeIncludes   :BusinessCapability ;
.

:Supporting
    a                    owl:Class ;
    rdfs:subClassOf      arch:QualifiedRelationship ;
    arch:unqualifiedForm :supports ;
    skos:prefLabel       "Supporting"@en ;
    skos:definition      "A supporting relationship from an application to a business capability."@en ;
    arch:domainIncludes  :Application ;
    arch:rangeIncludes   :BusinessCapability ;
.

:qualifiedSupports
    a                    owl:ObjectProperty ;
    rdfs:range           :Supporting ;
    arch:unqualifiedForm :supports ;
.

## requires — Application → ITComponent ────────────────────────

:requires
    a                    owl:ObjectProperty ;
    skos:prefLabel       "Requires"@en ;
    skos:definition      "Application requires an IT component."@en ;
    arch:domainIncludes  :Application ;
    arch:rangeIncludes   :ITComponent ;
.

:Requiring
    a                    owl:Class ;
    rdfs:subClassOf      arch:QualifiedRelationship ;
    arch:unqualifiedForm :requires ;
    skos:prefLabel       "Requiring"@en ;
    skos:definition      "A dependency relationship from an application to an IT component."@en ;
    arch:domainIncludes  :Application ;
    arch:rangeIncludes   :ITComponent ;
.

:qualifiedRequires
    a                    owl:ObjectProperty ;
    rdfs:range           :Requiring ;
    arch:unqualifiedForm :requires ;
.

## hasInterface — Application → Interface ──────────────────────

:hasInterface
    a                    owl:ObjectProperty ;
    skos:prefLabel       "Has Interface"@en ;
    skos:definition      "Application has an interface."@en ;
    arch:domainIncludes  :Application ;
    arch:rangeIncludes   :Interface ;
.

:InterfaceOwnership
    a                    owl:Class ;
    rdfs:subClassOf      arch:QualifiedRelationship ;
    arch:unqualifiedForm :hasInterface ;
    skos:prefLabel       "Interface Ownership"@en ;
    skos:definition      "An ownership relationship from an application to an interface."@en ;
    arch:domainIncludes  :Application ;
    arch:rangeIncludes   :Interface ;
.

:qualifiedHasInterface
    a                    owl:ObjectProperty ;
    rdfs:range           :InterfaceOwnership ;
    arch:unqualifiedForm :hasInterface ;
.

## usesData — Application → DataObject ─────────────────────────

:usesData
    a                    owl:ObjectProperty ;
    skos:prefLabel       "Uses Data"@en ;
    skos:definition      "Application uses or processes a data object."@en ;
    arch:domainIncludes  :Application ;
    arch:rangeIncludes   :DataObject ;
.

:DataUsage
    a                    owl:Class ;
    rdfs:subClassOf      arch:QualifiedRelationship ;
    arch:unqualifiedForm :usesData ;
    skos:prefLabel       "Data Usage"@en ;
    skos:definition      "A usage relationship from an application to a data object."@en ;
    arch:domainIncludes  :Application ;
    arch:rangeIncludes   :DataObject ;
.

:qualifiedUsesData
    a                    owl:ObjectProperty ;
    rdfs:range           :DataUsage ;
    arch:unqualifiedForm :usesData ;
.

## impacts — Initiative → Application ──────────────────────────

:impacts
    a                    owl:ObjectProperty ;
    skos:prefLabel       "Impacts"@en ;
    skos:definition      "Initiative impacts an application."@en ;
    arch:domainIncludes  :Initiative ;
    arch:rangeIncludes   :Application ;
.

:Impact
    a                    owl:Class ;
    rdfs:subClassOf      arch:QualifiedRelationship ;
    arch:unqualifiedForm :impacts ;
    skos:prefLabel       "Impact"@en ;
    skos:definition      "An impact relationship from an initiative to an application."@en ;
    arch:domainIncludes  :Initiative ;
    arch:rangeIncludes   :Application ;
.

:qualifiedImpacts
    a                    owl:ObjectProperty ;
    rdfs:range           :Impact ;
    arch:unqualifiedForm :impacts ;
.

## drives — Objective → Initiative ─────────────────────────────

:drives
    a                    owl:ObjectProperty ;
    skos:prefLabel       "Drives"@en ;
    skos:definition      "Objective drives an initiative."@en ;
    arch:domainIncludes  :Objective ;
    arch:rangeIncludes   :Initiative ;
.

:Driving
    a                    owl:Class ;
    rdfs:subClassOf      arch:QualifiedRelationship ;
    arch:unqualifiedForm :drives ;
    skos:prefLabel       "Driving"@en ;
    skos:definition      "A driving relationship from an objective to an initiative."@en ;
    arch:domainIncludes  :Objective ;
    arch:rangeIncludes   :Initiative ;
.

:qualifiedDrives
    a                    owl:ObjectProperty ;
    rdfs:range           :Driving ;
    arch:unqualifiedForm :drives ;
.

## usedBy — Organization → Application ─────────────────────────

:usedByOrg
    a                    owl:ObjectProperty ;
    skos:prefLabel       "Used by Organization"@en ;
    skos:definition      "Application is used by an organization."@en ;
    arch:domainIncludes  :Organization ;
    arch:rangeIncludes   :Application ;
.

:OrganizationalUsage
    a                    owl:Class ;
    rdfs:subClassOf      arch:QualifiedRelationship ;
    arch:unqualifiedForm :usedByOrg ;
    skos:prefLabel       "Organizational Usage"@en ;
    skos:definition      "A usage relationship from an organization to an application."@en ;
    arch:domainIncludes  :Organization ;
    arch:rangeIncludes   :Application ;
.

:qualifiedUsedByOrg
    a                    owl:ObjectProperty ;
    rdfs:range           :OrganizationalUsage ;
    arch:unqualifiedForm :usedByOrg ;
.

## providedBy — ITComponent → Provider ─────────────────────────

:providedBy
    a                    owl:ObjectProperty ;
    skos:prefLabel       "Provided By"@en ;
    skos:definition      "IT component is provided by a provider."@en ;
    arch:domainIncludes  :ITComponent ;
    arch:rangeIncludes   :Provider ;
.

:Provision
    a                    owl:Class ;
    rdfs:subClassOf      arch:QualifiedRelationship ;
    arch:unqualifiedForm :providedBy ;
    skos:prefLabel       "Provision"@en ;
    skos:definition      "A provision relationship from an IT component to a provider."@en ;
    arch:domainIncludes  :ITComponent ;
    arch:rangeIncludes   :Provider ;
.

:qualifiedProvidedBy
    a                    owl:ObjectProperty ;
    rdfs:range           :Provision ;
    arch:unqualifiedForm :providedBy ;
.

## categorizedBy — ITComponent → TechCategory ──────────────────

:categorizedBy
    a                    owl:ObjectProperty ;
    skos:prefLabel       "Categorized By"@en ;
    skos:definition      "IT component is categorized by a tech category."@en ;
    arch:domainIncludes  :ITComponent ;
    arch:rangeIncludes   :TechCategory ;
.

:Categorization
    a                    owl:Class ;
    rdfs:subClassOf      arch:QualifiedRelationship ;
    arch:unqualifiedForm :categorizedBy ;
    skos:prefLabel       "Categorization"@en ;
    skos:definition      "A categorization relationship from an IT component to a tech category."@en ;
    arch:domainIncludes  :ITComponent ;
    arch:rangeIncludes   :TechCategory ;
.

:qualifiedCategorizedBy
    a                    owl:ObjectProperty ;
    rdfs:range           :Categorization ;
    arch:unqualifiedForm :categorizedBy ;
.
