language en
Latest version:
Version 1.1
Download serialization:
JSON-LD RDF/XML N-Triples TTL
License:
http://insertlicenseURIhere.example.org
Visualization:
Visualize with WebVowl
Provenance of this page
Ontology Specification Draft

Abstract

This is a placeholder text for the abstract. The abstract should contain a couple of sentences summarizing the ontology and its purpose.

Introduction back to ToC

This is a place holder text for the introduction. The introduction should briefly describe the ontology, its motivation, state of the art and goals.

Namespace declarations

Table 1: Namespaces used in the document
[Ontology NS Prefix]<http://www.w3id.org/ecsel-dr-AH#>
ecsel-dr<http://www.w3id.org/ecsel-dr#>
ecsel-dr-AT<http://www.w3id.org/ecsel-dr-AT#>
ecsel-dr-PWR<http://www.w3id.org/ecsel-dr-PWR#>
error<http://org.semanticweb.owlapi/error#>
http://www.w3id.org/ecsel-dr-AH<http://www.w3id.org/ecsel-dr-AH>
owl<http://www.w3.org/2002/07/owl#>
rdf<http://www.w3.org/1999/02/22-rdf-syntax-ns#>
rdfs<http://www.w3.org/2000/01/rdf-schema#>
xml<http://www.w3.org/XML/1998/namespace>
xsd<http://www.w3.org/2001/XMLSchema#>

Arrowhead: Overview back to ToC

This ontology has the following classes and properties.

Classes

Object Properties

Data Properties

Arrowhead: Description back to ToC

This is a placeholder text for the description of your ontology. The description should include an explanation and a diagram explaining how the classes are related, examples of usage, etc.

Cross-reference for Arrowhead classes, object properties and data properties back to ToC

This section provides details for each class and property defined by Arrowhead.

Classes

AH Application Servcice IDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Application_Servcice_IDD

has super-classes
Interface Design Description IDD c

AH Application Servicec back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Application_Service

Application services – they are application specific and are implemented by application systems along with functionalities (to match requirements of an application)
has super-classes
AH Service c

AH Application Service SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Application_Service_SD

has super-classes
Service Description SD c

AH Application System Sy SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Application_System_Sy_SD

has super-classes
System Description Sy SD c

AH Application System Sy SDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Application_System_Sy_SDD

has super-classes
System Design Description Sy SDD c

AH Authorization Control Service IDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Authorization_Control_Service_IDD

has super-classes
AH Mandatory Core Service IDD c

AH Authorization Control Service SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Authorization_Control_Service_SD

has super-classes
AH Mandatory Core Service SD c

AH Authorization System Sy SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Authorization_System_Sy_SD

has super-classes
AH Mandatory Core System Sy SD c

AH Authorization System Sy SDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Authorization_System_Sy_SDD

has super-classes
AH Mandatory Core System Sy SDD c

AH Authorization System WADLc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Authorization_System_WADL

has super-classes
System Web Application Description WADL c

AH Automation Supporting Servicec back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Automation_Supporting_Service

has super-classes
AH Core Service c

AH Automation Supporting Service IDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Automation_Supporting_Service_IDD

has super-classes
AH Core Service IDD c
has sub-classes
AH Device Discovery Service IDD c, AH Global Service Discovery Service IDD c, AH Inter Cloud Negotiations Service IDD c, AH Session Establish Service IDD c, AH Session Management Service IDD c, AH System Discovery Service IDD c

AH Automation Supporting Service SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Automation_Supporting_Service_SD

has super-classes
AH Core Service SD c
has sub-classes
AH Device Discovery Service SD c, AH Global Service Discovery Service SD c, AH Inter Cloud Negotiations Service SD c, AH Session Establish Service SD c, AH Session Management Service SD c, AH System Discovery Service SD c

AH Automation Supporting Systemc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Automation_Supporting_System

has super-classes
Arrowhead Core Component c
is disjoint with
AH Mandatory Core System c

AH Automation Supporting System Sy SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Automation_Supporting_System_Sy_SD

has super-classes
AH Core System Sy SD c
has sub-classes
AH Device Registry System Sy SD c, AH Gatekeeper System Sy SD c, AH Gateway System Sy SD c, AH Historian Sy SD c, AH QoS Manager Sy SD c, AH System Registry System Sy SD c

AH Automation Supporting System Sy SDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Automation_Supporting_System_Sy_SDD

has super-classes
AH Core System Sy SDD c
has sub-classes
AH Device Registry System Sy SDD c, AH Gatekeeper System Sy SDD c, AH Gateway System Sy SDD c, AH Historian Sy SDD c, AH QoS Manager Sy SDD c, AH System Registry System Sy SDD c

AH Core Servicec back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Core_Service

