language en

The NORIA Ontology

Release 2022-12-15

This version:
https://w3id.org/noria/ontology/noria-0.2
Previous version:
https://w3id.org/noria/ontology/noria-0.1
Revision:
v0.2
Issued on:
2022-05-10
Authors:
Lionel Tailhardat (https://orcid.org/0000-0001-5887-899X)
Raphaël Troncy (https://orcid.org/0000-0003-0457-1436)
Yoan Chabot (https://orcid.org/0000-0001-5639-1504)
Publisher:
https://www.orange.com/
Imported Ontologies:
ApplicationOntology
CoreOntology
DocumentOntology
LocationOntology
NotificationOntology
ObservableOntology
ResourceOntology
Download serialization:
JSON-LD RDF/XML N-Triples TTL
License:
https://spdx.org/licenses/BSD-4-Clause
Visualization:
Visualize with WebVowl
Cite as:
Lionel Tailhardat (https://orcid.org/0000-0001-5887-899X), Raphaël Troncy (https://orcid.org/0000-0003-0457-1436), Yoan Chabot (https://orcid.org/0000-0001-5639-1504). The NORIA Ontology. Revision: v0.2. Retrieved from: https://w3id.org/noria/ontology/noria-0.2
Incompatible with:
https://w3id.org/noria/ontology/noria-0.1
Provenance of this page
nonPeerReviewed

Abstract

The NORIA-O project is a data model for IT networks, events and operations information. The ontology is developed using web technologies (e.g. RDF, OWL, SKOS) and is intended as a structure for realizing an IT Service Management (ITSM) Knowledge Graph (KG) for Anomaly Detection (AD) and Risk Management applications. The model has been developed in collaboration with operational teams, and in connection with third parties linked vocabularies. Alignment with third parties vocabularies is implemented on a per class or per property basis when relevant (e.g. with `rdfs:subClassOf`, `owl:equivalentClass`). Directions for direct instanciation of these vocabularies are provided for cases where implementing a class/property alignment is redundant. Alignment holds for the following vocabulary releases: - [BBO](https://hal.archives-ouvertes.fr/hal-02365012/) 1.0.0 - [BOT](https://w3id.org/bot/) 0.3.2 - [DevOps-Infra](https://oeg-upm.github.io/devops-infra/) 1.0.0 - [FOLIO](https://github.com/IBCNServices/Folio-Ontology) 1.0.0 - [ORG](https://www.w3.org/TR/vocab-org/) 0.8 - [PEP](https://w3id.org/pep/) 1.1 - [SEAS](https://w3id.org/seas/) 1.1 - [SLOGERT](https://sepses.ifs.tuwien.ac.at/ns/log/index-en.html) 1.1.0 - [UCO](https://github.com/ucoProject/uco) Release-0.8.0

The NORIA Ontology: Overview back to ToC

This ontology has the following classes and properties.

Classes

Object Properties

Data Properties

Cross-reference for The NORIA Ontology classes, object properties and data properties back to ToC

This section provides details for each class and property defined by The NORIA Ontology.

Classes

ActionPostConditionc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/ActionPostCondition

Set of Post Conditions or Potential outcomes that the execution of some OperationPlan may satisfy/lead to/confirm/solve. From the *ChangeRequest* perspective this enables to declare what to observe in order to confirm that the Procedure reached its goal; from the *TroubleTicket* perspective this enables to capitalize on expectations and outcomes for a given Procedure.
Is defined by
https://en.wikipedia.org/wiki/Hoare_logic
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
Example
In an Incident Management context, the materialization to expect, such as:
- 'service restored',
- 'traffic down',
- 'Customer or a probe with that traffic coming up after some CLI command'.
has super-classes
procedural object
is in range of
operationPlanPostCondition op

ActionPreConditionc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/ActionPreCondition

Set of Pre Conditions or Hypothesis enabling/leading to the potential execution of some OperationPlan.
Is defined by
https://en.wikipedia.org/wiki/Hoare_logic
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
Example
In an Incident Management context: when in situation X, shut link may help
has super-classes
procedural object
is in range of
operationPlanPreCondition op

AnomalyPatternc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/AnomalyPattern

An abstract class for grouping observables and events that, when satisfied by the existence of some instance/value, represents the occurrence of a (complex) fault/failure mode.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
has super-classes
failure mode, procedural object

Applicationc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/Application

An abstract system based on data processing and presentation.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
stable
Example
- RLOGS: Centralization of real time logs.
- DMZ VoIP: shared management zone / platform for Voice over IP services.
has super-classes
FunctionalElement c, application, system
is in domain of
applicationBusinessImportance op, applicationFunctionalDomain dp, applicationFunctionalSubDomain dp, applicationModelIdentifier dp, applicationNumericalIdentifier dp, applicationShortIdentifier dp, applicationType op
is in range of
changeRequestImpact op, logOriginatingManagedObject op, logOriginatingManagementSystem op, resourceForApplication op, troubleTicketRelatedService op

ApplicationModulec back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/ApplicationModule

A specific and managed instance of an Application.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Example
- Development instance of the RLOGS (Centralization of real time logs) Application.
- B2B instance of the DMZ VoIP (shared management zone / platform for Voice over IP services) Application.
has super-classes
FunctionalElement c, system
is in domain of
applicationModuleHotlineEnabled dp, applicationModuleIdentifier dp, applicationModuleName dp, applicationModuleOf op, applicationModuleRelatedParty op, applicationModuleSlaLevel op, applicationModuleSlaLevelDate dp, applicationModuleStatus op
is in range of
changeRequestImpact op, troubleTicketRelatedService op

ChangeRequestc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/ChangeRequest

A Change Request represents a record used for reporting and managing change activities on services and resources. It is a key artefact to the Change Management process. Change Management process is to respond to the customer’s changing business requirements while maximizing value and reducing incidents, disruption and network. Alignment: - *DCMI*: from the DCMI Abstract Model perspective, a ChangeRequest is a described resource, hence DC terms apply: - changeRequestId <=> http://purl.org/dc/terms/identifier : Identifier of the ChangeRequest. - changeRequestCreationDateTime <=> http://purl.org/dc/terms/created : The Date and time on which the ChangeRequest was created in the system. - changeRequestLastUpdate <=> http://purl.org/dc/terms/modified : The date and time on which the ChangeRequest was last updated. - changeRequestDescription <=> http://purl.org/dc/terms/description : Extended description of the change to be made. - changeRequestNote <=> http://purl.org/dc/terms/hasPart : A list of customer or internal comments. - changeRequestAttachment <=> http://purl.org/dc/terms/hasPart : DocumentAttachment(s) that are associated to the ChangeRequest. - changeRequestDuration <=> http://purl.org/dc/terms/extent (optional) - changeRequestRelatedParty <=> http://purl.org/dc/terms/contributor : Party playing a role in the ChangeRequest, whether it be an unqualified role (i.e. direct usage of dcterms:contributor) or a qualified role (i.e. sub-properties such as noria:changeRequestInitiatorParty). - changeRequestCorrelatedNotifications <=> http://purl.org/dc/terms/relation : EventRecord(s) instances or identifiers that are considered to be correlated to this ChangeRequest. - *PEP*: a ChangeRequest is a context for (potentially) many *ChangeAction* to occur; hence it relates to a `pep:ProcedureExecutionContainer`. - *BBO*: a ChangeRequest is a DocumentResource in the sense that it is the result of the Change Management process and can be used as an input for another activity. From the BPMN 2.0 perspective, a ChangeRequest is a DataObject.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-classes
DynamicElement c, document resource, procedure execution container
is in domain of
changeRequestActorParty op, changeRequestActualEndTime dp, changeRequestActualStartTime dp, changeRequestCategory op, changeRequestChangeCause op, changeRequestImpact op, changeRequestInitiatorParty op, changeRequestIsRegulated dp, changeRequestOutageDuration dp, changeRequestPilotParty op, changeRequestPlannedEndTime dp, changeRequestPlannedStartTime dp, changeRequestSpecification op, changeRequestStatusCurrent op, changeRequestType op, documentExternalId dp, documentHRef dp, documentStatusHistory op
is disjoint with
TroubleTicket c

CUidc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/CorporateUserIdentifier

The Corporate User Identifier (CUid) is the unique identifier of a Person as a member of Organization (i.e. an Employee). It is also the main account of this Person for connecting to the organization's IT resources, including to its personal computer (PC). Alignment: - *FOAF*: - The `foaf:accountName` allows for asserting the login identifier of an instance of this class. - The `foaf:holdsAccount` property allows for relating an employee entity to an instance of this class. - *UCO*: - A CUid is equivalent to a `observable:UserAccount`. - The `observable:accountLogin` and `observable:accountIdentifier` can be used in parallel to `foaf:accountName` for asserting the the login identifier. - The Person (`foaf:Agent`) holding this CUid is also a `observable:Contact`.
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
stable
has super-classes
online account, user account

DocumentAttachmentc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/DocumentAttachment

A file attachment. Alignment: - *DCMI*: from the DCMI Abstract Model perspective, a DocumentAttachment is a described resource, hence DC terms apply: - troubleTicketAttachmentForTicket <=> http://purl.org/dc/terms/isPartOf : The TroubleTicket this file is part of. - changeRequestAttachment <=> http://purl.org/dc/terms/isPartOf : The TroubleTicket this file is part of. - *BBO*: a DocumentAttachment is a DocumentResource in the sense that it is the result of the Incident Management Process (IMP) or Change Management Process (CMP) and can be used as an input for another activity. From the BPMN 2.0 perspective, a DocumentAttachment is a DataObject.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
Example
Picture of broken device, scanning of a bill or charge, network diagram, operation plan, location map.
has super-classes
DynamicElement c, document resource

DynamicElementc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/DynamicElement

Abstract class for time-related entities and their potential chaining (a.k.a. *Dynamic facet*).
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
stable
Example
An alarm with happens_on or followed_by properties
has super-classes
ManagedElement c
has sub-classes
ChangeRequest c, DocumentAttachment c, EventRecord c, TroubleTicket c, TroubleTicketNote c
is in domain of
eventRelatedElement op, eventRelatedParty op

EventRecordc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/EventRecord

This managed object represents the information stored in the log as a result of receiving notifications or incoming event reports. In that sense it is an abstract object with basic properties (e.g. event type, logging time, provenance system, message) to interpret in the context of its properties and relationships. For example, an *EventRecord* instance `log1` originating from the managed resource `R1` and describing a network interface state change on the Resource is fetched from a syslog-ng platform `Mon1` (i.e. the originating management system). A related *EventRecord* instance `alarm1` with `noria:alarmSeverity = Critical` and originating managed resource `R1` is triggered by a Network Monitoring System `NMS1` (i.e. the originating management system) for presentation to the Technical Support Center. Considering possible combinations of properties' objects and values, a `noria:EventRecord` allows for describing: - both informational and alarm notifications (this rely on `skos:ConceptScheme` over the `dcterms:type` of the `noria:EventRecord`), - notifications that affect both the network infrastructure (e.g. network interface down), network applications/services (e.g. timeout, k-out-of-n) and the Operation Support System (OSS) itself (e.g. updating a `noria:TroubleTicketNote`), - notifications originating from both onboard signaling (e.g. [SNMP Trap](https://en.wikipedia.org/wiki/Simple_Network_Management_Protocol)), probes (e.g. [NIDS](https://en.wikipedia.org/wiki/Intrusion_detection_system)), the monitoring system (e.g. threshold overrun, business rules) and inference engines (e.g. NORIA-AD). Alignment: - *DCMI*: from the DCMI Abstract Model perspective, a EventRecord is a described resource, hence DC terms apply: - *logRecordId* <=> http://purl.org/dc/terms/identifier : Identifier of notification or log record, as defined by <https://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/x721.html#-logRecordId>. - *logInformation* <=> http://purl.org/dc/terms/description : Additional information describing the logged event, as defined by <https://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/x721.html#-additionalInformation>. - *logType* <=> http://purl.org/dc/terms/type : The Type of the Event (e.g. General Operation Alarm, State Change, etc.), as defined by the NORIA `kos/Notification/EventType` concept scheme. - *alarmCorrelatedNotifications* <=> http://purl.org/dc/terms/relation : EventRecord instances or identifiers that are considered to be correlated to this EventRecord, as defined by <https://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/x721.html#-correlatedNotifications>. - *alarmOwner* <=> http://purl.org/dc/terms/mediator : The Support team member who acknowledged an Alarm Event Record. - *alarmProbableCause* <=> http://purl.org/dc/terms/conformsTo : The asserted or inferred cause of the Alarm Event Record, as defined by the NORIA `kos/Notification/ProbableCause` and `kos/Notification/SecurityAlarmCause` concept schemes. Asserting the Alarm cause is equivalent to directly connecting the Alarm, as a fault (issue, incident) artefact, to some phenomenon interpretation. Inferring the Alarm cause is equivalent to guessing the phenomenon origin through Root Cause Analysis (RCA) or some probabilistic approach. - *BBO*: an EventRecord is a `BBO:DocumentResource` in the sense that it is the result of the Event Management process and can be used as an input for another activity. From the BPMN 2.0 perspective, an EventRecord is a `DataObject`. - *PEP*: an EventRecord is an artefact of the realization of a `pep:Procedure`, hence it is a specialization of a `pep:ProcedureExecution` for the NORIA context. - *SLOGERT*: an EventRecord is equivalent to a `log:Event`.
Is defined by
https://w3id.org/noria/ontology/NotificationOntology
https://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/x721.html#-eventLogRecord
https://www.itu.int/rec/T-REC-X.733-199202-I/
Term status
stable
Example
- A network router event with
  loggingTime=`2022-01-01T17:12:00,259Z` and
  logText=`LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0/1, changed state to up`.
- A configuration change event on network router with
  pep:hasCommand='no shutdown' and
  logText='SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36)'
  and logOriginatingManagedObject=<object/NE_R1>.
has super-classes
DynamicElement c, document resource, event, event record, procedure execution
is in domain of
alarmMitigatedBy op, alarmMonitoredAttribute op, alarmProposedRepairAction op, alarmSeverity op, logOriginatingAgent op, logOriginatingManagedObject op, logOriginatingManagementSystem op, logText dp, loggingTime dp
is in range of
documentStatusHistory op, troubleTicketTrigger op

FunctionalElementc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/FunctionalElement

Abstract class for services and broadcasting zones above the *Structural* facet (a.k.a. *Functional facet*).
Term status
stable
has super-classes
ManagedElement c
has sub-classes
Application c, ApplicationModule c, Service c
is in range of
eventRelatedElement op

Locusc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/Locus

A uniquely identified space for Resources within a given Room. Alignment: - *BOT*: - The relationship to the Locus of a Room is available with the `bot:containsZone` property. - Approximating the geographical coordinates of a Locus is feasible through transitive inference over the `bot:hasZeroPoint` of the parent `bot:Site` (considering the GeoNames database this would to a `(bot:Site)=[bot:hasZeroPoint]=>(gn:Feature)` path towards `wgs84_pos:lat` or `wgs84_pos:long` values). - *ORG*: Note that, at instanciation time, `bot:Site` entities may also be `org:Site` (see https://www.w3.org/TR/vocab-org/#org:Site) in order to allow for an Organization (including teams, persons, manufacturers) to be localized (e.g. see `org:basedAt`), and hence allow for intervention distance/time calculus or threat calculus with respect to a given Locus.
Is defined by
https://w3id.org/noria/ontology/LocationOntology
Term status
stable
Example
Ligne:L, Colonne:6, en Salle:SALLE STOCKAGE RESEAU 314.
Line:L, Column:6, in Room:Server room 314.
has super-classes
space
is in domain of
locusLine dp, locusLine dp
is in range of
locatedAtLocus op

ManagedElementc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/ManagedElement

Top abstract class of NORIA Cyber/Physical concepts for describing, managing and analyzing ICT systems.
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
stable
has super-classes
feature of interest
has sub-classes
DynamicElement c, FunctionalElement c, ProceduralElement c, StructuralElement c
is in domain of
elementManagedBy op

NetworkInterfacec back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/NetworkInterface

A Network Interface of some Resource (e.g. server, router, virtual routing and forwarding (VRF) instance), and of some type (e.g. physical, virtual). Usage notes: - The name of the Network Interface (aka. networkInterfaceName, such as `ge-0/0/0.3013` or `ae52.3028`) can be set with the `rdfs:label` property.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has super-classes
StructuralElement c, communication connection point, network interface
is in domain of
networkInterfaceAdministrativeStatus op, networkInterfaceConnects op, networkInterfaceDescription dp, networkInterfaceLaserRxHighPowerWarningThreshold dp, networkInterfaceLaserRxLowPowerWarningThreshold dp, networkInterfaceLaserRxOpticalPower dp, networkInterfaceLaserRxOpticalPowerAverage dp, networkInterfaceLaserTxOpticalPower dp, networkInterfaceOf op, networkInterfaceOperationalStatus op, networkInterfaceRoutingPriorityMetric dp, networkInterfaceType op

OperationPlanc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/OperationPlan

An abstract class representing a formal set of operations to be carried out in a standardized/controlled way.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
Example
A system upgrade procedure, a network traffic fail-over activation, the control method for qualifying some system fault.
has super-classes
control method, procedural object, procedure
is in domain of
operationPlanPostCondition op, operationPlanPreCondition op
is in range of
actionCorrelatedOperationPlan op

ProceduralElementc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/ProceduralElement

Abstract class for (predefined/computed) operational process (a.k.a. *Procedural facet*).
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
stable
Example
Incident diagnosis procedure, cyber attack scenario, network route fail-over algorithm
has super-classes
ManagedElement c

ProductModelc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/ProductModel

The Product Model of some Resource as per the Manufacturer's naming.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has super-classes
structural property
is in domain of
productManufacturedBy op
is in range of
resourceProductModel op

Propertyc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/Property

An abstract representation of qualifiable, quantifiable, observable or operable qualities of some Element.
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
unstable
has super-classes
property
has sub-classes
StructuralObservable c

Resourcec back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/Resource

General resource record of the Communication Device kind from the logistics park. It is a managed entity that can be either Physical or Virtual. Alignment: - *SEAS*: Whenever a Resource individual is an assembly of other resources (e.g. a server rack) or is part of an assembly (e.g. a server blade), the Resource individual can also be declared as a `seas:System` in order to benefit of the `seas:subSystemOf` relation. For example, Resources may be grouped in some `noria:Service` class for providing both an end-to-end analysis of the data path (i.e. Communication Devices + Connections) and an abstract object linked to some end user (e.g. Customer). - *BOT*: A `noria:Resource` is a sub-class of `bot:Element` for setting instances in the context of a physical environment (e.g. in a building). - *SLOGERT*: A `noria:Resource` is equivalent to a `log:Host`. - *UCO*: A `noria:Resource` is equivalent to an UCO's observable `Device`.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has super-classes
StructuralElement c, communication device, device, element, host, system
is in domain of
clusterController op, locatedAtLocus op, resourceForApplication op, resourceHostName dp, resourceInstallationDate dp, resourceLogisticId dp, resourceManagementIPAddress op, resourceProductModel op, resourceSerialNumber dp, resourceType op, resourceUsageState op, virtualServerStatus op
is in range of
changeRequestImpact op, clusterController op, logOriginatingManagedObject op, networkInterfaceOf op, networkLinkTerminationResource op, troubleTicketRelatedResource op

Roomc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/Room

A part of the physical world or a virtual world whose 3D spatial extent is bounded actually or theoretically, and provides for certain functions within the zone it is contained in. Alignment: - *BOT*: A Room is a specialization of a `bot:Space` for common sense understanding.
Is defined by
https://w3id.org/noria/ontology/LocationOntology
Term status
stable
Example
SALLE STOCKAGE RESEAU 314
Server room 314
has super-classes
space

Servicec back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/Service

Service is an abstract base class for defining the Service hierarchy, i.e. the composition of assets (a.k.a. asset chain, service function chain) for providing a end-to-end data path or processing for some specific Customer or purpose. Usage notes: - The `noria:Service` is loosely defined as per the way to group underpinning assets. The typical usage is to assert `noria:ApplicationModule` entities as `seas:subSystemOf` a given `noria:Service`. - The network topology related to a given `noria:Service` is inferred from the set of resources, network interfaces and network links included in each Application that is part of the Service. We remark here that, although deterministic, the data path granularity calculus for some communication session (e.g. a time-bounded IP/http query with its response) depends on the specificity of the resources included in `ApplicationModule` instances. For example, the resulting granularity for a "national IP backbone infrastructure" application instance will correspond to the [routing domain](https://en.wikipedia.org/wiki/Routing_domain). Alignment: - *SEAS*: A `noria:Service` allows for grouping components, hence it is a subclass of `seas:System`. - *DevOps-Infra*: - The `noria:Service` is a concrete instance of a set of deployment models, hence it relates to `devopsprod:ServiceInstance`. - A `noria:Service.serviceType(<kos/service/type/CustomerFacingService>)` relates to the `devopsprod:BusinessProductInstance` concept. - *tmforum*: - The `noria:Service` is equivalent to the `Service` object from the *[TMF 638 - Service Inventory](https://github.com/tmforum-apis/TMF638_ServiceInventory)* API. - Using the `noria:serviceType` relates to asserting the `CustomerFacingService` or `ResourceFacingService` Service subclasses notions of the *TMF 638 - Service Inventory* API (i.e. as either being possibly visible and usable by a Customer or not). - *IETF*: Assuming a group *Service Functions* (SFs), the `noria:Service` concept relates to the *Service Function Chain (SFC)* definition from the [RFC 7665: SFC Architecture](https://www.rfc-editor.org/rfc/rfc7665) (see also [ITU-T X.1045](https://handle.itu.int/11.1002/1000/14043) for complementary SFC definition).
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
unstable
Example
End-to-end data path for some specific customer
has super-classes
FunctionalElement c, system
is in domain of
serviceType op
is in range of
changeRequestImpact op, troubleTicketRelatedService op

StructuralElementc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/StructuralElement

Abstract class for physical/logical ICT systems's assets and relations (a.k.a. *Structural facet*).
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
stable
Example
router xxx, virtual machine yyy, link zzz entities; is_a, connected_to or part_of properties
has super-classes
ManagedElement c, system
has sub-classes
NetworkInterface c, NetworkLink c, Resource c
is in range of
eventRelatedElement op

StructuralObservablec back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/StructuralObservable

An abstract class for ICT systems's properties that should be defined as classes for extended description capability.
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
unstable
Example
Time context of the observable value
has super-classes
Property c

TroubleTicketc back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/TroubleTicket

A trouble ticket represents a record used for reporting and managing the resolution of resource problems. Main trouble ticket attributes are its description, severity, type, priority, related dates (created, target resolution, resolution, etc.), state and related information (change reason, change date), related parties (originator, owner, pilot), notes, trouble causes and impacts. Alignment: - *DCMI*: from the DCMI Abstract Model perspective, a TroubleTicket is a described resource, hence DC terms apply: - troubleTicketId <=> http://purl.org/dc/terms/identifier : Identifier of the trouble ticket. - troubleTicketCreationDateTime <=> http://purl.org/dc/terms/created : The Date on which the TroubleTicket was created in the ticketing system. - troubleTicketLastUpdate <=> http://purl.org/dc/terms/modified : The date and time that the TroubleTicket was last updated. - troubleTicketName <=> http://purl.org/dc/terms/title : Name of the TroubleTicket, typically a short description provided by the user that create the ticket or complementary data - troubleTicketDescription <=> http://purl.org/dc/terms/description : Extended description of the trouble or issue. - troubleTicketNote <=> http://purl.org/dc/terms/hasPart : The TroubleTicketNote(s) that are associated to the TroubleTicket. - troubleTicketAttachment <=> http://purl.org/dc/terms/hasPart : The DocumentAttachment(s) that are associated to the TroubleTicket. - troubleTicketRelationshipParentOf <=> http://purl.org/dc/terms/hasPart : The TroubleTicket(s) this ticket is parent of (TicketRelationship). - troubleTicketRelationshipChildOf <=> http://purl.org/dc/terms/isPartOf : The TroubleTicket this ticket is the child of (TicketRelationship). - troubleTicketDuration <=> http://purl.org/dc/terms/extent (optional) : The overall duration of the incident management process, typically in ISO 8601 duration format. Can be useful for computing Mean Time To Repair (MTTR) values for a given `problemCategory`. - troubleTicketCorrelatedNotifications <=> http://purl.org/dc/terms/relation : EventRecord(s) instances or identifiers that are considered to be correlated to this TroubleTicket/TroubleTicketNote. - *BBO*: a TroubleTicket is a DocumentResource in the sense that it is the result of the Incident Management process and can be used as an input for another activity. From the BPMN 2.0 perspective, a TroubleTicket is a DataObject. - *PEP*: a TroubleTicketNote is a context for (potentially) many *CorrectiveMaintenanceAction* to occur; hence it relates to a `pep:ProcedureExecutionContainer`, which in turns enable to track the corresponding `EventRecord` through the `ldp:member` property.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-classes
DynamicElement c, document resource, procedure execution container
is in domain of
documentExternalId dp, documentHRef dp, documentStatusHistory op, problemCategory op, problemResponsibility op, troubleTicketCategory op, troubleTicketCause dp, troubleTicketCharacteristic op, troubleTicketCommittedRestorationDateTime dp, troubleTicketCriticity op, troubleTicketDetectionDateTime dp, troubleTicketFreezeItem op, troubleTicketImpacts op, troubleTicketIsNotificationEnable dp, troubleTicketOrigin op, troubleTicketPartyIntervention op, troubleTicketPlannedRestorationDateTime dp, troubleTicketPriority op, troubleTicketRelatedParty op, troubleTicketRelatedResource op, troubleTicketRelatedService op, troubleTicketSeverity op, troubleTicketStatusCurrent op, troubleTicketSupervisionTool dp, troubleTicketTargetRestorationDateTime dp, troubleTicketTrigger op, troubleTicketType op, troubleTicketUrgency op
is disjoint with
ChangeRequest c

TroubleTicketNotec back to ToC or Class ToC

IRI: https://w3id.org/noria/ontology/TroubleTicketNote

A trouble ticket note represents a record used for reporting and information sharing during the incident management process for a given Trouble Ticket. Alignment: - *DCMI*: from the DCMI Abstract Model perspective, a TroubleTicketNote is a described resource, hence DC terms apply: - troubleTicketNoteDate <=> http://purl.org/dc/terms/created : The recording date of the TroubleTicketNote. - troubleTicketNoteAuthor <=> http://purl.org/dc/terms/creator : The Author of the TroubleTicketNote. - troubleTicketNoteText <=> http://purl.org/dc/terms/description : The content of the TroubleTicketNote. - troubleTicketNoteForTicket <=> http://purl.org/dc/terms/isPartOf : The TroubleTicket this note is part of. - troubleTicketNoteCorrelatedNotifications <=> http://purl.org/dc/terms/relation : EventRecord(s) instances or identifiers that are considered to be correlated to this TroubleTicketNote. - *BBO*: a TroubleTicketNote is a DocumentResource in the sense that it is the result of the Incident Management process and can be used as an input for another activity. From the BPMN 2.0 perspective, a TroubleTicketNote is a DataObject. - *PEP*: a TroubleTicketNote is a context for (potentially) many *CorrectiveMaintenanceAction* to occur; hence it relates to a `pep:ProcedureExecutionContainer`, which in turns enable to track the corresponding `EventRecord` through the `ldp:member` property.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
Example
We shut interface ge-0-0-1 of Router1 in order to force route on Router2.
2.6Gb traffic measured at 10:28.
Customer has confirmed that the service is restored.
has super-classes
DynamicElement c, document resource, procedure execution container
is in domain of
troubleTicketNoteCommentType op, troubleTicketNoteCorrelatedExecution op, troubleTicketNoteOperationType op

Object Properties

actionCorrelatedOperationPlanop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/actionCorrelatedOperationPlan

The Operation Plan (procedure) guiding the execution of the given Action.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
has super-properties
used procedure
has domain
change action
corrective maintenance action
has range
OperationPlan c

agentManagesResourceop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/agentManagesResource

The Network Element (IT Resource) the Agent is responsible of (supervises). Alignment: - *FOAF*: A team may be interested into following the state of some resources, hence this property is semantically akin to `foaf:topic_interest`.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has super-properties
topic interest
has domain
agent
is inverse of
resourceManagedBy op

agentPreferredContactMethodop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/agentPreferredContactMethod

The preferred contact method to reach the Agent (Team, Group, Employee).
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
stable
Example
Phone, e-mail
has domain
agent
has range
concept and (in scheme value agent contact method)

alarmMitigatedByop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/alarmMitigatedBy

The ProcedureExecutionContainer (i.e. the set of Procedure Execution(s)) that led to clear the alarm and/or solve the issue. This allows, for example, the timely reporting of changing conditions prevalent at the time of the alarm.
Is defined by
https://w3id.org/noria/ontology/NotificationOntology
Term status
stable
Example
ProcedureExecutionContainer(x)
    .ldp:member EventRecord(y)
        .hasCommand='ip address 10.1.5.1 255.255.255.0'
        .hasResult='SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36)'
has domain
EventRecord c
has range
procedure execution container

alarmMonitoredAttributeop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/alarmMonitoredAttribute

The Monitored attributes parameter, when present, defines one or more attributes of the managed object and their corresponding values at the time of the alarm. Managed object definers may specify the set of attributes which are of interest, if any. This allows, for example, the timely reporting of changing conditions prevalent at the time of the alarm.
Is defined by
https://w3id.org/noria/ontology/NotificationOntology
https://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/x721.html#-monitoredAttributes
https://www.itu.int/rec/T-REC-X.733-199202-I/
Term status
unstable
has domain
EventRecord c

alarmProposedRepairActionop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/alarmProposedRepairAction

This parameter, when present, is used if the cause is known and the system being managed can suggest one or more solutions. This parameter is a set of possibilities specified by the object class definer.
Is defined by
https://w3id.org/noria/ontology/NotificationOntology
https://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/x721.html#-proposedRepairActions
https://www.itu.int/rec/T-REC-X.733-199202-I/
Term status
stable
Example
Switch to standby equipment, retry to connect, replace media, etc.
has domain
EventRecord c
has range
procedure

alarmSeverityop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/alarmSeverity

Indication of how it is perceived that the capability of the managed object has been affected, or how serious are the service affecting conditions (including for security alarms).
Is defined by
https://w3id.org/noria/ontology/NotificationOntology
https://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/x721.html#-perceivedSeverity
https://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/x721.html#-securityAlarmSeverity
https://www.itu.int/rec/T-REC-X.733-199202-I/
Term status
stable
Example
Critical, Major, Minor, Warning.
has super-properties
has criticality, type
has domain
EventRecord c
has range
concept and (in scheme value perceived severity)

applicationBusinessImportanceop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/applicationBusinessImportance

The importance of the Application from the business impact perspective for risk assessment analysis and incident management prioritization.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
unstable
has domain
Application c
has range
concept and (in scheme value business importance)

applicationModuleAdministrationLeaderop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/applicationModuleAdministrationLeader

Administration leader.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
unstable
has super-properties
applicationModuleRelatedParty op
has range
agent

applicationModuleAdministrationTeamop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/applicationModuleAdministrationTeam

Administration team.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
unstable
has super-properties
applicationModuleRelatedParty op
has range
organizational unit

applicationModuleHotlineGroupop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/applicationModuleHotlineGroup

Hotline team.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
unstable
has super-properties
applicationModuleRelatedParty op
has range
organizational unit

applicationModuleOfop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/applicationModuleOf

A child/parent relationship between a specific and managed instance of an Application (i.e. an Application Module) and the Application.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
stable
has super-properties
sub system of
has domain
ApplicationModule c

applicationModuleRelatedPartyop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/applicationModuleRelatedParty

Generic property for linking a party playing a role in the management of the Application Module.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
unstable
has super-properties
elementManagedBy op
has sub-properties
applicationModuleAdministrationLeader op, applicationModuleAdministrationTeam op, applicationModuleHotlineGroup op, applicationModuleSupportLeader op, applicationModuleSupportTeam op
has domain
ApplicationModule c

applicationModuleSlaLevelop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/applicationModuleSlaLevel

SLA level.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
unstable
has domain
ApplicationModule c
has range
concept and (in scheme value sla level)

applicationModuleStatusop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/applicationModuleStatus

Status of the Application Module.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
unstable
Example
En Production
In Production
has domain
ApplicationModule c
has range
concept and (in scheme value status)

applicationModuleSupportGroupop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/applicationModuleSupportGroup

Level 1 support team.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
unstable
has range
organizational unit

applicationModuleSupportLeaderop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/applicationModuleSupportLeader

Support leader.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
unstable
has super-properties
applicationModuleRelatedParty op
has range
agent

applicationModuleSupportTeamop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/applicationModuleSupportTeam

Level 2 Support Team.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
unstable
has super-properties
applicationModuleRelatedParty op
has range
organizational unit

applicationTypeop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/applicationType

The type of the Application.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
stable
has super-properties
type
has domain
Application c
has range
concept and (in scheme value type)

changeRequestActorPartyop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/changeRequestActorParty

The actor of the Change Request.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-properties
change request related party, contributor
has domain
ChangeRequest c
has range
agent

changeRequestCategoryop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/changeRequestCategory

Nature of the Change Request
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
Example
Internal intervention, Third party intervention, Customer intervention, Change requested by customer
has super-properties
type
has domain
ChangeRequest c
has range
concept and (in scheme value category)

changeRequestChangeCauseop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/changeRequestChangeCause

Cause of (reason for) the Change Request.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
Example
Configuration, Preventative maintenance, Software upgrade, Network extension, etc.
has super-properties
type
has domain
ChangeRequest c
has range
concept and (in scheme value cause)

changeRequestImpactop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/changeRequestImpact

Set of physical/logical entities on which the Change Request is carried-out.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
Example
Resource(s), Application(s), Service(s)
has super-properties
eventRelatedElement op, relation
has domain
ChangeRequest c
has range
Application c
ApplicationModule c
Resource c
Service c

changeRequestInitiatorPartyop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/changeRequestInitiatorParty

The agent initiating the Change Request.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-properties
change request related party, contributor
has domain
ChangeRequest c
has range
agent

changeRequestPilotPartyop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/changeRequestPilotParty

The pilot of the Change Request.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-properties
change request related party, contributor
has domain
ChangeRequest c
has range
agent

changeRequestSpecificationop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/changeRequestSpecification

An item of the standard operation plan catalog for recurring activities.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
has super-properties
type
has domain
ChangeRequest c
has range
concept and (in scheme value specification)

changeRequestStatusCurrentop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/changeRequestStatusCurrent

The current status of the Change Request.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has domain
ChangeRequest c
has range
concept and (in scheme value status)

changeRequestTypeop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/changeRequestType

The type of the request describes the a priori impact and risk level of the Change Request.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-properties
type
has domain
ChangeRequest c
has range
concept and (in scheme value type)

clusterControllerop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/clusterController

Relates a Resource that is part of a cluster with the cluster controller.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
unstable
Example
Resource("cluster-01").clusterController("virtual-center-01")
has super-properties
sub system of
has domain
Resource c
has range
Resource c

documentStatusHistoryop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/documentStatusHistory

The status change history of the document as recorded by the system's logging feature.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
Example
EventRecord
    .loggingTime("2019-01-23T11:58:00Z")
    .logOriginatingManagementSystem(</object/APP_MyOSS>)
    .references(</document/TT_2019-01-23_Resource1>)
    .title("InProgress")
    .type </kos/Notification/EventType/stateChange>
has super-properties
references
has domain
ChangeRequest c
TroubleTicket c
has range
EventRecord c

elementManagedByop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/elementManagedBy

The Agent or Owner of the Managed Element. Alignment: - *ORG*: the *elementManagedBy* property can range an `org:Organization` or `org:OrganizationalUnit` entity as the ORG data model defines these class as subClassOf `foaf:Agent` (see [org:Organization](https://www.w3.org/TR/vocab-org/#org:Organization)).
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
stable
has sub-properties
applicationModuleRelatedParty op, resourceManagedBy op
has domain
ManagedElement c
has range
agent

elementPropertyop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/elementProperty

An abstract representation of a relationship between some Element instance and some Property instance.
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
unstable
has super-properties
has property
has sub-properties
structuralElementObservable op

eventRelatedElementop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/eventRelatedElement

The structural or functional element instance some event or time-dependant entity is related with.
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
unstable
has sub-properties
changeRequestImpact op, logOriginatingManagedObject op, logOriginatingManagementSystem op, troubleTicketRelatedResource op, troubleTicketRelatedService op
has domain
DynamicElement c
has range
FunctionalElement c
StructuralElement c

eventRelatedPartyop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/eventRelatedParty

Party playing a role (stakeholders) in the life cycle of a given event instance or time-dependant entity.
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
unstable
has sub-properties
logOriginatingAgent op, troubleTicketRelatedParty op
has domain
DynamicElement c

locatedAtLocusop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/locatedAtLocus

A uniquely identified space of the Resource within a given Room. Alignment: - *UCO*: This property enables linking a concrete `Resource` instance to some location, hence it relates to `observable:location`. - *BOT*: This property is akin to the inverse of `bot:hasElement`.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
unstable
Example
Ligne:L, Colonne:6, en Salle:SALLE STOCKAGE RESEAU 314.
Line: L, Column:6, in Room:Server room 314.
has super-properties
location
has domain
Resource c
has range
Locus c

logOriginatingAgentop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/logOriginatingAgent

The Agent at the origin of the Log record whenever it represents some action carried out on the ICT system. This includes information about the service user associated with the service request that caused a security alarm.
Is defined by
https://w3id.org/noria/ontology/NotificationOntology
https://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/x721.html#-serviceUser
https://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/x721.html#-sourceIndicator
Term status
stable
Example
A employee or maintenance bot that carried-out a change or corrective maintenance action. A service user that carried-out SQL Injection.
has super-properties
creator, eventRelatedParty op, made by, was attributed to
has domain
EventRecord c
has range
agent

logOriginatingManagedObjectop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/logOriginatingManagedObject

The Managed Object entity at the origin of the Log record. This includes information about the service provider associated with the service request that caused a security alarm.
Is defined by
https://w3id.org/noria/ontology/NotificationOntology
https://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/x721.html#-SecurityAlarmDetector
https://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/x721.html#-managedObjectInstance
https://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/x721.html#-serviceProvider
https://www.itu.int/rec/T-REC-X.733-199202-I/
Term status
stable
Example
A named Resource, Application, Security Alarm Detector, etc.
has super-properties
creator, eventRelatedElement op, happened at, has source host, made by, was attributed to
has domain
EventRecord c
has range
Application c
Resource c

logOriginatingManagementSystemop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/logOriginatingManagementSystem

The Management System that receives, processes and forwards the Log record.
Is defined by
https://w3id.org/noria/ontology/NotificationOntology
Term status
stable
Example
A named instance of Network Management System (NMS), Security Information and Event Monitoring system (SIEM), etc.
has super-properties
creator, eventRelatedElement op, was attributed to
has domain
EventRecord c
has range
Application c

networkInterfaceAdministrativeStatusop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/networkInterfaceAdministrativeStatus

The administrative status of the Network Interface.
Is defined by
https://w3id.org/noria/ontology/ObservableOntology
Term status
stable
Example
up, down
has super-properties
structuralElementObservable op
has domain
NetworkInterface c
has range
concept and (in scheme value administrative state)

networkInterfaceConnectsop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/networkInterfaceConnects

The Network Link the Network Interface is attached-to.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has super-properties
connects system at
has domain
NetworkInterface c
has range
NetworkLink c

networkInterfaceOfop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/networkInterfaceOf

The Resource the Network Interface is part-of.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has super-properties
connection point of
has domain
NetworkInterface c
has range
Resource c

networkInterfaceOperationalStatusop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/networkInterfaceOperationalStatus

The operational status of the Network Interface.
Is defined by
https://w3id.org/noria/ontology/ObservableOntology
Term status
stable
Example
up, down
has super-properties
structuralElementObservable op
has domain
NetworkInterface c
has range
concept and (in scheme value operational state)

networkInterfaceTypeop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/networkInterfaceType

The type of the Network Interface.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
unstable
Example
physical, subinterface, virtual
has domain
NetworkInterface c

networkLinkTerminationResourceop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/networkLinkTerminationResource

Link termination Resource, the Resource at some end fo the Network Link.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has super-properties
connects system
has domain
NetworkLink c
has range
Resource c

operationPlanPostConditionop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/operationPlanPostCondition

The ActionPostCondition to check/that would be observed whenever the OperationPlan is carried out. Alignment: - *PEP*: OperationPlan (Procedures) may be linked to some description of the output, hence `operationPlanPostCondition` is a kind of `pep:hasOutput`. - *BBO*: From the BPMN perspective, the `operationPlanPostCondition` is the description of what should be observed to after the realization of a given Task, hence it is a kind of `BBO:has_completionCondition`.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-properties
has completion condition, has output
has domain
OperationPlan c
has range
ActionPostCondition c

operationPlanPreConditionop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/operationPlanPreCondition

The ActionPreCondition to check/that would be checked whenever the OperationPlan will be executed/is executed. Alignment: - *PEP*: OperationPlan (Procedures) may be linked to some description of the input, hence `operationPlanPreCondition` is a kind of `pep:hasInput`. - *BBO*: From the BPMN perspective, the `operationPlanPreCondition` is the description of what may activate the realization of a given Task, hence it is a kind of `BBO:has_activationCondition`.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-properties
has activation condition, has input
has domain
OperationPlan c
has range
ActionPreCondition c

problemCategoryop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/problemCategory

The *final* nature (for product ticket class) or technical impact (for resource ticket class) of the incident category of any Trouble Ticket or Incident Ticket.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
Example
Isolated customer site, Total breakdown, Working backup, Downgrading equipment, Inaccessible destination, etc.
has super-properties
type
has domain
TroubleTicket c
has range
concept and (in scheme value trouble category)

problemResponsibilityop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/problemResponsibility

The *final* area of responsibility identified for the incident.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
Example
Customer, Managed access equipment on customer's premises, Managed backbone networks, Managed specific networks, Contract application-hosting services, Ill-defined, etc.
has super-properties
type
has domain
TroubleTicket c
has range
concept and (in scheme value problem responsibility)

productManufacturedByop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/productManufacturedBy

The Manufacturer of the Product Model.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has domain
ProductModel c
has range
organization

resourceForApplicationop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/resourceForApplication

The Application this Resource is contributing to, whatever the Application type.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
Example
Corporate Internet access Infrastructure, Clock synchronization Service
has super-properties
sub system of
has domain
Resource c
has range
Application c

resourceManagedByop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/resourceManagedBy

The Support team or Owner of the Network Element (IT Resource).
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
Example
- Resource("DNS server").resourceManagedBy("DNS admin team")
- NetworkLink("WAN Paris-Papeete").resourceManagedBy("International backbone support team")
has super-properties
elementManagedBy op
is inverse of
agentManagesResource op

resourceManagementIPAddressop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/resourceManagementIPAddress

Specifies the IP address for remote management of the Resource, if relevant.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
unstable
Example
- IPv4: 192.168.1.25.
- IPv6: 2001:0db8:0000:0000:0000:8a2e:0370:7334
has super-properties
ip address
has domain
Resource c

resourceProductModelop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/resourceProductModel

The product model of the Resource.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has domain
Resource c
has range
ProductModel c

resourceTypeop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/resourceType

The type of the Network Element Resource.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has domain
Resource c
has range
concept and (in scheme value type)

resourceUsageStateop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/resourceUsageState

The production state of the Resource.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has domain
Resource c
has range
concept and (in scheme value lifecycle state)

serviceTypeop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/serviceType

The type of the Service.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
unstable
has super-properties
type
has domain
Service c
has range
concept and (in scheme value type)

structuralElementObservableop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/structuralElementObservable

An abstract representation of a relationship between some StructuralElement instance and some StructuralObservable instance.
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
unstable
has super-properties
elementProperty op
has sub-properties
networkInterfaceAdministrativeStatus op, networkInterfaceOperationalStatus op, virtualServerStatus op

structuralObservableOfop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/structuralObservableOf

Relates some `StructuralObservable` instance to some `StructuralElement` instance.
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
unstable
is inverse of
structural element property

troubleTicketCategoryop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketCategory

The *initial* nature (for product ticket class) or technical impact (for resource ticket class) of the incident category of any Trouble Ticket or Incident Ticket.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
Example
Isolated customer site, Total breakdown, Working backup, Downgrading equipment, Inaccessible destination, etc.
has super-properties
type
has domain
TroubleTicket c
has range
concept and (in scheme value trouble category)

troubleTicketCharacteristicop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketCharacteristic

A list of Characteristics of the ticket (TroubleTicketCharacteristic [*]). The Trouble ticket specific characteristics
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
has domain
TroubleTicket c

troubleTicketCriticityop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketCriticity

The ticket criticity from the customer impact perspective.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
Example
Interrupted service, Corrupted service, Working backup, etc.
has super-properties
type
has domain
TroubleTicket c
has range
concept and (in scheme value category)

troubleTicketFreezeItemop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketFreezeItem

The ticket freeze period history.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
Example
A list of `noria:EventRecord` specifically describing the freeze periods for the given `noria:TroubleTicket`.
has domain
TroubleTicket c

troubleTicketImpactsop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketImpacts

A list of resources or services (applications) impacted by the trouble.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
Example
TroubleTicket.troubleTicketImpacts({Application [*], Resource [*]})
has super-properties
relation
has domain
TroubleTicket c

troubleTicketNoteCommentTypeop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketNoteCommentType

The comment provenance type and/or disclosure rules family.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
Example
Customer, Group, Internal, System, etc.
has super-properties
type
has domain
TroubleTicketNote c
has range
concept and (in scheme value comment type)

troubleTicketNoteCorrelatedExecutionop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketNoteCorrelatedExecution

The correlated *ProcedureExecutionContainer* corresponding to the corrective maintenance actions depicted in the Trouble Ticket Note (i.e. the set of `EventRecord` about interactions with the system and as notified by the system). From a practical perspective, relating a `noria:TroubleTicketNote` to a `pep:ProcedureExecutionContainer` is akin to show off the materialization of a corrective maintenance action from the technical perspective. Note that for actions undoubtedly related to a given trouble ticket note (i.e. that can be asserted without mining for execution context candidates), one can avoid using `troubleTicketNoteCorrelatedExecution` by directly relating the note to `EventRecord` with `ldp:member` as `TroubleTicket` and `TroubleTicketNote` are themselves subclasses of `pep:ProcedureExecutionContainer`.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
has super-properties
relation
has domain
TroubleTicketNote c
has range
procedure execution container

troubleTicketNoteOperationTypeop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketNoteOperationType

The operation type of the note.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
Example
Inward customer comments, Local customer call back, Tests and measurements, Diagnosis, etc.
has super-properties
type
has domain
TroubleTicketNote c
has range
concept and (in scheme value operation type)

troubleTicketOriginop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketOrigin

The person or group family at the origin of the creation of the Trouble Ticket.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
Example
Customer, Supervision, Internal, Carrier, User, Partners
has super-properties
type
has domain
TroubleTicket c
has range
concept and (in scheme value origin)

troubleTicketPartyInterventionop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketPartyIntervention

The history of groups activation and responsibility transfer.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
has domain
TroubleTicket c

troubleTicketPriorityop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketPriority

The trouble management priority.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
Example
P1, P2, P3, P4
has super-properties
type
has domain
TroubleTicket c
has range
concept and (in scheme value priority)

troubleTicketRelatedPartyop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketRelatedParty

The related party(ies) that are associated to the ticket.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
has super-properties
eventRelatedParty op
has domain
TroubleTicket c
has range
agent

troubleTicketRelatedResourceop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketRelatedResource

The Resource entity on which the trouble ticket has been created.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-properties
eventRelatedElement op, relation
has domain
TroubleTicket c
has range
Resource c

troubleTicketRelatedServiceop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketRelatedService

The *Application* or *Service* entity on which trouble ticket has been created.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
Example
- TroubleTicket.troubleTicketImpacts("syslog-ng")
  Application("syslog-ng").applicationType(<kos/application/type/service-platform>)

- TroubleTicket.troubleTicketImpacts("Corporate Internet access Infrastructure")
  Application("Corporate Internet access Infrastructure").applicationType(<kos/application/type/infrastructure>)
has super-properties
eventRelatedElement op, relation
has domain
TroubleTicket c
has range
Application c
ApplicationModule c
Service c

troubleTicketSeverityop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketSeverity

The criticity of the incident. The classification (severity) of the Incident may be defined in accordance with Service Level Agreement (SLA) requirements. The thresholds of Incident resolution depend on standards defined per service type. When the thresholds are exceeded, specific process of escalation may be activated.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
Example
Minor, Major, Blocking, etc.
has super-properties
type
has domain
TroubleTicket c
has range
concept and (in scheme value severity)

troubleTicketStatusCurrentop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketStatusCurrent

The current activity status of the trouble ticket.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
Example
Initialised, InProgress, Frozen, Restored, Resolved, Closed
has domain
TroubleTicket c
has range
concept and (in scheme value status)

troubleTicketTriggerop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketTrigger

has domain
TroubleTicket c
has range
EventRecord c

troubleTicketTypeop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketType

The ticket type.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
Example
Failure, Long period assistance, Assistance, Installation, Maintenance, Parametrization, etc.
has super-properties
type
has domain
TroubleTicket c
has range
concept and (in scheme value type)

troubleTicketUrgencyop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketUrgency

The priority level of the incident.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
Example
Immediate Intervention, Deferred Intervention, (State of) Emergency, No intervention, etc.
has super-properties
type
has domain
TroubleTicket c
has range
concept and (in scheme value urgency)

virtualServerStatusop back to ToC or Object Property ToC

IRI: https://w3id.org/noria/ontology/virtualServerStatus

The operational status of the Virtual Server.
Is defined by
https://w3id.org/noria/ontology/ObservableOntology
Term status
unstable
has super-properties
structuralElementObservable op
has domain
Resource c
has range
concept and (in scheme value operational state)

Data Properties

agentInstructionsdp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/agentInstructions

Instructions for involving the Agent (Team, Group, Employee).
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
stable
Example
Use the Ticketing system + hotline phone number for national L2 and L3 issues.
has domain
agent
has range
string

agentWorkingHoursdp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/agentWorkingHours

The Working Hours for reaching the Agent (Team, Employee, etc.).
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
unstable
Example
8:00 am - 12:00 am / 1:00 pm - 5:30 pm (Mon --> Fri)
8H-12H/13H-17H30 (lun --> ven)
has domain
agent
has range
string

applicationFunctionalDomaindp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/applicationFunctionalDomain

The functional domain of the Application for describing the organization’s activities from a system point of view. Alignment: - *tmforum*: the `noria:applicationFunctionalDomain` is equivalent to the *Domain* concept of the ODA Functional Framework.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
https://www.tmforum.org/oda/information-systems/information-framework-sid/
Term status
unstable
Example
- Market and Customer Relationship Management domain
- Service Development, Management and Operations
- Resource Development, Management and Operations
has domain
Application c

applicationFunctionalSubDomaindp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/applicationFunctionalSubDomain

The functional sub-domain of the Application for describing the organization’s activities from a system point of view. Alignment: - *tmforum*: the `noria:applicationFunctionalSubDomain` is equivalent to *Aggregate Business Entities* (ABEs) and *Business Entities* (BEs) of the ODA Functional Framework.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
https://www.tmforum.org/oda/information-systems/information-framework-sid/
Term status
unstable
Example
- Human Resource Management
- Offer and Product Operational Analysis
- Resource Repository Management
has domain
Application c

applicationModelIdentifierdp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/applicationModelIdentifier

Application model code.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
stable
has super-properties
identifier
has domain
Application c
has range
string

applicationModuleHotlineEnableddp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/applicationModuleHotlineEnabled

Hotline enabled for issues on a given ApplicationModule.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
unstable
has domain
ApplicationModule c
has range
boolean

applicationModuleIdentifierdp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/applicationModuleIdentifier

Application module code.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
stable
has super-properties
identifier
has domain
ApplicationModule c
has range
string

applicationModuleNamedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/applicationModuleName

The name of the Application module.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
stable
Example
CONCAT(
    Application().applicationModelIdentifier(),
    "_",
    ApplicationModule().applicationModuleIdentifier()
)
has super-properties
functionalElementDistinguishedName dp
has domain
ApplicationModule c
has range
string

applicationModuleSlaLevelDatedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/applicationModuleSlaLevelDate

SLA Level date, the date at which the SLA Level has been set or updated.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
unstable
has super-properties
in x s d date time stamp
has domain
ApplicationModule c

applicationNumericalIdentifierdp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/applicationNumericalIdentifier

Application numerical identifier, the numerical identifier of the Application within the Information System.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
unstable
has super-properties
identifier
has domain
Application c
has range
int

applicationShortIdentifierdp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/applicationShortIdentifier

Application short identifier, a short string identifier of Application within the Information System.
Is defined by
https://w3id.org/noria/ontology/ApplicationOntology
Term status
stable
has super-properties
functionalElementDistinguishedName dp, identifier
has domain
Application c
has range
string

changeRequestActualEndTimedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/changeRequestActualEndTime

Date and time on which the Change Request implementation has been completed. It is displayed only after the Change Request implementation has been completed actually.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-properties
date
has domain
ChangeRequest c
has range
date time

changeRequestActualStartTimedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/changeRequestActualStartTime

Date and time on which the Change Request implementation has started. It is displayed only after the Change Request implementation has started actually.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-properties
date
has domain
ChangeRequest c
has range
date time

changeRequestIsRegulateddp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/changeRequestIsRegulated

If *true*, the Change Request is subject to special regulations.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
has domain
ChangeRequest c
has range
boolean

changeRequestOutageDurationdp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/changeRequestOutageDuration

Expected duration of the outage, if any involved by the Change Request type.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-properties
extent
has domain
ChangeRequest c
has range
duration

changeRequestPlannedEndTimedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/changeRequestPlannedEndTime

Date and time on which is planned the end of the implementation of the Change Request. It is displayed only before the Change Request implementation is completed.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-properties
date
has domain
ChangeRequest c
has range
date time

changeRequestPlannedStartTimedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/changeRequestPlannedStartTime

Date and time on which is planned the end of the implementation of the Change Request. It is displayed only before the Change Request implementation is completed.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-properties
date
has domain
ChangeRequest c
has range
date time

documentExternalIddp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/documentExternalId

ID given by the requestor to facilitate the relationship set up and searches afterwards.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
Example
Customer reference, Identifier coming from an external system, etc.
has super-properties
identifier
has domain
ChangeRequest c
TroubleTicket c
has range
string

documentHRefdp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/documentHRef

Hyperlink to the TroubleTicket or ChangeRequest entity in the originating information system.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-properties
source
has domain
ChangeRequest c
TroubleTicket c
has range
any u r i

elementDistinguishedNamedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/elementDistinguishedName

The Distinguished Name of the Element Instance (i.e. unique identifier).
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
unstable
has sub-properties
functionalElementDistinguishedName dp, structuralElementDistinguishedName dp

functionalElementDistinguishedNamedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/functionalElementDistinguishedName

The Distinguished Name of the Functional Element Instance (i.e. unique identifier).
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
unstable
has super-properties
elementDistinguishedName dp
has sub-properties
applicationModuleName dp, applicationShortIdentifier dp

locusLinedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/locusLine

The line identifier in a `noria:Room` for a Locus defined by Cartesian coordinates.
Is defined by
https://w3id.org/noria/ontology/LocationOntology
Term status
unstable
Example
Line:L, in Room:Server room 314.
has domain
Locus c

locusLinedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/locusRow

The row identifier in a `noria:Room` for a Locus defined by Cartesian coordinates.
Is defined by
https://w3id.org/noria/ontology/LocationOntology
Term status
unstable
Example
Column:6, in Room:Server room 314.
has domain
Locus c

loggingTimedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/loggingTime

The Date on which the log record was created in the system.
Is defined by
https://w3id.org/noria/ontology/NotificationOntology
https://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/x721.html#-loggingTime
Term status
stable
has super-properties
created, time
has domain
EventRecord c
has range
date time

logTextdp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/logText

Textual information describing the logged event.
Is defined by
https://w3id.org/noria/ontology/NotificationOntology
https://www.itu.int/ITU-T/formal-language/itu-t/x/x721/1992/x721.html#-additionalText
Term status
stable
has super-properties
has simple result, msg, title
has domain
EventRecord c
has range
string

networkInterfaceDescriptiondp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/networkInterfaceDescription

A human-readable/editable text that describes the network interface. The information included in the description depends on the capabilities of the Resource's operating system.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has domain
NetworkInterface c
has range
string

networkInterfaceLaserRxHighPowerWarningThresholddp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/networkInterfaceLaserRxHighPowerWarningThreshold

The high received power notification threshold.
Is defined by
https://w3id.org/noria/ontology/ObservableOntology
Term status
unstable
has super-properties
structuralElementObservableData dp
has domain
NetworkInterface c
has range
int

networkInterfaceLaserRxLowPowerWarningThresholddp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/networkInterfaceLaserRxLowPowerWarningThreshold

The low received power notification threshold.
Is defined by
https://w3id.org/noria/ontology/ObservableOntology
Term status
unstable
has super-properties
structuralElementObservableData dp
has domain
NetworkInterface c
has range
int

networkInterfaceLaserRxOpticalPowerdp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/networkInterfaceLaserRxOpticalPower

The received optical power measure of the Network Interface, in dBm.
Is defined by
https://w3id.org/noria/ontology/ObservableOntology
Term status
unstable
Example
Rx = -3.58 dBm
has super-properties
structuralElementObservableData dp
has domain
NetworkInterface c
has range
int

networkInterfaceLaserRxOpticalPowerAveragedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/networkInterfaceLaserRxOpticalPowerAverage

The average received optical power of the Network Interface, in dBm.
Is defined by
https://w3id.org/noria/ontology/ObservableOntology
Term status
unstable
has super-properties
structuralElementObservableData dp
has domain
NetworkInterface c
has range
int

networkInterfaceLaserTxOpticalPowerdp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/networkInterfaceLaserTxOpticalPower

The emitted optical power measure of the Network Interface, in dBm.
Is defined by
https://w3id.org/noria/ontology/ObservableOntology
Term status
unstable
Example
Tx = -2.13 dBm
has super-properties
structuralElementObservableData dp
has domain
NetworkInterface c
has range
int

networkInterfaceRoutingPriorityMetricdp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/networkInterfaceRoutingPriorityMetric

The metric value associated to the Network Interface for some routing protocol.
Is defined by
https://w3id.org/noria/ontology/ObservableOntology
Term status
stable
Example
IS-IS route priority=122
has super-properties
structuralElementObservableData dp
has domain
NetworkInterface c
has range
int

networkLinkIddp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/networkLinkId

The UID of the NetworkLink.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has super-properties
identifier
has domain
NetworkLink c
has range
string

networkLinkInstallationDatedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/networkLinkInstallationDate

The installation date of the NetworkLink.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has domain
NetworkLink c
has range
date time

networkLinkTypedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/networkLinkType

A description of the type of the Network Link.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
unstable
has domain
NetworkLink c
has range
string

resourceHostNamedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/resourceHostName

The hostname (nodename) of the Resource.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has super-properties
host, hostname, identifier, structuralElementDistinguishedName dp
has domain
Resource c
has range
string

resourceInstallationDatedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/resourceInstallationDate

The installation date of the Resource.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has domain
Resource c
has range
date time

resourceLogisticIddp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/resourceLogisticId

The logistic UID of the Resource (a.k.a. asset tag).
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has super-properties
identifier
has domain
Resource c
has range
string

resourceSerialNumberdp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/resourceSerialNumber

The serial number of the Resource.
Is defined by
https://w3id.org/noria/ontology/ResourceOntology
Term status
stable
has super-properties
identifier
has domain
Resource c
has range
string

siteIddp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/siteId

A unique identifier of a Site.
Is defined by
https://w3id.org/noria/ontology/LocationOntology
Term status
unstable
has super-properties
identifier
has domain
site

sitePrincipalAddressdp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/sitePrincipalAddress

Street address of a Site.
Is defined by
https://w3id.org/noria/ontology/LocationOntology
Term status
unstable
has sub-properties
sitePrincipalAddressCityName dp, sitePrincipalAddressCountry dp, sitePrincipalAddressPostalCode dp, sitePrincipalAddressStreet dp
has domain
site

sitePrincipalAddressCityNamedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/sitePrincipalAddressCityName

City Name for a Site. Alignment: - *GeoNames*: a `P` class `gn:Feature` (city, village, etc.) may correspond to this property.
Is defined by
https://w3id.org/noria/ontology/LocationOntology
Term status
unstable
has super-properties
sitePrincipalAddress dp
has domain
site

sitePrincipalAddressCountrydp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/sitePrincipalAddressCountry

Country name or code for a Site. Alignment: - *GeoNames*: - a `A` class `gn:Feature` (country, state, region, etc.) may correspond to this property. - prefer ISO 3166 values for easier matching with `gn:countryCode`.
Is defined by
https://w3id.org/noria/ontology/LocationOntology
Term status
unstable
has super-properties
country code, sitePrincipalAddress dp
has domain
site

sitePrincipalAddressPostalCodedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/sitePrincipalAddressPostalCode

Postal Code for a Site. Alignment: - *GeoNames*: *ADM2*, *ADM3* or *ADM4* annotations may correspond to this property, depending on the considered country.
Is defined by
https://w3id.org/noria/ontology/LocationOntology
Term status
unstable
has super-properties
postal code, sitePrincipalAddress dp
has domain
site

sitePrincipalAddressStreetdp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/sitePrincipalAddressStreet

Street for a Site.
Is defined by
https://w3id.org/noria/ontology/LocationOntology
Term status
unstable
has super-properties
sitePrincipalAddress dp
has domain
site

siteTypedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/siteType

The type of a Site.
Is defined by
https://w3id.org/noria/ontology/LocationOntology
Term status
unstable
Example
building, data center, rack
has domain
site

structuralElementDistinguishedNamedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/structuralElementDistinguishedName

The Distinguished Name of the Structural Element Instance (i.e. unique identifier).
Is defined by
https://w3id.org/noria/ontology/CoreOntology
Term status
unstable
has super-properties
elementDistinguishedName dp
has sub-properties
resourceHostName dp

troubleTicketCausedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketCause

The cause(s) defined for the trouble, in plain text.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
Example
SSH authentication failure due to loss of sync to NTP server and internal clock drift.
has super-properties
description
has domain
TroubleTicket c

troubleTicketCommittedRestorationDateTimedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketCommittedRestorationDateTime

The Customer Commitment Deadline Date (calculated on product information).
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-properties
date
has domain
TroubleTicket c

troubleTicketDetectionDateTimedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketDetectionDateTime

The date on which the trouble was discovered.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-properties
date
has domain
TroubleTicket c
has range
date time

troubleTicketIsNotificationEnabledp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketIsNotificationEnable

The *enable* or *disable* external notification on trouble ticket events.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has domain
TroubleTicket c
has range
boolean

troubleTicketPlannedRestorationDateTimedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketPlannedRestorationDateTime

Confirmed to customer planned restoration date ATR (Actual Time to Restore (ATR)).
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-properties
date
has domain
TroubleTicket c
has range
date time

troubleTicketSupervisionTooldp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketSupervisionTool

Supervision tool which detected the problem.
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
unstable
has super-properties
source
has domain
TroubleTicket c
has range
string

troubleTicketTargetRestorationDateTimedp back to ToC or Data Property ToC

IRI: https://w3id.org/noria/ontology/troubleTicketTargetRestorationDateTime

The Customer initial restoration date Estimated Time to Restore (ETR).
Is defined by
https://w3id.org/noria/ontology/DocumentOntology
Term status
stable
has super-properties
date
has domain
TroubleTicket c
has range
date time

Legend back to ToC

c: Classes
op: Object Properties
dp: Data Properties
null

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.