IT Service Management Ontology
type: Ontology
title: A dictionary for some IT service management subjects.
version info: $Id: itsmo.owl 204 2012-10-29 17:33:14Z e-artspace $
contributor: ITSMO Ontology is a project sponsored by E-Artspace Labs (http://www.e-artspace.com)
rights: IT Service Management Ontology is available under the Creative Commons Attribution 3.0 Unported license; see http://creativecommons.org/licenses/by/3.0/. In a nutshell, you are free to copy, distribute and transmit the work; to remix/adapt the work (e.g. to import the ontology and create specializations of its elements), as long as you attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work). You may not use this work for commercial purposes without written permission of the author. Proper Attribution: Simply include the statement "This work is based on the IT Service Management Ontology, developed by Enrico Fagnoni" and link back to http://ontology.it/itsmo/.
comment: IT Service Management Ontology (ITSMO) provides the vocabulary for annotating resources related to IT Service Management. ITSMO try to be consistent with 2011 ITIL glossary. ITIL® is a Registered Trade Mark, and a Registered Community Trade Mark of the Office of Government Commerce, and is Registered in the U.S. Patent and Trademark Office. Please make sure you are only using element identifiers in this namespace, e.g.http://ontology.it/itsmo/v1#ITService. There may be copies of the ontology file on the Web which can be retrieved from other locations, BUT THOSE LOCATIONS MUST NOT BE USED AS REFERENCES.
creator: Enrico Fagnoni
license: http://creativecommons.org/licenses/by/3.0/
subject: ITSM, ITIL, IT Service Management

Catalogue
type: Class
disjoint with: Template
disjoint with: Warranty
subclass of: Document
disjoint with: Plan
disjoint with: ServiceOption
disjoint with: Policy
comment: A complete list of items, typically one in alphabetical or other systematic order
disjoint with: Utility

Template
type: Class
disjoint with: ServiceOption
comment: A skeleton document or a document to be used as reference for editing another document.
disjoint with: Catalogue
disjoint with: Plan
disjoint with: Policy
disjoint with: Utility
disjoint with: Warranty
subclass of: Document

Warranty
type: Class
conforms to: English 2011 Glossary
comment: Assurance that a product or service will meet agreed requirements. This may be a formal agreement such as a service level agreement or contract, or it may be a marketing message or brand image. Warranty refers to the ability of a service to be available when needed, to provide the required capacity, and to provide the required reliability in terms of continuity and security. Warranty can be summarized as ‘how the service is delivered’, and can be used to determine whether a service is ‘fit for use’. The business value of an IT service is created by the combination of utility and warranty.
disjoint with: Policy
disjoint with: Template
disjoint with: Plan
disjoint with: ServiceOption
disjoint with: Catalogue
subclass of: Document
disjoint with: Utility

Document
type: Class
disjoint with: Building
disjoint with: RunnableResource
disjoint with: Identity
comment: Information in readable form. A document may be paper or electronic – for example, a policy statement, service level agreement, incident record or diagram of a computer room layout. Dublin Core vocabulary appy to objetc of thes class.
disjoint with: Hardware
disjoint with: SoftwarePackage
conforms to: English 2011 Glossary
subclass of: Configuration Item

Plan
type: Class
disjoint with: Template
subclass of: Document
disjoint with: ServiceOption
conforms to: English 2011 Glossary
disjoint with: Utility
disjoint with: Policy
comment: A detailed proposal that describes the activities and resources needed to achieve an objective – for example, a plan to implement a new IT service or process. ISO/IEC 20000 requires a plan for the management of each IT service management process.
disjoint with: Catalogue
disjoint with: Warranty

ServiceOption
type: Class
disjoint with: Template
conforms to: English 2011 Glossary
disjoint with: Utility
comment: A choice of utility and warranty offered to customers by a core service or service package.
disjoint with: Policy
disjoint with: Plan
disjoint with: Warranty
disjoint with: Catalogue
subclass of: Document

Policy
type: Class
disjoint with: Catalogue
disjoint with: Utility
subclass of: Document
disjoint with: ServiceOption
disjoint with: Warranty
disjoint with: Template
disjoint with: Plan
conforms to: English 2011 Glossary
comment: Formally documented management expectations and intentions. Policies are used to direct decisions, and to ensure consistent and appropriate development and implementation of processes, standards, roles, activities, IT infrastructure etc.

Utility
type: Class
disjoint with: Warranty
disjoint with: Template
disjoint with: Policy
subclass of: Document
comment: The functionality offered by a product or service to meet a particular need. Utility can be summarized as ‘what the service does’, and can be used to determine whether a service is able to meet its required outcomes, or is ‘fit for purpose’. The business value of an IT service is created by the combination of utility and warranty.
disjoint with: Plan
disjoint with: Catalogue
conforms to: English 2011 Glossary
disjoint with: ServiceOption

SoftwarePackage
type: Class
disjoint with: Document
disjoint with: Hardware
disjoint with: Identity
disjoint with: Building
disjoint with: RunnableResource
comment: A logical entity that identify a software release or a software feature set. For example: "VirtueMart 1.1.x", "Linux LTS 10.04" , "Windows 7 service pack 2", "Apache 2" . Sometime referenced only with "software".
subclass of: Configuration Item

Hardware
type: Class
disjoint with: SoftwarePackage
disjoint with: Document
disjoint with: Identity
disjoint with: Building
disjoint with: RunnableResource
subclass of: Configuration Item
comment: the physical part of a computer

Identity
type: Class
disjoint with: Document
conforms to: English 2011 Glossary
disjoint with: SoftwarePackage
disjoint with: Building
disjoint with: RunnableResource
subclass of: Configuration Item
disjoint with: Hardware
comment: A unique name that is used to identify a user, person or role. The identity is used to grant rights to that user, person or role. Example identities might be the username SmithJ or the role ‘change manager’.

Building
type: Class
comment: Any human-made structure used or intended for supporting or sheltering any use or continuous occupancy
disjoint with: SoftwarePackage
disjoint with: Document
disjoint with: Hardware
disjoint with: Identity
disjoint with: RunnableResource
subclass of: Configuration Item

RunnableResource
type: Class
subclass of: Restriction
  on property: hasPriority
  max cardinality: 1
subclass of: Restriction
  on property: hasDesign
  max cardinality: 1
disjoint with: Identity
subclass of: Restriction
  max cardinality: 1
  on property: hasOperationProcess
subclass of: Restriction
  on property: hasCriticality
  max cardinality: 1
subclass of: Configuration Item
disjoint with: Document
disjoint with: SoftwarePackage
disjoint with: Hardware
disjoint with: Building
comment: Configuration items that require an execution environment to go live.

Configuration Item
type: Class
disjoint with: QualitativeValue
disjoint with: LifeCycleStage
subclass of: Restriction
  max cardinality: 1
  on property: hasReferenceBaseline
disjoint with: Configuration
subclass of: Thing
subclass of: Restriction
  on property: hasStatus
  max cardinality: 1
disjoint with: Snapshot
disjoint with: Dependency
comment: any component or other service asset that needs to be managed in order to deliver an IT service. Information about each configuration item is recorded [at least] in a configuration record within the configuration management system and is maintained throughout its lifecycle by service asset and configuration management. Configuration items are under the control of change management. They typically include IT services, hardware, software, buildings, people and formal documentation such as process documentation and service level agreements. Note that tis definition is a bit extensive than ITIL one, because it allow a CI to be described in more than one configuration records.This make this definition compatible with semantic web architecture that allow metadata do be defined everywhere in the web. See ITSMO user manual for more info about this class.
disjoint with: ControlledConfiguration
conforms to: English 2011 Glossary

DataCenter
type: Class
subclass of: Building
comment: is a facility used to house computer systems and associated components>

RunTimeDependency
type: Class
disjoint with: StructuralDependency
comment: A time dependent dinamic dependency. For example there is a runtime dependency betwen proces A and ITservice B when A calls a REST service exposed by B.
subclass of: Dependency

StructuralDependency
type: Class
comment: describes a part/whole relationship between components. A strucural dependency is an included file, a paragrapg in a text, a library used by applcation an application etc. etc.
disjoint with: RunTimeDependency
subclass of: Dependency

Dependency
type: Class
subclass of: Restriction
  on property: hasDependentObject
  cardinality: 1
comment: The direct or indirect reliance of one Configuraiton Item on another. [ Note that the ITIL 2011 restrict the domain of this terms to Processes or activity, this definition is more general ]. This is a superclass for all types of dependency relastionship for a CI.
disjoint with: Configuration Item
subclass of: Restriction
  on property: hasDependencyDistance
  max cardinality: 1
conforms to: English 2011 Glossary
subclass of: Thing
disjoint with: Snapshot
subclass of: Restriction
  max cardinality: 1
  on property: hasDependencyStrength
disjoint with: Configuration
disjoint with: ControlledConfiguration
disjoint with: QualitativeValue
disjoint with: LifeCycleStage

Application
type: Class
conforms to: English 2011 Glossary
subclass of: SoftwarePackage
comment: Software that provides functions which are required by an IT service. Each application may be part of more than one IT service. An application runs on one or more servers or clients.
comment: Application should be executable and installable Software Package. For example a library is not an application but it is a Software Package. [Not ITIL definition]

ServiceScope
type: Class
subclass of: QualitativeValue
comment: The service Scope (busines or infrastructure)

QualitativeValue
type: Class
comment: This property share the same definition of gr:QualitativeValue. A qualitative value is a predefined value for a service characteristic. Examples: The Service is critical. Note: Value sets are supported by creating subclasses of this class. Ordinal relations between values (gr:greater, gr:lesser, ...) can be provided directly by GoodRelations after subclassing itsmo:QualitativeValue to gr:QualitativeValue
disjoint with: Configuration
disjoint with: LifeCycleStage
disjoint with: Snapshot
disjoint with: Dependency
disjoint with: Configuration Item
disjoint with: ControlledConfiguration

ControlledConfiguration
type: Class
disjoint with: QualitativeValue
disjoint with: Dependency
subclass of: Restriction
  on property: hasCMDB
  cardinality: 1
subclass of: Configuration
comment: A term used to describe configuration subjected to change management and stored in a configuration management database (CMDB). If you use a Version Control System as CMDB, this is could be the the name of a source tree. If you use a plain filesystem as CMDB, this is the pathname of a directory that contains a file structure. Could be thinked as a "versioned directory". This term is similar to ITILs: "configuration record".
disjoint with: LifeCycleStage
disjoint with: Configuration Item
disjoint with: Snapshot

hasCMDB
type: ObjectProperty
domain: ControlledConfiguration
range: Class
  union of: IT Service
  union of: System
comment: the related resource is a means to store configuration throughout their lifecycle for described resource. The configuration management system maintains one or more configuration management databases, and each database stores attributes of configuration items, and relationships with other configuration items.

Configuration
type: Class
disjoint with: LifeCycleStage
disjoint with: Snapshot
disjoint with: QualitativeValue
disjoint with: Dependency
disjoint with: Configuration Item
comment: A term that indicate a set of related phisical object with their metadata that are considered as a whole.

LifeCycleStage
type: Class
conforms to: English 2011 Glossary
disjoint with: ControlledConfiguration
disjoint with: Configuration Item
comment: A stage in the life of a configuration item. The lifecycle defines the categories for status and the status transitions that are permitted. For example: The lifecycle of an application includes requirements, design, build, deploy, operate, optimize. The expanded incident lifecycle includes detection, diagnosis, repair, recovery and restoration The lifecycle of a server may include: ordered, received, in test, live, disposed etc
disjoint with: Configuration
disjoint with: Snapshot
disjoint with: QualitativeValue
disjoint with: Dependency

Snapshot
type: Class
disjoint with: Configuration
disjoint with: LifeCycleStage
disjoint with: QualitativeValue
disjoint with: Dependency
disjoint with: Configuration Item
disjoint with: ControlledConfiguration
comment: A shapshot at a defined time frame for a configuration Item. Use dcterms:created to annotate the date of the snapshot.

Dependency Strength
type: Class
disjoint with: criticality
disjoint with: Process Priority
comment: A Strength level for a dependency
subclass of: QualitativeValue

criticality
type: Class
disjoint with: Dependency Strength
disjoint with: Process Priority
comment: A process Critcality
subclass of: QualitativeValue

Process Priority
type: Class
comment: A process priority
subclass of: QualitativeValue
disjoint with: criticality
disjoint with: Dependency Strength

hasReferenceBaseline
type: ObjectProperty
sub property of: hasBaseline
comment: the referenced resource is a baseline that officially represent the annotated Configuration Item. If not present you can assume the the actual configuration.

hasStatus
type: ObjectProperty
range: LifeCycleStage
comment: the referenced resource is a stage in the life cycle of the described resource.
sub property of: quantitativeServiceProperty

CustomerAgreementPortfolio
type: Class
subclass of: Catalogue
comment: A database or structured document used to manage service contracts or agreements between an IT service provider and its customers. Each IT service delivered to a customer should have a contract or other agreement that is listed in the customer agreement portfolio.
conforms to: English 2011 Glossary
disjoint with: CustomerPortfolio
disjoint with: ServicePortfolio

CustomerPortfolio
type: Class
disjoint with: CustomerAgreementPortfolio
disjoint with: ServicePortfolio
conforms to: English 2011 Glossary
subclass of: Catalogue
comment: A database or structured document used to record all customers of the IT service provider. The customer portfolio is the business relationship manager’s view of the customers who receive services from the IT service provider.>

ServicePortfolio
type: Class
conforms to: English 2011 Glossary
comment: The complete set of services that is managed by a service provider. The service portfolio is used to manage the entire lifecycle of all services, and includes three categories: service pipeline (proposed or in development), service catalogue (live or available for deployment), and retired services.
subclass of: Catalogue
disjoint with: CustomerPortfolio
disjoint with: CustomerAgreementPortfolio

ManagementProcess
type: Class
comment: Is a process of planning and controlling one or more of activities. Here are some examples: Configuration Management: the process responsible for ensuring that the assets required to deliver services are properly controlled, and that accurate and reliable information about those assets is available when and where it is needed. This information includes details of how the assets have been configured and the relationships betweens [ITIL glossary]. Project Management: the discipline of planning, organizing, securing, and managing resources to achieve specific goals. A project is a temporary endeavor with a defined beginning and end (usually time-constrained, and often constrained by funding or deliverables), undertaken to meet unique goals and objectives, typically to bring about beneficial change or added value[Wikipedia]. Change Management: the process responsible for controlling the lifecycle of all changes, enabling beneficial changes to be made with minimum disruption to IT services.[ITIL glossary]
subclass of: Process

Process
type: Class
conforms to: English 2011 Glossary
subclass of: RunnableResource
subclass of: Restriction
  max cardinality: 1
  on property: hasAccountable
comment: A structured set of activities designed to accomplish a specific objective. A process takes one or more defined inputs and turns them into defined outputs. It may include any of the roles, responsibilities, tools and management controls required to reliably deliver the outputs. A process may define policies, standards, guidelines, activities and work instructions if they are needed.

hasAccountable
type: ObjectProperty
comment: The one ultimately accountable for the correct and thorough completion of the process, and the one to whom Responsible is accountable. In other words, an Accountable must sign off (Approve) on work that Responsible provides. There must be only one Accountable specified for each process.
domain: Process

Baseline
type: Class
subclass of: Snapshot
conforms to: English 2011 Glossary
comment: A configuration baseline is a snapshot that is used as a reference point.

Operational Level Agreement
type: Class
subclass of: Agreement
comment: An Agreement between an IT Service Provider and another part of the same Organisation. An OLA supports the IT Service Provider's delivery of IT Services to Customers. The OLA defines the goods or Services to be provided and the responsibilities of both parties. For example there could be an OLA between the IT Service Provider and a procurement department to obtain hardware in agreed times, between the Service Desk and a Support Group to provide Incident Resolution in agreed times. See Service Level Agreement.
conforms to: English 2011 Glossary
disjoint with: Service Level Agreement

Agreement
type: Class
conforms to: English 2011 Glossary
comment: A document that describes a formal understanding between two or more parties. An agreement is not legally binding, unless it forms part of a contract.
subclass of: Warranty

Service Level Agreement
type: Class
conforms to: English 2011 Glossary
subclass of: Agreement
comment: An Agreement between an IT Service Provider and a Customer. The SLA describes the IT Service, documents Service Level Targets, and specifies the responsibilities of the IT Service Provider and the Customer. A single SLA may cover multiple IT Services or multiple Customers. See Operational Level Agreement.
disjoint with: Operational Level Agreement

System
type: Class
conforms to: English 2011 Glossary
subclass of: RunnableResource
comment: A number of related things that work together to achieve an overall Objective. For example:computer System including hardware, software and Applications, a management System, including multiple Processes that are planned and managed together. For example a Quality Management System, a Database Management System or Operating System that includes many software modules that are designed to perform a set of related Functions.

hasDependentObject
type: ObjectProperty
comment: The subject of the statement depends fro, the referenced resource.
domain: Dependency

hasDependencyDistance
type: DatatypeProperty
sub property of: datatypeDependencyProperty
range: positiveInteger
comment: States the distance of an indirect dependency. If this property does not exist the distance is unknown. The value means the number of dependency hops from the direct dependency source reference. A value of 1 means a direct dependancy. This should be a positive integer.
domain: Dependency

hasDependencyStrength
type: ObjectProperty
domain: Dependency
range: Dependency Strength
comment: The level of dependency. There are two level of predefined value: itsmo:strongDependancy and itsmo:weakDependancy. Other value can be defined.

IT Service
type: Class
comment: A service is a means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An IT is a service provided by an IT service provider. An IT service is made up of a combination of information technology, people and processes. A customer-facing IT service directly supports the business processes of one or more customers and its service level targets should be defined in a service level agreement. Other IT services, called supporting services, are not directly used by the business but are required by the service provider to deliver customer-facing services.
conforms to: English 2011 Glossary
subclass of: RunnableResource
subclass of: Restriction
  on property: hasProvider
  max cardinality: 1

hasProvider
type: ObjectProperty
comment: States The Service Provider that provides IT Services to Internal Customers or External Customers.
conforms to: English 2011 Glossary
domain: IT Service
sub property of: quantitativeServiceProperty

Project
type: Class
comment: A temporary organization, with people and other assets, that is required to achieve an objective or other outcome. Each project has a lifecycle that typically includes initiation, planning, execution, and closure. Projects are usually managed using a formal methodology such as PRojects IN Controlled Environments (PRINCE2) or the Project Management Body of Knowledge (PMBOK).
conforms to: English 2011 Glossary
subclass of: RunnableResource
subclass of: Restriction
  min cardinality: 1
  on property: hasProjectOwner

hasProjectOwner
type: ObjectProperty
range: Identity
domain: Project
comment: the reference resource is who owns the described respurce.

Life cycle
type: Class
comment: A set of related LifeCycleStage. Could be implementetd with a state machine.

hasPriority
type: ObjectProperty
domain: RunnableResource
sub property of: quantitativeServiceProperty
range: Process Priority
comment: Relative priority

hasDesign
type: ObjectProperty
sub property of: quantitativeServiceProperty
domain: RunnableResource
conforms to: English 2011 Glossary
comment: States process that identifies requirements and then defines a solution that is able to meet these requirements.
range: Process

hasOperationProcess
type: ObjectProperty
comment: States Day-to-day management proces of an IT service, system or other runnable item.
domain: RunnableResource
conforms to: English 2011 Glossary
range: Process
sub property of: quantitativeServiceProperty

hasCriticality
type: ObjectProperty
comment: Relative criticality
range: criticality
sub property of: quantitativeServiceProperty
domain: RunnableResource

ServiceCatalogue
type: Class
comment: A database or structured document with information about all live IT services, including those available for deployment. The service catalogue is part of the service portfolio and contains information about two types of IT service: customer-facing services that are visible to the business; and supporting services required by the service provider to deliver customer-facing services.
subclass of: ServicePortfolio
conforms to: English 2011 Glossary

uses
type: ObjectProperty
sub property of: quantitativeServiceProperty
domain: Configuration Item
comment: This object property is a shortcut for the original itsmo:hasDirectDependency property for the common case of having a runtime (itsmo:runtimeDependency) dependency with strong strength (itsmo:strongDependency) with another resource (totally or partially). Note that this property is NOT transitive because states a DIRECT dependency.
range: Configuration Item

quantitativeServiceProperty
type: ObjectProperty
comment: This class is a container to collect all property that are safely sub-classable to gr:quantitativeProductOrServiceProperties.

hasAgreement
type: ObjectProperty
comment: An contract or an agriment related to a service (Service level agreed, ola or other)
sub property of: quantitativeServiceProperty
domain: IT Service
range: Agreement

hasServiceScope
type: ObjectProperty
comment: This atribute state the service scope
range: ServiceScope
domain: IT Service

hasManagementProcess
type: ObjectProperty
sub property of: quantitativeServiceProperty
domain: Configuration Item
comment: the referernced resource is a process for managing the described project rference
range: ManagementProcess

hasCustomer
type: ObjectProperty
range: Identity
sub property of: quantitativeServiceProperty
domain: IT Service
comment: States the service Customer

hasTemplate
type: ObjectProperty
comment: states a document that contains a skeleton or that can be used as reference for editing.
domain: Document
range: Template

hasSLAPackage
type: ObjectProperty
comment: The reference resouce (or litteral) is a choice of utility and warranty offered to customers by a core service or service package.
domain: IT Service
sub property of: quantitativeServiceProperty
range: ServiceOption

hasSystemAdministrator
type: ObjectProperty
comment: the referenced resource is the owner of the the system
domain: System

hasPublishingProcess
type: ObjectProperty
domain: Document
comment: the referenced resource is a Process for publishing the described resource.
range: Process

hasParty
type: ObjectProperty
domain: Agreement
comment: One of the parties of an agreement

links
type: ObjectProperty
sub property of: uses
comment: This object property is a shortcut for the original itsmo:hasDirectDependency property for the common case of having a runtime (itsmo:runtimeDependency) dependency with weak strength (itsmo:strongDependency) with another resource (totally or partially). Note that this property is NOT transitive because states a DIRECT dependency. It is an uses properties but with a weak dependency strenght becouse the link can be broken without risk of destruction for describing resource.

the referenced resource is process for edititing described resource.
type: ObjectProperty
comment: hasEditingProcess
domain: Document
range: Process

hasBaseline
type: ObjectProperty
comment: A reference to a baseline of a configuration.
range: Baseline
sub property of: hasSnapshot

requires
type: ObjectProperty
comment: A related resource that is directly totally or partially included either physically or logically in the described resource. This property implies dcterms:hasPart This object property is a shortcut for the original itsmo:hasDirectDependency property for the common case of having a static structural (itsmo:structuralDependency) dependency with strong strength (itsmo:strongDependency). Note that this property is NOT transitive becouse it states a DIRECT dependency. See http://ontology.it/itsmo/v1/itsmo.html#dependency_relations for more info. N.B. The study of part-whole relations is a large field in its own right - "mereology" and "mereotopology" and has been the topic of many papers. Note that this property is quite different form gr:includes one (that has a more restricted domains). gr:includes could be thinked as a subclass of itsmo:includes
range: Configuration Item
domain: Configuration Item
sub property of: quantitativeServiceProperty

hasConsole
type: ObjectProperty
sub property of: quantitativeServiceProperty
domain: IT Service
range: IT Service
comment: The referenced service is an administrative console forr the annotate service

hasInformed
type: ObjectProperty
comment: Those who are kept up-to-date on progress, often only on completion of the task or deliverable; and with whom there is just one-way communication. [source Wikypedia Raci matrix]
domain: Process
range: Identity

hasProvisioningProcess
type: ObjectProperty
sub property of: quantitativeServiceProperty
range: Process
domain: Class
  union of: IT Service
  union of: System

hasConsulted
type: ObjectProperty
comment: Those whose opinions are sought, typically subject matter experts; and with whom there is two-way communication. [ source wikypedia RACI matrix]
domain: Process
range: Identity

hasDependency
type: ObjectProperty
range: Dependency
comment: This states that the subject resource depends (directly or indirectly) from referenced resource. This could be thinked as a pseudo transitive property. If hasDependency(A,B) and BhasDependency(B,C) then hasDepency(A,C). Note that this is not a standard OWL reasoning.

hasUtility
type: ObjectProperty
range: Utility
comment: The referenced resource is an utility for the annotated service or service option.
sub property of: quantitativeServiceProperty
domain: Class
  union of: ServiceOption
  union of: IT Service

hasWarranty
type: ObjectProperty
range: Warranty
comment: The referenced resource is a Warranty for the annotated service or Service Option.
domain: Class
  union of: ServiceOption
  union of: IT Service
sub property of: quantitativeServiceProperty

hasDeliverable
type: ObjectProperty
range: Configuration Item
comment: the reference resource is a planned output for the described resource
domain: Project

hasConfiguration
type: ObjectProperty
range: Configuration
comment: A resource in from which the described resource is derived. General practice suggests to use a Version Control System to manage configuration ad versioned directory. This practice minimize the need of baseline and helps to maintain a coherent history of Configuration Items Changes. ITIL impose using just one Controlled Configuration record per Configuration Item.
sub property of: quantitativeServiceProperty
domain: Configuration Item

hasSnapshot
type: ObjectProperty
domain: Configuration Item
comment: The reference resource is a snapshot of a configuration item.
sub property of: quantitativeServiceProperty
range: Snapshot

hasServiceDesignPackage
type: ObjectProperty
comment: the reference resource is a resource defining some aspects of an IT Service and its Requirements through each stage of its Lifecycle.
sub property of: quantitativeServiceProperty
domain: RunnableResource

hasResponsible
type: ObjectProperty
range: Identity
comment: Those who do the work to achieve a Process. There is typically one role with a participation type of Responsible, although others can be delegated to assist in the work required.
domain: Process

hasManagementPlan
type: ObjectProperty
domain: ManagementProcess
sub property of: quantitativeServiceProperty
range: Plan
comment: the reference resource is a plan document for the described resource.

directReportOf
type: ObjectProperty
domain: Identity
comment: The referenced resource is the head of the described resource. This is a shortcut for describing a strong structural dependency between two identities.
range: Identity

isShared
type: DatatypeProperty
domain: IT Service
sub property of: datatypeDependencyProperty
comment: The service is shared between many customers
range: boolean

agreementValidFrom
type: DatatypeProperty
comment: This property specifies the beginning of the validity of an agreement.
range: dateTime
domain: Agreement

hasConfigurationDump
type: DatatypeProperty
comment: identifies a dump of a configuration. This cold be an URI of a controlled configuration revision. an archive file or just a string that allow you how to identify such dump.
domain: Snapshot

hasLinkedDataDump
type: DatatypeProperty
domain: Snapshot
comment: states a set of metadata snapshot. This sholud be a string expressed in a formal RDF language like XML/RF or turtle. It is used to take a snapshot of the properties of a C.I. when it has mulltiple or uncontrolled configuration or any other sparse metadata definition. Think it as the output of a SPARQL DESCRIBE query to an end-point that contains metadata for configuration Item..
range: string

agreementValidThrough
type: DatatypeProperty
range: dateTime
domain: Agreement
comment: This property specifies the end of the validity of an agreement.

datatypeServiceProperty
type: DatatypeProperty
comment: This property is the super property for all pure datatype properties that can be used to describe a gr:ProductOrService.

low priority
type: Priority
comment: a low priority

low critical
type: Criticality
comment: a low criticality value

high critical
type: Criticality
comment: an high criticality value

InfrastructureService
type: ServiceScope
comment: An IT service that is not directly used by the business, but is required by the IT service provider to deliver IT Business Services (for example, a directory service or a backup service). Supporting services may also include IT services only used by the IT service provider. All live supporting services, including those available for deployment, are recorded in the service catalogue along with information about their relationships to Business Services and other CIs. ITIL 2011 call ths also "Supporting Service"
conforms to: English 2011 Glossary

weak Dependency
type: DependencyStrength
comment: If the resource is missing can degrade process performances or functions but the dependent process still exists.

strong dependency
type: DependencyStrength
comment: The resource is mandatory for the process execution.

mediumPriority
type: Priority
comment: a mediumPriority

medium critical
type: Criticality
comment: a medium criticality value

BusinessService
type: ServiceScope
conforms to: English 2011 Glossary
comment: An IT service that is visible to the customer. These are normally services that support the customer’s business processes and facilitate one or more outcomes desired by the customer. All live customer-facing services, including those available for deployment, are recorded in the service catalogue along with customer-visible information about deliverables, prices, contact points, ordering and request processes. Other information such as relationships to supporting services and other CIs will also be recorded for internal use by the IT service provider. ITIL 2011 calls this "customer-facing service" while use Business Service as a more general term ( ITIL Business Service could be also a non IT )

Retire
type: LifeCycleStage
comment: Permanent removal of a configuration item, from the live environment. Being retired is a stage in the lifecycle of many configuration items.

high priority
type: Priority
comment: an high priority