has super-classes
AH Service c
has sub-classes
AH Automation Supporting Service c, AH Mandatory Core Service c

AH Core Service IDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Core_Service_IDD

has super-classes
Interface Design Description IDD c
has sub-classes
AH Automation Supporting Service IDD c, AH Mandatory Core Service IDD c

AH Core Service SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Core_Service_SD

has super-classes
Service Description SD c
has sub-classes
AH Automation Supporting Service SD c, AH Mandatory Core Service SD c

AH Core System Sy SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Core_System_Sy_SD

has super-classes
System Description Sy SD c
has sub-classes
AH Automation Supporting System Sy SD c, AH Mandatory Core System Sy SD c

AH Core System Sy SDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Core_System_Sy_SDD

has super-classes
System Design Description Sy SDD c
has sub-classes
AH Automation Supporting System Sy SDD c, AH Mandatory Core System Sy SDD c

AH Device Discovery Service IDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Device_Discovery_Service_IDD

has super-classes
AH Automation Supporting Service IDD c

AH Device Discovery Service SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Device_Discovery_Service_SD

has super-classes
AH Automation Supporting Service SD c

AH Device Registry System Sy SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Device_Registry_System_Sy_SD

has super-classes
AH Automation Supporting System Sy SD c

AH Device Registry System Sy SDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Device_Registry_System_Sy_SDD

has super-classes
AH Automation Supporting System Sy SDD c

AH Gatekeeper System Sy SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Gatekeeper_System_Sy_SD

has super-classes
AH Automation Supporting System Sy SD c

AH Gatekeeper System Sy SDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Gatekeeper_System_Sy_SDD

has super-classes
AH Automation Supporting System Sy SDD c

AH Gateway System Sy SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Gateway_System_Sy_SD

has super-classes
AH Automation Supporting System Sy SD c

AH Gateway System Sy SDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Gateway_System_Sy_SDD

has super-classes
AH Automation Supporting System Sy SDD c

AH Global Service Discovery Service IDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Global_Service_Discovery_Service_IDD

has super-classes
AH Automation Supporting Service IDD c

AH Global Service Discovery Service SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Global_Service_Discovery_Service_SD

has super-classes
AH Automation Supporting Service SD c

AH Historian Sy SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Historian_Sy_SD

has super-classes
AH Automation Supporting System Sy SD c

AH Historian Sy SDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Historian_Sy_SDD

has super-classes
AH Automation Supporting System Sy SDD c

AH Inter Cloud Negotiations Service IDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Inter_Cloud_Negotiations_Service_IDD

has super-classes
AH Automation Supporting Service IDD c

AH Inter Cloud Negotiations Service SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Inter_Cloud_Negotiations_Service_SD

has super-classes
AH Automation Supporting Service SD c

AH Local Cloudc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Local_Cloud

has super-classes
cloud lobe c

AH Mandatory Core Servicec back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Mandatory_Core_Service

has super-classes
AH Core Service c

AH Mandatory Core Service IDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Mandatory_Core_Service_IDD

Class of all Interface Design Descriptions (IDDs) of mandatory Arrowwhead core services. While the class AH_mandatory_core_service contains the mandatory core services only as instances, this class contains classes of the IDDs of each single mandatory core service as subclasses (not only as instances). Since each AH Local Cloud runs one instance of each mandatory core service, each of these services has to be documented by an AH service documentation, i.e. at least by a SD and a IDD. So the IDD is an individual document for each mandatory core service in each single Local Cloud. Hence, all IDDs of a certain mandatory core service will be individuals of the corresponding IDD class.
has super-classes
AH Core Service IDD c
has sub-classes
AH Authorization Control Service IDD c, AH Orchestration Service IDD c, AH Service Discovery Service IDD c, AH Store Management Service IDD c, AH Token Generation Service IDD c

AH Mandatory Core Service SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Mandatory_Core_Service_SD

has super-classes
AH Core Service SD c
has sub-classes
AH Authorization Control Service SD c, AH Orchestration Service SD c, AH Service Discovery Service SD c, AH Store Management Service SD c, AH Token Generation Servcie SD c

AH Mandatory Core Systemc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Mandatory_Core_System

has super-classes
Arrowhead Core Component c
is disjoint with
AH Automation Supporting System c

AH Mandatory Core System Sy SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Mandatory_Core_System_Sy_SD

has super-classes
AH Core System Sy SD c
has sub-classes
AH Authorization System Sy SD c, AH Orchestration System Sy SD c, AH Service Registry System Sy SD c

AH Mandatory Core System Sy SDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Mandatory_Core_System_Sy_SDD

has super-classes
AH Core System Sy SDD c
has sub-classes
AH Authorization System Sy SDD c, AH Orchestration System Sy SDD c, AH Service Registry System Sy SDD c

AH Orchestration Service IDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Orchestration_Service_IDD

has super-classes
AH Mandatory Core Service IDD c

AH Orchestration Service SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Orchestration_Service_SD

has super-classes
AH Mandatory Core Service SD c

AH Orchestration System Sy SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Orchestration_System_Sy_SD

has super-classes
AH Mandatory Core System Sy SD c

AH Orchestration System Sy SDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Orchestration_System_Sy_SDD

has super-classes
AH Mandatory Core System Sy SDD c

AH Orchestrator WADLc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Orchestrator_WADL

has super-classes
System Web Application Description WADL c

AH QoS Manager Sy SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_QoS_Manager_Sy_SD

has super-classes
AH Automation Supporting System Sy SD c

AH QoS Manager Sy SDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_QoS_Manager_Sy_SDD

has super-classes
AH Automation Supporting System Sy SDD c

AH Servicec back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Service

has super-classes
Service c
has sub-classes
AH Application Service c, AH Core Service c
is in domain of
is a h service documented by op

AH Service Discovery Service IDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Service_Discovery_Service_IDD

has super-classes
AH Mandatory Core Service IDD c

AH Service Discovery Service SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Service_Discovery_Service_SD

has super-classes
AH Mandatory Core Service SD c

AH Service Documentationc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Service_Documentation

has super-classes
Service Documentation c
is in range of
is a h service documented by op, is part of service documentation op

AH Service Documentation Documentc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Service_Documentation_Document

Document belonging to the documentation of an Arrowhead Service. There are four types of documents for Arrowhead service documentations: - Service Description - Interface Design Description - Communication Profile - Semantic Profile. The central documents are IDDs. They document the implementation of a certain service based on a certain communication technology (communication, encoding, data format) and a certain information model. The Service Description contains a more general description of the service, without the link to a specific communication technology or information model. Communication Profiles and Semantic Profiles are optional documents for a service documentation. They can be seen as modules of an IDD, since they can describe the communication technolopgy and the information model of a service implementation as external documents. If they exist, the IDD refers to them instead of declaring these contents by themselfes. That is, CP and SP are useful if different service implementations use the same CP and SP - then their IDDs can refer to one and the same CP or SP document.
has super-classes
Documentation Document c
has sub-classes
Communication Profile c, Interface Design Description IDD c, Semantic Profile c, Service Description SD c
is in domain of
is part of service documentation op

AH Service Registry System Sy SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Service_Registry_System_Sy_SD

has super-classes
AH Mandatory Core System Sy SD c

AH Service Registry System Sy SDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Service_Registry_System_Sy_SDD

has super-classes
AH Mandatory Core System Sy SDD c

AH Service Registry WADLc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Service_Registry_WADL

has super-classes
System Web Application Description WADL c

AH Session Establish Service IDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Session_Establish_Service_IDD

has super-classes
AH Automation Supporting Service IDD c

AH Session Establish Service SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Session_Establish_Service_SD

has super-classes
AH Automation Supporting Service SD c

AH Session Management Service IDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Session_Management_Service_IDD

has super-classes
AH Automation Supporting Service IDD c

AH Session Management Service SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Session_Management_Service_SD

has super-classes
AH Automation Supporting Service SD c

AH Store Management Service IDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Store_Management_Service_IDD

has super-classes
AH Mandatory Core Service IDD c

AH Store Management Service SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Store_Management_Service_SD

has super-classes
AH Mandatory Core Service SD c

AH Systemc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_System

has super-classes
Software System c
has sub-classes
Arrowhead Application Component c, Arrowhead Core Component c
is in domain of
is a h system documented by op

AH System Discovery Service IDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_System_Discovery_Service_IDD

has super-classes
AH Automation Supporting Service IDD c

AH System Discovery Service SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_System_Discovery_Service_SD

has super-classes
AH Automation Supporting Service SD c

AH System Documentationc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_System_Documentation

has super-classes
System Documentation c
is in range of
is a h system documented by op, is part of system documentation op

AH System Documentation Documentc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_System_Documentation_Document

has super-classes
Documentation Document c
has sub-classes
System Description Sy SD c, System Design Description Sy SDD c, System Web Application Description WADL c
is in domain of
is part of system documentation op

AH System Of Systems Documentationc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_System_Of_Systems_Documentation

has super-classes
System Documentation c
is in range of
is part of SoS documentation op

AH System Of Systems Documentation Documentc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_System_Of_Systems_Documentation_Document

has super-classes
Documentation Document c
has sub-classes
System Of Systems Description So SD c, System Of Systems Design Description So SDD c
is in domain of
is part of SoS documentation op

AH System Registry System Sy SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_System_Registry_System_Sy_SD

has super-classes
AH Automation Supporting System Sy SD c

AH System Registry System Sy SDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_System_Registry_System_Sy_SDD

has super-classes
AH Automation Supporting System Sy SDD c

AH Token Generation Servcie SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Token_Generation_Servcie_SD

has super-classes
AH Mandatory Core Service SD c

AH Token Generation Service IDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Token_Generation_Service_IDD

has super-classes
AH Mandatory Core Service IDD c

Arrowheadc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Arrowhead

has super-classes
Service-Oriented Architecture c

Arrowhead Application Componentc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Application_System

has super-classes
AH System c
is disjoint with
Arrowhead Core Component c

Arrowhead Core Componentc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#AH_Core_System

Software system, that belongs to the "standard" components offered by Arrowhead framework. Arrowhead core systems can occur once in each Arrowhead Local Cloud. Arriwhead Core Systems can be distinguished in Arrowhead Mandatory Core Systems and Automation supporting systems. Mandatory core systems must exist in each Arrowhead Local Cloud, Automation supporting systems can occur in an Arrowhead Local Cloud.
has super-classes
AH System c
has sub-classes
AH Automation Supporting System c, AH Mandatory Core System c
is disjoint with
Arrowhead Application Component c

Communication Profilec back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Communication_Profile_CP

Communication Profile (CP)
has super-classes
AH Service Documentation Document c
is in range of
refers to CP op

Communication Security Mechanismc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Communication_Security_Mechanism

corresponds to a part of OSI layer 5
has super-classes
Communication Technology c
is in range of
documents AH service comm security mechanism op, uses communication security mechanism op

Communication Technologyc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Communication_Technology

Communications technology, also known as information technology, refers to all equipment and programs that are used to process and communicate information.
has super-classes
cloud lobe c
has sub-classes
Communication Security Mechanism c, Data Link Media Access Technology c, End-to-End Communication Technology c, Point-to-Point Communication Technology c, Transfer Protocol c

Constrained Devicec back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Constrained_Device

A constrained device is a device in the sense of an service-oriented architecture that is restricted in terms of processing capabilities (speed, complexity of operations), memory and power supply. The concept constrained device was introduced in the context of the Internet of Things (IoT) and refers for example to sensor devices, location devices, switches etc. which are connected by low-power wireless communication technologies like BLE, ZigBee, Z-Wave etc., have a battery on board that should last for two to three years and which are (very) small in physical size.
has super-classes
Device c
has sub-classes
Illumination Device c, Sensor Device c, Switch Device c

Data Formatc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Data_Format

Data format in information technology may refer to: Data type, constraint placed upon the interpretation of data in a type system.
has super-classes
cloud lobe c
is in range of
documents AH service data format op, uses data format op

Data Modelc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Data_Model

A data model is an abstract model that organizes elements of data and standardizes how they relate to one another and to the properties of real-world entities.
has super-classes
cloud lobe c

Devicec back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Device

A device in the context of Arrowhead framework is a piece of equipment, machine, hardware, etc. with computational, memory, and communication capabilities which hosts one or several Arrowhead Framework systems. (Source: Arrowhead)
is equivalent to
device c
device c
has super-classes
cloud lobe c
has sub-classes
Constrained Device c, Gateway c, Industrial Personal Computer c, Personal Computer c, Programmable Logic Controller c, Raspberry Pi c, Smartphone c, Tablet Computer c
is in domain of
IP address dp, MAC address dp, device ID dp, device name dp, hosts op, is device in op
is in range of
contains device op, is hosted by op, runs on op

Documentation Documentc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Documentation_Document

A document that documents something
has super-classes
cloud lobe c
has sub-classes
AH Service Documentation Document c, AH System Documentation Document c, AH System Of Systems Documentation Document c
is in domain of
documents service part op, is part of op, is referred to by op, refers to op
is in range of
has part op, is referred to by op, refers to op

End-to-End Communication Technologyc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#End_To_End_Communication_Technology

The end-to-end principle is a design framework in computer networking. In networks designed according to this principle, application-specific features reside in the communicating end nodes of the network, rather than in intermediary nodes, such as gateways and routers, that exist to establish the network.
has super-classes
Communication Technology c

Gatewayc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Gateway

A gateway is a piece of networking hardware used in telecommunications for telecommunications networks that allows data to flow from one discrete network to another.
is equivalent to
gateway c
has super-classes
Device c

Illumination Devicec back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Illumination_Device

A category of devices which's purpose is to illuminate
has super-classes
Constrained Device c

Industrial Personal Computerc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Industrial_Personal_Computer

Industrial PCs are primarily used for process control and/or data acquisition. In some cases, an industrial PC is simply used as a front-end to another control computer in a distributed processing environment.
has super-classes
Device c

Information Modelc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Information_Model

An information model in software engineering is a representation of concepts and the relationships, constraints, rules, and operations to specify data semantics for a chosen domain of discourse. Typically it specifies relations between kinds of things, but may also include relations with individual things.
has super-classes
cloud lobe c
is in domain of
is information model of op
is in range of
documents AH service information model op, has information model op

Interface Design Description IDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Interface_Design_Description_IDD

Interface Design Description (IDD)
has super-classes
AH Service Documentation Document c
has sub-classes
AH Application Servcice IDD c, AH Core Service IDD c
is in domain of
documents AH service method op, refers to CP op, refers to SD op, refers to SP op
is in range of
refers to IDD op

Local Networkc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Local_Network

A local area network is a computer network that interconnects computers within a limited area
has super-classes
cloud lobe c

Methodc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Method

Method of a service: method that is provided by a service within a SoA.
has super-classes
cloud lobe c
is in domain of
is method of op
is in range of
documents AH service method op, has method op

Personal Computerc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Personal_Computer

A personal computer (PC) is a multi-purpose computer whose size, capabilities, and price make it feasible for individual use.
has super-classes
Device c

Point-to-Point Communication Technologyc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Point_To_Point_Communication_Technology

corresponds to OSI layer 3, e.g. IPv4 or IPv6
has super-classes
Communication Technology c

Programmable Logic Controllerc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Programmable_Logic_Controller

A programmable logic controller (PLC) is an industrial digital computer which has been ruggedized and adapted for the control of manufacturing processes
is equivalent to
programmable logic controller c
has super-classes
Device c

Raspberry Pic back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Raspberry_Pi

The Raspberry Pi is a series of small single-board computers developed in the United Kingdom by the Raspberry Pi Foundation to put the power of computing and digital making into the hands of people all over the world.
has super-classes
Device c

Semantic Profilec back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Semantic_Profile_SP

Semantic Profile (SP)
has super-classes
AH Service Documentation Document c
is in range of
refers to SP op

Sensor Devicec back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Sensor_Device

A category of devices which's purpose is to sense
is equivalent to
sensor device c
has super-classes
Constrained Device c

Servicec back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Service

In the context of the Arrowhead Framework a Service is the information exchanged from a providing system to a consuming system. • is based on a number of service orientation principles derived from high level objectives and properties of the Arrowhead framework • can be realized by an arbitrary number of service producers and service consumers • a system can consume a number of services, process and provide other services to fulfil a more complex task • can only be provided by technical systems • can support operational activities within business processes • can support non-functional requirements, such as real-time • can have stakeholders, with an interest in business benefit, in one or more specific area of interest • can have an appointed stakeholder, responsible for the governance of the Service (definition, development). (Source: Arrowhead Framework Definitions V2.4 & Arrowhead Device Registry Presentation)
has super-classes
cloud lobe c
has sub-classes
AH Service c
is in domain of
has information model op, has method op, is service documented by op, produced by op, uses comm tech op, uses communication security mechanism op, uses data format op, uses transfer protocol op
is in range of
defines compliant service op, is information model of op, is method of op, is service producer of op, produces op
is disjoint with
Software System c

Service Description SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Service_Description_SD

Service Description (SD)
has super-classes
AH Service Documentation Document c
has sub-classes
AH Application Service SD c, AH Core Service SD c
is in range of
refers to SD op

Service Documentationc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Service_Documentation

Service documentation is any communicable material that is used to describe, explain or instruct regarding some attributes of a service
has super-classes
cloud lobe c
has sub-classes
AH Service Documentation c
is in range of
is service documented by op

Service-Oriented Architecturec back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Service_Oriented_Architecture

Service-oriented architecture (SoA) is a style of software design where services are provided to the other components by application components, through a communication protocol over a network.
is equivalent to
service oriented architecture protocols c
has super-classes
cloud lobe c
has sub-classes
Arrowhead c
is in domain of
defines compliant documentation op, defines compliant service op, defines compliant system op, defines compliant system architecture op, has SoA property op
is in range of
is SoA property of op

Smartphonec back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Smartphone

A smartphone is a mobile device that combines cellular and mobile computing functions into one unit.
has super-classes
Device c

SoA Propertyc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#SoA_Property

has super-classes
cloud lobe c
is in domain of
is SoA property of op
is in range of
has SoA property op

Software Systemc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Software_System

System software is software designed to provide a platform for other software.
has super-classes
cloud lobe c
has sub-classes
AH System c
is in domain of
is hosted by op, is service producer of op, is system documented by op, produces op, runs on op
is in range of
defines compliant system op, hosts op, produced by op
is disjoint with
Service c

Switch Devicec back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Switch_Device

A switch is a device in a computer network that connects other devices together.
has super-classes
Constrained Device c

System Description Sy SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#System_Description_Sy_SD

has super-classes
AH System Documentation Document c
has sub-classes
AH Application System Sy SD c, AH Core System Sy SD c
is in domain of
refers to IDD op
is in range of
refers to Sy SD op

System Design Description Sy SDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#System_Design_Description_Sy_SDD

has super-classes
AH System Documentation Document c
has sub-classes
AH Application System Sy SDD c, AH Core System Sy SDD c
is in range of
refers to Sy SDD op

System Documentationc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#System_Documentation

System documentation is any communicable material that is used to describe, explain or instruct regarding some attributes of a system
has super-classes
cloud lobe c
has sub-classes
AH System Documentation c, AH System Of Systems Documentation c
is in range of
is system documented by op

System Of Systemsc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#System_Of_Systems

System of systems is a collection of task-oriented or dedicated systems that pool their resources and capabilities together to create a new, more complex system which offers more functionality and performance than simply the sum of the constituent systems.
has super-classes
cloud lobe c
is in range of
defines compliant system architecture op

System Of Systems Description So SDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#System_Of_Systems_Description_So_SD

has super-classes
AH System Of Systems Documentation Document c
is in range of
refers to So SD op

System Of Systems Design Description So SDDc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#System_Of_Systems_Design_Description_So_SDD

has super-classes
AH System Of Systems Documentation Document c
is in domain of
refers to So SD op, refers to Sy SDD op

System Web Application Description WADLc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#System_Web_Application_Description_WADL

Description of an Arrowhead compliant software system in terms of the Web Application Description Language WADL. The Web Application Description Language (WADL) is a machine-readable XML description of HTTP-based web services. WADL models the resources provided by a service and the relationships between them. WADL is intended to simplify the reuse of web services that are based on the existing HTTP architecture of the Web. It is platform and language independent and aims to promote reuse of applications beyond the basic use in a web browser. WADL is the REST equivalent of SOAP's Web Services Description Language (WSDL), which can also be used to describe REST web services. Sources: https://en.wikipedia.org/wiki/Web_Application_Description_Language Sun Microsystems (31 August 2009). "Web Application Description Language: W3C Member Submission 31 August 2009". World Wide Web Consortium. Retrieved 12 August 2012. World Wide Web Consortium (14 October 2009). "Team Comment on the "Web Application Description Language" Submission". World Wide Web Consortium. Retrieved 12 August 2012. Lawrence Mandel (29 May 2008). "Describe REST Web services with WSDL 2.0: A how-to guide". IBM. Retrieved 12 August 2012.
has super-classes
AH System Documentation Document c
has sub-classes
AH Authorization System WADL c, AH Orchestrator WADL c, AH Service Registry WADL c

Tablet Computerc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Tablet_Computer

A tablet computer, commonly shortened to tablet, is a mobile device, typically with a mobile operating system and touchscreen display
has super-classes
Device c

Transfer Protocolc back to ToC or Class ToC

IRI: http://www.w3id.org/ecsel-dr-AH#Transfer_Protocol

corresponds to OSI layers 6 and 7
has super-classes
Communication Technology c
is in range of
documents AH service transfer protocol op, uses transfer protocol op

Object Properties

contains deviceop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#contains_device

has super-properties
has architectural part op
has domain
error68 c
has range
Device c
is inverse of
is device in op

defines compliant documentationop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#defines_compliant_documentation

has domain
Service-Oriented Architecture c
has range
error65 c

defines compliant serviceop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#defines_compliant_service

has domain
Service-Oriented Architecture c
has range
Service c

defines compliant systemop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#defines_compliant_system

has domain
Service-Oriented Architecture c
has range
Software System c

defines compliant system architectureop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#defines_compliant_system_architecture

has domain
Service-Oriented Architecture c
has range
System Of Systems c

documentsop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#documents

has domain
error69 c
has range
error62 c
is inverse of
is documented by op

documents AH service comm security mechanismop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#documents_AH_service_comm_security_mechanism

has characteristics: functional

has super-properties
documents AH service comm tech op
has domain
error71 c
has range
Communication Security Mechanism c

documents AH service comm techop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#documents_AH_service_comm_tech

has super-properties
documents service part op
has sub-properties
documents AH service comm security mechanism op, documents AH service data format op, documents AH service transfer protocol op
has domain
error70 c
has range
error64 c

documents AH service data formatop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#documents_AH_service_data_format

has characteristics: functional

has super-properties
documents AH service comm tech op
has domain
error76 c
has range
Data Format c

documents AH service information modelop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#documents_AH_service_information_model

has super-properties
documents service part op
has domain
error75 c
has range
Information Model c

documents AH service methodop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#documents_AH_service_method

Relation between an Interface Design Description document (of a specific service) and a method of this service. The relation expresses that the IDD document documents the methods of the service the IDD belongs to. With this, a consistency check would be possible: IF a service S has a method M AND the IDD IDD_S is part of the service documentation of S (i.e. IDD_S is the IDD of S) THEN IDD_S should contain a documentation of M.
has super-properties
documents service part op
has domain
Interface Design Description IDD c
has range
Method c

documents AH service transfer protocolop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#documents_AH_service_transfer_protocol

has characteristics: functional

has super-properties
documents AH service comm tech op
has domain
error73 c
has range
Transfer Protocol c

documents service partop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#documents_service_part

has sub-properties
documents AH service comm tech op, documents AH service information model op, documents AH service method op
has domain
Documentation Document c

has architectural partop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#has_architectural_part

has sub-properties
contains device op, has method op, hosts op, produces op
is inverse of
is an architectural part of op

has information modelop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#has_information_model

has domain
Service c
has range
Information Model c
is inverse of
is information model of op

has methodop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#has_method

has super-properties
has architectural part op
has domain
Service c
has range
Method c
is inverse of
is method of op

has partop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#has_part_documentation_document

has domain
error74 c
has range
Documentation Document c
is inverse of
is part of op

has SoA propertyop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#has_SoA_property

has domain
Service-Oriented Architecture c
has range
SoA Property c
is inverse of
is SoA property of op

hostsop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#hosts

has super-properties
has architectural part op
has domain
Device c
has range
Software System c
is inverse of
is hosted by op, runs on op

is a h service documented byop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#is_AH_service_documented_by

is AH service documented by
has super-properties
is service documented by op
has domain
AH Service c
has range
AH Service Documentation c

is a h system documented byop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#is_AH_system_documented_by

is AH system documented by
has super-properties
is system documented by op
has domain
AH System c
has range
AH System Documentation c

is an architectural part ofop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#is_architectural_part_of

has sub-properties
is device in op, is hosted by op, is method of op, produced by op
is inverse of
has architectural part op

is device inop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#is_device_in

has super-properties
is an architectural part of op
has domain
Device c
has range
error63 c
is inverse of
contains device op

is documented byop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#is_documented_by

has sub-properties
is service documented by op, is system documented by op
has domain
error67 c
has range
error60 c
is inverse of
documents op

is hosted byop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#is_hosted_by

has equivalent properties
runs on op
has super-properties
is an architectural part of op
has domain
Software System c
has range
Device c
is inverse of
hosts op

is information model ofop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#is_information_model_of

has domain
Information Model c
has range
Service c
is inverse of
has information model op

is method ofop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#is_method_of

has super-properties
is an architectural part of op
has domain
Method c
has range
Service c
is inverse of
has method op

is part ofop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#is_part_of

has sub-properties
is part of SoS documentation op, is part of service documentation op, is part of system documentation op
has domain
Documentation Document c
has range
error61 c
is inverse of
has part op

is part of service documentationop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#is_part_of_service_documentation

has super-properties
is part of op
has domain
AH Service Documentation Document c
has range
AH Service Documentation c

is part of SoS documentationop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#is_part_of_SoS_documentation

has super-properties
is part of op
has domain
AH System Of Systems Documentation Document c
has range
AH System Of Systems Documentation c

is part of system documentationop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#is_part_of_system_documentation

has super-properties
is part of op
has domain
AH System Documentation Document c
has range
AH System Documentation c

is referred to byop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#is_referred_to_by

has domain
Documentation Document c
has range
Documentation Document c
is inverse of
refers to op

is service documented byop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#is_service_documented_by

is service documented by
has super-properties
is documented by op
has sub-properties
is a h service documented by op
has domain
Service c
has range
Service Documentation c

is service producer ofop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#is_service_producer_of

has equivalent properties
produces op
has domain
Software System c
has range
Service c
is inverse of
produced by op

is SoA property ofop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#is_SoA_property_of

has domain
SoA Property c
has range
Service-Oriented Architecture c
is inverse of
has SoA property op

is system documented byop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#is_system_documented_by

is system documented by
has super-properties
is documented by op
has sub-properties
is a h system documented by op
has domain
Software System c
has range
System Documentation c

produced byop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#produced_by

has super-properties
is an architectural part of op
has domain
Service c
has range
Software System c
is inverse of
is service producer of op, produces op

producesop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#produces

Relation expressing that a software system produces a service. Equivalent names for this relation include: offers, provides, isServiceProducerOf Since Arrowhead uses the pair produce / consume and corresponding service producer / service consumer adressing the relations and the software systems, this ontology uses these names for the relations too. If it is needed, object properties with other names can be added and stated to be equivalent to these ones.
has equivalent properties
is service producer of op
has super-properties
has architectural part op
has domain
Software System c
has range
Service c
is inverse of
produced by op

refers toop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#refers_to

describes the relation between two documentation documents that one document refers to another document. To our best knowledge, the following relations hold between different types of documentation documents: - an IDD refers to exactly one SD. - an SD is referred to by one or more IDD (each stating a way of implementing the service with a specific technolopgy (Source: Arrowhead Framework Definitions V2.4)) - an IDD refers to at most one CP (if it not refers to a CP, then the IDD contains all CP information by itself) - an IDD refers to n SP, 0 <= n (if it not refers to a SP, then the IDD contains all SP information by itself) - a SySD refers to one or more IDDs (that is, a system produces one or more services). - a SySDD refers to one or more SySD's. (Remark HB: I don't understand this. How can one concrete white box description of a system fulfill (support / implement) different black box descriptions of systems? The other way around seems to be possible as between SDs and IDDs). - an SoSD refers to n SySD's. - an SoSDD refers to n SoSD's. - an SoSDD refers to n SySD's. - an SoSDD refers to n SySDDs.
has sub-properties
refers to CP op, refers to IDD op, refers to SD op, refers to SP op, refers to So SD op, refers to Sy SD op, refers to Sy SDD op
has domain
Documentation Document c
has range
Documentation Document c
is inverse of
is referred to by op

refers to CPop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#refers_to_CP

an Interface Design Description (IDD) can refer to a Communication Profile (CP). No other documentation document can refer to a CP. Hence the domain of this object property is the class of IDDs. An IDD can refer to a CP, but this is not mandatory. CPs are intended to be used in cases in which several services use the same CP. Then the CP information should be extracted to an CP document and the IDDs of all services that use this CP shall refer to this CP. If the CP is unique for a specific service, the CP information can directly be included in the IDD. If the IDD refers to a CP, this must be a unique reference. That is, one IDD must not refer to different CPs. Hence this object property is functional. (If the service could be implemented using different communication technologies, each implementation would need an own IDD!!).

has characteristics: functional

has super-properties
refers to op
has domain
Interface Design Description IDD c
has range
Communication Profile c

refers to IDDop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#refers_to_IDD

has super-properties
refers to op
has domain
System Description Sy SD c
has range
Interface Design Description IDD c

refers to SDop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#refers_to_SD

has characteristics: functional

has super-properties
refers to op
has domain
Interface Design Description IDD c
has range
Service Description SD c

refers to So SDop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#refers_to_So_SD

has super-properties
refers to op
has domain
System Of Systems Design Description So SDD c
has range
System Of Systems Description So SD c

refers to SPop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#refers_to_SP

an Interface Design Description (IDD) can refer to a Semantic Profile (SP). No other documentation document can refer to a SP. Hence the domain of this object property is the class of IDDs. An IDD can refer to a SP, but this is not mandatory. SPs are intended to be used in cases in which several services use the same SP. Then the SCP information should be extracted to an SP document and the IDDs of all services that use this SP shall refer to this SP. If the SP is unique for a specific service, the SP information can directly be included in the IDD. References to SPs are not necessarily unique for an IDD. That is, different methods of the service documented by the IDD can use different Semantic Profiles.
has super-properties
refers to op
has domain
Interface Design Description IDD c
has range
Semantic Profile c

refers to Sy SDop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#refers_to_Sy_SD

has super-properties
refers to op
has domain
error72 c
has range
System Description Sy SD c

refers to Sy SDDop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#refers_to_Sy_SDD

has super-properties
refers to op
has domain
System Of Systems Design Description So SDD c
has range
System Design Description Sy SDD c

runs onop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#runs_on

has equivalent properties
is hosted by op
has domain
Software System c
has range
Device c
is inverse of
hosts op

uses comm techop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#uses_comm_tech

has sub-properties
uses communication security mechanism op, uses data format op, uses transfer protocol op
has domain
Service c
has range
error66 c

uses communication security mechanismop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#uses_communication_security_mechanism

has super-properties
uses comm tech op
has domain
Service c
has range
Communication Security Mechanism c

uses data formatop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#uses_data_format

has super-properties
uses comm tech op
has domain
Service c
has range
Data Format c

uses transfer protocolop back to ToC or Object Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#uses_transfer_protocol

has super-properties
uses comm tech op
has domain
Service c
has range
Transfer Protocol c

Data Properties

device IDdp back to ToC or Data Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#device_ID

Data property of each device in Arrowhead context. Needed by Device Discovery service. Purpose: provides an unique identifier for a device.

has characteristics: functional

has domain
Device c
has range
string

device namedp back to ToC or Data Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#device_name

has domain
Device c
has range
string

IP addressdp back to ToC or Data Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#IP_address

has domain
Device c
has range
string

MAC addressdp back to ToC or Data Property ToC

IRI: http://www.w3id.org/ecsel-dr-AH#MAC_address

has domain
Device c
has range
string

Legend back to ToC

c: Classes
op: Object Properties
dp: Data Properties

References back to ToC

Add your references here. It is recommended to have them as a list.

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.