IIRA Crosscutting Function
creator: sebastian
type: Class
comment: Often these enabling functions, the so-called crosscutting functions, need to be made available across many of the system functional components. For Reference Architecture 6: Functional Viewpoint example, system functions need to be connected so they can interact with each other to complete functionality at the system level.
subclass of: Standard Classification
subclass of: Restriction
  has value: FunctionalViewpoint
  on property: isPartOf

IIRA Functional Domain
type: Class
subclass of: Standard Classification
subclass of: Restriction
  has value: Industrial Internet Reference Architecture
  on property: is Described in

IIRA System Characteristic
type: Class
subclass of: Standard Classification
subclass of: Restriction
  has value: FunctionalViewpoint
  on property: isPartOf

Description
description: Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource.
Has Version: description-006
issued: 1999-07-02
Date Modified: 2008-01-14
comment: An account of the resource.
note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.

Title
Has Version: title-006
issued: 1999-07-02
Date Modified: 2008-01-14
comment: A name given to the resource.
note: A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.

License Document
type: Class
comment: A legal document giving official permission to do something with a Resource.

Creator
description: Examples of a Creator include a person, an organization, or a service.
Has Version: creatorT-002
issued: 2008-01-14
Date Modified: 2010-10-11
comment: An entity primarily responsible for making the resource.
range: Agent
sub property of: creator
sub property of: contributor
equivalent property: maker

Description
description: Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource.
Has Version: descriptionT-001
issued: 2008-01-14
Date Modified: 2008-01-14
comment: An account of the resource.
sub property of: Description

Has Version
Has Version: hasVersion-003
issued: 2000-07-11
Date Modified: 2008-01-14
comment: A related resource that is a version, edition, or adaptation of the described resource.
sub property of: relation
note: This term is intended to be used with non-literal values as defined in the DCMI Abstract Model (http://dublincore.org/documents/abstract-model/). As of December 2007, the DCMI Usage Board is seeking a way to express this intention with a formal range declaration.

Date Issued
Has Version: issued-003
issued: 2000-07-11
Date Modified: 2008-01-14
comment: Date of formal issuance (e.g., publication) of the resource.
range: Literal
sub property of: date

Date Modified
Has Version: modified-003
issued: 2000-07-11
Date Modified: 2008-01-14
comment: Date on which the resource was changed.
range: Literal
sub property of: date

Title
Has Version: titleT-002
issued: 2008-01-14
Date Modified: 2010-10-11
comment: A name given to the resource.
range: Literal
sub property of: Title

Stakeholder Group
creator: sebastian
type: Class
type: NamedIndividual
comment: A Stakeholder Group is a party of people who have common interests and concerns.
comment: A stakeholder is everyone with an interest in a system.
note: Stakeholders are interpreted in the same manner as outlined by ISO 42010: '<system> individual, team, organization, or classes thereof, having an interest in a system'

IDS RAM Perspective
type: Class
subclass of: Standard Classification
equivalent class: Class
  one of: Certification
  one of: Governance
  one of: Security

has numerical value
type: DatatypeProperty
domain: Class

has unit
type: ObjectProperty
domain: Error1
range: Unit

is Component Of
type: ObjectProperty
comment: Represents Standards that are component of other Standards. This relation is not transitive
domain: Standard
range: Class
  union of: Standard
  union of: StandardPart
sub property of: related To

is member of
type: ObjectProperty
comment: A relation between collections and entities, e.g. 'the Night Watch by Rembrandt is in the Rijksmuseum collection'; 'Davide is member of the Pen Club', 'Igor is one the subjects chosen for the experiment'.
domain: Entity
label: è membro di @it
range: Collection
sub property of: associatedWith

alternative label
type: AnnotationProperty

definition
type: AnnotationProperty

note
type: AnnotationProperty

preferred label
type: AnnotationProperty

was Generated By
type: ObjectProperty
comment: Standard A has influences in Standard B. For example, IEC_61499 hasInfluenceIn IEC_61804-2(EDDL)
sub property of: related To

Family Name
type: property
domain: person

mbox
type: property
domain: Agent
range: thing

name
type: property
domain: thing

Admin Shell Sub Model
type: Class
comment: Describes the Administration Shell concept to organize/classify standards into submodels
subclass of: Standard Classification

RAMI Hierarchy Level
type: Class
subclass of: Standard Classification
equivalent class: Class
  one of: ConnectedWorld
  one of: ControlDevice
  one of: Enterprise
  one of: FieldDevice
  one of: Product
  one of: Station
  one of: WorkCenter

RAMI IT Layer
type: Class
subclass of: Standard Classification
equivalent class: Class
  one of: Asset
  one of: Business
  one of: Communication
  one of: Functional
  one of: Information
  one of: Integration

RAMI Life Cycle Layer
type: Class
subclass of: Standard Classification
definition: It describes the different Life Cycle and Value Stream layers for the RAMI model according to the IEC 62890 Standard.

Artificial Intelligence
creator: sebastian
type: NamedIndividual
type: Concern
comment: Artificial intelligence (AI) is intelligence exhibited by machines. In computer science, an ideal "intelligent" machine is a flexible rational agent that perceives its environment and takes actions that maximize its chance of success at some goal. Colloquially, the term "artificial intelligence" is applied when a machine mimics "cognitive" functions that humans associate with other human minds, such as "learning" and "problem solving". (source: wikipedia)
has d bpedia resource: Artificial intelligence
supports: Data Analytics

AMQP
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: AMQP (Advanced Message Queuing Protocol): An open standard application layer protocol for message-oriented middleware. The defining features of AMQP are message orientation, queuing, routing (including point-to-point and publish-and-subscribe), reliability and security. (source: https://www.postscapes.com/internet-of-things-protocols/)
has official resource: www.amqp.org

Access Policy
creator: sebastian
type: NamedIndividual
type: Concern
comment: Access to the service shall be regulated by access policies. Users entitled in access policies to envoke a given service must be able to actually envoke it.
see also: IoT-A Requirement UNI.604
supports: Data Access Control

Access Rights for IoT-Cloud
creator: Muhammad Usman
type: NamedIndividual
type: Concern
note: TODO what is the IoT Cloud?
has wikipedia article: Access rights
supports: Cloud Connectivity

Accountability
type: NamedIndividual
type: Concern
comment: A system built using the ARM shall support the reversing of the pseudonymization processes in order to guarantee mutual accountability
see also: IoT-A Requirement UNI.605

Actuation
creator: sebastian
type: NamedIndividual
type: Concern
comment: Sending data or a signal to a kind of actuating device, which leads to a change in a defined environment.
note: Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.1 THE CONTROL DOMAIN' 'Page 28'
has d bpedia resource: Actuator
supports: Internet of Things

Adaptability
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: Because of clients' need and time's requirements, there ought to be constant change in the system of associated devices for Internet of Things. Adaptability is continuously a need for survival and development of Internet of Things.
note: TODO merge with programmability or evolveability
has wikipedia article: Adaptability
supports: Internet of Things

Administration Shell
associated with: Trusted Connector
type: NamedIndividual
type: Standard Classification
type: Standarization Framework
comment: Represents the classifications of the standards according to the submodels of the administration shell.
has Publisher: Platform Industry 4.0
alignes With: Trusted Connector
frames: Lifecycle Status
frames: Availability
frames: Business Context
frames: Communication
frames: Data Access
frames: Dynamic Adjustability
frames: Endpoint Invocation
frames: Identification
frames: Identity Management
frames: Integrity Protection and Verification
frames: Interoperability
frames: Secure Communication
frames: Security
frames: Semantic Interoperability
frames: Service Choreography
frames: Service Composition
frames: Service Orchestration
frames: Syntactic Interoperability
frames: Thing description
frames: Thing representation
frames: Trustworthiness

Aeron
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: Aeron - Efficient reliable UDP unicast, UDP multicast, and IPC message transport. (source: https://www.postscapes.com/internet-of-things-protocols/)
has official resource: Aeron

Agility
type: NamedIndividual
type: Concern
comment: Agility as a key pillar that enables quick and astute business operational decisions for an OpenFog System. The predicted scale of the data generated by IoT means that it is highly unlikely that humans alone will be able to comprehend the data, derive knowledge and make wise decisions about how to best leverage their IoT assets for the benefit of their businesses. In the OpenFog architecture the agility pillar is about making sure that the valuable data generated in the IoT can be rapidly transformed into actionable insights that drive rapid decisions and further levels of automation to support business interest. Spurce: OpenFog Consortum Architecture Whitepaper
note: Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.7 Agility Pillar' 'Page 31'
supports: Business Context

Alliance of Industrial Internet Architecture Classification
creator: sebastian
type: Class
subclass of: Standard Classification

AII Data Classification
type: NamedIndividual
type: Alliance of Industrial Internet Architecture Classification
is Described in: AII Industrial Internet Architecture
alignes With: IDS RAM Information Layer
alignes With: InformationDomain
frames: Data Analytics
frames: Data Processing
frames: Data Collection
frames: Edge computing
frames: Semantic Interoperability

AiiDataAnno
type: NamedIndividual
type: oaAnnotation
oahas body: AII Data Classification
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 32
    oahas start selector: Page 25
  oahas source: Industrial Internet Architecture Version 1

AII Network Classification
type: NamedIndividual
type: Alliance of Industrial Internet Architecture Classification
is Described in: AII Industrial Internet Architecture
alignes With: IDS RAM System Layer
alignes With: IIRA Connectivity
alignes With: RAMI Communication Layer
alignes With: RAMI Integration Layer
frames: Communication
frames: Connectivity
frames: Identification
frames: Syntactic Interoperability

AiiNetworkAnno
type: NamedIndividual
type: oaAnnotation
oahas body: AII Network Classification
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 25
    oahas start selector: Page 10
  oahas source: Industrial Internet Architecture Version 1

AII Security Classification
type: NamedIndividual
type: Alliance of Industrial Internet Architecture Classification
is Described in: AII Industrial Internet Architecture
alignes With: IDS RAM Security Perspective
alignes With: IIRA Security
frames: Data Access
frames: Security

AiiSecurityAnno
type: NamedIndividual
type: oaAnnotation
oahas body: AII Security Classification
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 37
    oahas start selector: Page 32
  oahas source: Industrial Internet Architecture Version 1

AllSeen Alliance
creator: sebastian
type: NamedIndividual
type: Organization
type: IIoTConsortium
comment: The AllSeen Alliance is a nonprofit consortium dedicated to enabling and driving the widespread adoption of products, systems and services that support the Internet of Everything with an open, universal development framework supported by a vibrant ecosystem and thriving technical community' (source: https://www.postscapes.com/internet-of-things-protocols/)
has official resource: allseenalliance.org

Alliance Industrie du Futur
type: NamedIndividual
type: IIoTConsortium
has Headquater In: France
has official resource: www.industrie-dufutur.org

Alliance of Industrial Internet
type: NamedIndividual
type: IIoTConsortium
alternative label: 工业互联网产业联盟 @cn
has Headquater In: China
see also: www.aii-alliance.org

Alljoyn
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: Alljoyn - An open source software framework that makes it easy for devices and apps to discover and communicate with each other. (source: https://www.postscapes.com/internet-of-things-protocols/)
has official resource: framework

AnnoActuation
type: NamedIndividual
type: oaAnnotation
oahas body: Actuation
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 29
    oahas start selector: Page 28
  oahas source: The Industrial Internet of Things Volume G1: Reference Architecture IIC:PUB:G1:V1.80:20170131
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 29
    oahas start selector: Page 28
  oahas source: The Industrial Internet of Things Volume G1: Reference Architecture IIC:PUB:G1:V1.80:20170131

AnnoAiiClassification
type: NamedIndividual
type: oaAnnotation
oahas body: Alliance of Industrial Internet Architecture Classification
oahas target: oaSpecificResource
  format: pdf
  oahas source: Industrial Internet Architecture Version 1
oahas target: oaSpecificResource
  format: pdf
  oahas source: Industrial Internet Architecture Version 1

Anonymity
has stakeholder: EndUser
type: NamedIndividual
type: Concern
comment: Anonymity is the guarantee for a user to interact with a system without being tracked or connected to its real-world identity.
see also: IoT-A Requirement UNI.001
see also: IoT-A Requirement UNI.322
has d bpedia resource: Anonymity
has d bpedia resource: Anonymous web browsing
supports: Privacy

AoutonomousCommunication
see also: IoT-A Requirement UNI.247

Architecture Description
type: Class
comment: A Reference Architecture describes the structure of a system with its element types and their structures, as well as their interaction types, among each other and with their environment. Describing this, a Reference Architecture defines restrictions for an instantiation (concrete architecture). Through abstraction from individual details, a Reference Architecture is universally valid within a specific domain. Further architectures with the same functional requirements can be constructed based on the reference architecture. Along with reference architectures comes a recommendation, based on experiences from existing developments as well as from a wide acceptance and recognition by its users or per definition. [ISO/IEC42010] Note: It is important to distinguish the Reference Architecture from a Reference Architecture Description. While the first refers to a mental model or shared concept, the second is potentially only one of several different documents describing this model.
comment: ISO 42010 definition of an Architecture Description
subclass of: Standarization Framework

Arrowhead Framework
type: NamedIndividual
type: IIoTConsortium
type: Standarization Framework
has Publisher: Arrowhead Project
see also: www.arrowhead.eu

Arrowhead Project
type: NamedIndividual
type: Organization
see also: www.arrowhead.eu

Asset Management
creator: Priyanka
type: NamedIndividual
type: Concern
comment: The concern of being able to manage the system onboarding, configuration, policy, software/firmware updates and other lifecycle management operations.
note: Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.1 THE CONTROL DOMAIN' 'Page 29'
has wikipedia article: Physical and Infrastructure asset management
supports: Internet of Things

Authentication
creator: sebastian
type: NamedIndividual
type: Concern
comment: Authentication before opening a valid connection; this can be done by just verifying the server identity or doing mutual authentication.
see also: IoT-A Requirement UNI.612
see also: IoT-A Requirement UNI.618
supports: Identity Management

Authorization
type: NamedIndividual
type: Concern
see also: IoT-A Requirement UNI.319
see also: IoT-A Requirement UNI.502
see also: IoT-A Requirement UNI.503
supports: Privacy

Auto Scaling
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: Autoscaling, also spelled auto scaling or auto-scaling, and sometimes also called automatic scaling, is a method used in cloud computing, whereby the amount of computational resources in a server farm, typically measured in terms of the number of active servers, scales automatically based on the load on the farm. It is closely related to, and builds upon, the idea of load balancing.
note: TODO already covered by scalability?
has wikipedia article: Autoscaling
supports: Scalability

Autonomous Communication
has stakeholder: Q1548249
type: NamedIndividual
type: Concern
comment: Authonomous Communication frames all requirements in order to autonomously establish communication channels between participants of a network. In most cases, this will be a machine-to-machine communication channel. Main challenges are related to interoperability.
see also: IoT-A Requirement UNI.005
see also: IoT-A Requirement UNI.012
see also: IoT-A Requirement UNI.708
supports: Communication
supports: Service Choreography

Autonomous Configuration
has stakeholder: Q1548249
type: NamedIndividual
type: Concern
comment: A system built using the Reference Architecture shall be able to remotely control and configure devices.
see also: IoT-A Requirement UNI.015
see also: IoT-A Requirement UNI.031
see also: IoT-A Requirement UNI.032
see also: IoT-A Requirement UNI.060
see also: IoT-A Requirement UNI.247
see also: IoT-A Requirement UNI.509
see also: IoT-A Requirement UNI.704
see also: IoT-A Requirement UNI.706
see also: IoT-A Requirement UNI.717
note: Publications referred: '<https://doi.org/10.1016/j.jksuci.2016.10.003>' '1.2. Utilities of IoT' 'Page 295'
supports: Service Choreography

Availability
creator: sebastian
type: NamedIndividual
type: Concern
comment: In reliability theory and reliability engineering, the term availability has the following meanings: * The degree to which a system, subsystem or equipment is in a specified operable and committable state at the start of a mission, when the mission is called for at an unknown, i.e. a random, time. Simply put, availability is the proportion of time a system is in a functioning condition. This is often described as a mission capable rate. Mathematically, this is expressed as 100% minus unavailability. * The ratio of (a) the total time a functional unit is capable of being used during a given interval to (b) the length of the interval. For example, a unit that is capable of being used 100 hours per week (168 hours) would have an availability of 100/168. However, typical availability values are specified in decimal (such as 0.9998). In high availability applications, a metric known as nines, corresponding to the number of nines following the decimal point, is used. With this convention, "five nines" equals 0.99999 (or 99.999%) availability. (source: wikipedia)
see also: IoT-A Requirement UNI.058
see also: IoT-A Requirement UNI.064
see also: IoT-A Requirement UNI.239
see also: IoT-A Requirement UNI.321
see also: IoT-A Requirement UNI.601
see also: IoT-A Requirement UNI.610
see also: IoT-A Requirement UNI.616
note: Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.6 Reliability, Availability, and Serviceability (RAS)Pillar' 'Page 29'
has d bpedia resource: Availability
supports: Reliability

Awareness
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: Awareness is the ability to directly know and perceive, to feel, or to be cognizant of events. More broadly, it is the state of being conscious of something. Another definition describes it as a state wherein a subject is aware of some information when that information is directly available to bring to bear in the direction of a wide range of behavioral processes. The concept is often synonymous to consciousness and is also understood as being consciousness itself.
has wikipedia article: Awareness
supports: Edge computing

Big Data Value Association
type: NamedIndividual
type: Organization
alternative label: BDVA

Bandwidth
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: In computing, bandwidth is the maximum rate of data transfer across a given path. Bandwidth may be characterized as network bandwidth, data bandwidth, or digital bandwidth.
has wikipedia article: Bandwidth (computing)
supports: Communication

BDVA Cloud and High Performance Computing
creator: sebastian
associated with: IIRA Application Domain
type: NamedIndividual
type: BDVA Concern
type: Standard Classification
comment: The Cloud and High Performance Computing (HPC): Effective Big Data processing and data management might imply the effective usage of Cloud and High Performance Computing infrastructures. This area is separately elaborated further in collaboration with the Cloud and High Performance Computing (ETP4HPC) communities.
is Described in: BDVA Strategic Research and Innovation Agenda
alignes With: IIRA Application Domain
frames: Artificial Intelligence
frames: Big Data Applications
frames: Cloud Computing Capability
frames: Data Analytics
frames: Data Processing
frames: Data Publishing
frames: Machine Learning

BdvaCloudAndHighPerformanceComputingAnno
type: NamedIndividual
type: oaAnnotation
oahas body: BDVA Cloud and High Performance Computing
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017

BDVA Communication and Connectivity
creator: sebastian
type: NamedIndividual
type: BDVA Concern
type: Standard Classification
comment: Effective communication and connectivity mechanisms are necessary in providing support for Big Data. This area is separately further elaborated, along with various communication communities, such as the 5G community.
is Described in: BDVA Strategic Research and Innovation Agenda
frames: Communication
frames: Data Access
frames: Data Analytics
frames: Interoperability
frames: Quality of Service
frames: Semantic Interoperability
frames: Service Description

BdvaCommunicationConnectivityAnno
type: NamedIndividual
type: oaAnnotation
oahas body: BDVA Communication and Connectivity
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017

BDVA Concern
creator: sebastian
type: Class
type: NamedIndividual
type: class
comment: The BDV Reference Model distinguishes between two different elements. On the one hand, it describes the elements that are at the core of the BDVA; on the other, it outlines the features that are developed in strong collaboration with related European activities. The BDV Reference Model is structured into horizontal and vertical concerns. Horizontal concerns cover specific aspects along the data processing Vertical concerns address cross-cutting issues, which may affect all the horizontal concerns. In addition, vertical concerns may also involve non-technical aspects.
subclass of: Standard Classification
has official resource: BDVA SRIA v4 Ed1.1.pdf

BdvaConcernAnno
type: NamedIndividual
type: oaAnnotation
oahas body: BDVA Concern
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 38
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017

BDVA Cybersecurity and Trust
creator: sebastian
associated with: Security
associated with: IDS RAM Security Perspective
associated with: IIC Security Framework
type: NamedIndividual
type: BDVA Concern
type: Standard Classification
comment: Big Data often need support to maintain security and trust beyond privacy and anonymisation. The aspect of trust frequently has links to trust mechanisms such as blockchain technologies, smart contracts and various forms of encryption.
is Described in: BDVA Strategic Research and Innovation Agenda
alignes With: Security
alignes With: IDS RAM Security Perspective
alignes With: IIC Security Framework
frames: Communication
frames: Data Sovereignty
frames: Integrity Protection and Verification
frames: Privacy
frames: Secure Communication
frames: Security
frames: Trustworthiness

BdvaCyberSecurityTrustAnno
type: NamedIndividual
type: oaAnnotation
oahas body: BDVA Cybersecurity and Trust
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017

BDVA Data Analytics
creator: sebastian
associated with: IDS RAM Process Layer
associated with: InformationDomain
associated with: RAMI Functional Layer
associated with: RAMI Information Layer
type: NamedIndividual
type: BDVA Concern
type: Standard Classification
comment: Data analytics to improve data understanding, deep learning and the meaningfulness of data.
is Described in: BDVA Strategic Research and Innovation Agenda
alignes With: IDS RAM Process Layer
alignes With: InformationDomain
alignes With: RAMI Functional Layer
alignes With: RAMI Information Layer
frames: Artificial Intelligence
frames: Data Analytics
frames: Data Processing
frames: Machine Learning
frames: Stream processing
frames: Trustworthiness

BdvaDataAnalyticsAnno
type: NamedIndividual
type: oaAnnotation
oahas body: BDVA Data Analytics
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017

BDVA Data Management
creator: sebastian
associated with: IDS RAM Information Layer
associated with: IDS RAM Process Layer
associated with: RAMI Information Layer
type: NamedIndividual
type: BDVA Concern
type: Standard Classification
comment: Principles and techniques for data management
is Described in: BDVA Strategic Research and Innovation Agenda
alignes With: IDS RAM Information Layer
alignes With: IDS RAM Process Layer
alignes With: RAMI Information Layer
frames: Big Data Applications
frames: Data Quality
frames: Interoperability
frames: Provenance Tracking
frames: Security
frames: Semantic Interoperability
frames: Syntactic Interoperability
frames: Trustworthiness

BdvaDataManagementAnno
type: NamedIndividual
type: oaAnnotation
oahas body: BDVA Data Management
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017

BDVA Data Processing Architectures
creator: sebastian
associated with: IDS RAM Process Layer
associated with: IIRA Connectivity
associated with: InformationDomain
type: NamedIndividual
type: BDVA Concern
type: Standard Classification
comment: Optimised and scalable architectures for analytics of both data-at-rest and data-in-motion, with low latency delivering real-time analytics.
is Described in: BDVA Strategic Research and Innovation Agenda
alignes With: IDS RAM Process Layer
alignes With: IIRA Connectivity
alignes With: InformationDomain
frames: Big Data Applications
frames: Communication
frames: Data at rest
frames: DataInMotion
frames: Data Processing
frames: Scalability
frames: Stream processing

BdvaDataProcessingArchitecturesAnno
type: NamedIndividual
type: oaAnnotation
oahas body: BDVA Data Processing Architectures
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017

BDVA Data Protection
creator: sebastian
associated with: IDS RAM Security Perspective
associated with: IIC Security Framework
type: NamedIndividual
type: BDVA Concern
type: Standard Classification
comment: Privacy and anonymisation mechanisms to facilitate data protection. This is shown related to data management and processing as there is a strong link here, but it can also be associated with the area of cybersecurity.
is Described in: BDVA Strategic Research and Innovation Agenda
alignes With: IDS RAM Security Perspective
alignes With: IIC Security Framework
frames: Data Protection
frames: Data Sovereignty
frames: Privacy
frames: Trustworthiness

BdvaDataProtectionAnno
type: NamedIndividual
type: oaAnnotation
oahas body: BDVA Data Protection
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017

BDVA Data Sharing Platforms
creator: sebastian
associated with: Industrial Data Space Reference Architecture Model
associated with: Industrial Internet Reference Architecture
type: NamedIndividual
type: BDVA Concern
type: Standard Classification
comment: Data sharing and trading are seen as important ecosystem enablers in the data economy, although closed and personal data present particular challenges for the free flow of data. The following two conceptual solutions – Industrial Data Platforms (IDPs) and Personal Data Platforms (PDPs) – introduce new approaches to addressing this particular need to regulate closed proprietary and personal data.
is Described in: BDVA Strategic Research and Innovation Agenda
frames: Business Context
frames: Data Economy
frames: Data Publishing

BdvaDataSharingPlatformsAnno
type: NamedIndividual
type: oaAnnotation
oahas body: BDVA Data Sharing Platforms
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017

Data Visualisation and User Interaction
creator: sebastian
associated with: IIRA Usage Viewpoint
associated with: RAMI Functional Layer
type: NamedIndividual
type: BDVA Concern
type: Standard Classification
comment: Engineering and DevOps for building Big Data Value systems: This topic will be elaborated in greater detail along with the NESSI Software and Service community.
is Described in: BDVA Strategic Research and Innovation Agenda
alignes With: IIRA Usage Viewpoint
alignes With: RAMI Functional Layer
frames: Big Data Applications

BdvaDataVisualizationAndUserInteractionAnno
type: NamedIndividual
type: oaAnnotation
oahas body: Data Visualisation and User Interaction
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017

BDVA Engineering and DevOps
creator: sebastian
type: NamedIndividual
type: BDVA Concern
type: Standard Classification
comment: Engineering and DevOps for building Big Data Value systems: This topic will be elaborated in greater detail along with the NESSI Software and Service community.
is Described in: BDVA Strategic Research and Innovation Agenda

BdvaDevelopmentEngineeringAnno
type: NamedIndividual
type: oaAnnotation
oahas body: BDVA Engineering and DevOps
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017

BDVA Strategic Research and Innovation Agenda
creator: sebastian
type: NamedIndividual
type: Standarization Framework
comment: This Strategic Research and Innovation Agenda (SRIA) defines the overall goals, main technical and non-technical priorities, and a research and innovation roadmap for the European Public Private Partnership (PPP) on Big Data Value. The SRIA has been developed by the Big Data Value Association (BDVA), an industry-led organisation representing large businesses, small and medium-sized enterprises (SMEs), and research organisations in Europe.
label: BDVA SIRA
has Publisher: Big Data Value Association

BdvaSiraAnno
type: NamedIndividual
type: oaAnnotation
oahas body: BDVA Strategic Research and Innovation Agenda
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 106
    oahas start selector: Page 1
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 106
    oahas start selector: Page 1
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017

BDVA Standards
creator: sebastian
type: NamedIndividual
type: BDVA Concern
type: Standard Classification
comment: Standardisation of Big Data technology areas to facilitate data integration, sharing and interoperability
is Described in: BDVA Strategic Research and Innovation Agenda
frames: Business Context
frames: Communication
frames: Data Economy
frames: Interoperability

BdvaStandardsAnno
type: NamedIndividual
type: oaAnnotation
oahas body: BDVA Standards
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017

BDVA IoT CPS and Edge Computing
creator: sebastian
type: NamedIndividual
type: BDVA Concern
type: Standard Classification
comment: IoT, CPS, Edge and Fog Computing: A main source of Big Data is sensor data from an IoT context and actuator interaction in Cyber Physical Systems. In order to meet real-time needs it will often be necessary to handle Big Data aspects at the edge of the system. This area is separately elaborated further in collaboration with the IoT (Alliance for Internet of Things Innovation (AIOTI)) and CPS communities
is Described in: BDVA Strategic Research and Innovation Agenda
frames: Internet of Things

BdvaThingsAssetsSensorsActuatorsAnno
type: NamedIndividual
type: oaAnnotation
oahas body: BDVA IoT CPS and Edge Computing
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 37
  oahas source: BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017

Big Data Applications
type: NamedIndividual
type: Concern
comment: Big data is a term for data sets that are so large or complex that traditional data processing applications are inadequate to deal with them. Challenges include analysis, capture, data curation, search, sharing, storage, transfer, visualization, querying, updating and information privacy. The term "big data" often refers simply to the use of predictive analytics, user behavior analytics, or certain other advanced data analytics methods that extract value from data, and seldom to a particular size of data set. (source: wikipedia)
has d bpedia resource: Big data
supports: Data Analytics

Blockchain
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: The term Blockchain refers to a set of technologies for distributed databases.
has d bpedia resource: Blockchain.info

Bluetooth
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: Bluetooth works in the 2.4 GHz ISM band and uses frequency hopping. With a data rate up to 3 Mbps and maximum range of 100m. Each application type which can use Bluetooth has its own profile. (source: https://www.postscapes.com/internet-of-things-protocols/)
has Classification: RAMICommunicationLayer
has official resource: Bluetooth-Home.aspx

Business Context
creator: sebastian
type: NamedIndividual
type: Concern
comment: Electronic business, or e-business, is the application of information and communication technologies in support of all the activities of business. Commerce constitutes the exchange of products and services between businesses, groups and individuals and can be seen as one of the essential activities of any business. (source: wikipedia)
has d bpedia resource: Electronic business

Business Cycle SCM
type: Class
comment: Suply Chain Management Business Cycle.
subclass of: Standard Classification

Business Manager
comment: A business manager is responsible for the running of the business and to make large profits.
note: Publications referred: 'IIC:PUB:G1:V1.80:20170131' '1.5 AUDIENCE' 'Page 7'
has wikipedia article: Business manager

Business process management
type: NamedIndividual
type: Concern
comment: Business process management (BPM) is a field in operations management that focuses on improving corporate performance by managing and optimizing a company's business processes. It can therefore be described as a "process optimization process." It is argued that BPM enables organizations to be more efficient, more effective and more capable of change than a functionally focused, traditional hierarchical management approach. These processes can impact the cost and revenue generation of an organization. As a policy-making approach, BPM sees processes as important assets of an organization that must be understood, managed, and developed to announce value-added products and services to clients or customers. This approach closely resembles other total quality management or continual improvement process methodologies and BPM proponents also claim that this approach can be supported, or enabled, through technology. As such, many BPM articles and scholars frequently discuss BPM from one of two viewpoints: people and/or technology. (source: wikipedia)
label: BPM
see also: IoT-A Requirement UNI.211
see also: IoT-A Requirement UNI.212
see also: IoT-A Requirement UNI.214
see also: IoT-A Requirement UNI.215
see also: IoT-A Requirement UNI.229
has d bpedia resource: Business process management
supports: Business Context

Business Transactions
creator: sebastian
type: NamedIndividual
type: Concern
comment: A financial transaction is an agreement, communication, or movement carried out between a buyer and a seller to exchange an asset for payment. It involves a change in the status of the finances of two or more businesses or individuals. The buyer and seller are separate entities or objects, often involving the exchange of items of value, such as information, goods, services, and money. It is still a transaction if the goods are exchanged at one time, and the money at another. This is known as a two-part transaction: part one is giving the money, part two is receiving the goods. (source: wikipedia)
has d bpedia resource: Financial transaction
supports: Business Context

Business Value
creator: sebastian
type: NamedIndividual
type: Concern
note: Publications referred: '(IIC:PUB:G1:V1.80:20170131' '4 BUSINESS VIEWPOINT' 'Page 20'
supports: Business Context

Cardinality of Participants
creator: sebastian
type: NamedIndividual
type: Concern
comment: Data Artefacts from different Data Providers are delivered in order to provide additional insights (e.g. Collaborative Predictive Maintenance).
has d bpedia resource: Cardinality (computer engineering)
supports: interoperability

Certification
creator: sebastian
type: NamedIndividual
type: Concern
comment: Certification refers to the confirmation of certain characteristics of an object, person, or organization. This confirmation is often, but not always, provided by some form of external review, education, assessment, or audit. Accreditation is a specific organization's process of certification. (source: wikipedia)
has d bpedia resource: Certification
supports: Security
supports: Trustworthiness

Cloud Computing Capability
creator: sebastian
is part of: Data Processing
type: NamedIndividual
type: Concern
comment: Cloud computing is a type of Internet-based computing that provides shared computer processing resources and data to computers and other devices on demand. It is a model for enabling ubiquitous, on-demand access to a shared pool of configurable computing resources (e.g., computer networks, servers, storage, applications and services), which can be rapidly provisioned and released with minimal management effort. Cloud computing and storage solutions provide users and enterprises with various capabilities to store and process their data in third-party data centers that may be located far from the user–ranging in distance from across a city to across the world. Cloud computing relies on sharing of resources to achieve coherence and economy of scale, similar to a utility (like the electricity grid) over an electricity network. (source: wikipedia)
see also: IoT-A Requirement UNI.102
see also: IoT-A Requirement UNI.234
has d bpedia resource: Cloud computing

Communication
type: NamedIndividual
type: Admin Shell Sub Model
type: Concern
type: Standard Classification
see also: IoT-A Requirement UNI.021
see also: IoT-A Requirement UNI.095
see also: IoT-A Requirement UNI.303
see also: IoT-A Requirement UNI.306
see also: IoT-A Requirement UNI.307
see also: IoT-A Requirement UNI.308
see also: IoT-A Requirement UNI.309
see also: IoT-A Requirement UNI.310
see also: IoT-A Requirement UNI.311
see also: IoT-A Requirement UNI.312
see also: IoT-A Requirement UNI.313
see also: IoT-A Requirement UNI.315
see also: IoT-A Requirement UNI.318
see also: IoT-A Requirement UNI.321
see also: IoT-A Requirement UNI.324
see also: IoT-A Requirement UNI.716
is Described in: Administration Shell
supports: Interoperability

Complex Event Processing
type: NamedIndividual
type: Concern
comment: Event processing is a method of tracking and analyzing (processing) streams of information (data) about things that happen (events), and deriving a conclusion from them. Complex event processing, or CEP, is event processing that combines data from multiple sources to infer events or patterns that suggest more complicated circumstances. The goal of complex event processing is to identify meaningful events (such as opportunities or threats) and respond to them as quickly as possible. (source: wikipedia)
label: CEP
see also: IoT-A Requirement UNI.232
has d bpedia resource: Complex event processing
supports: Data Analytics

Compliance
creator: sebastian
type: NamedIndividual
type: Concern
comment: In general, compliance means conforming to a rule, such as a specification, policy, standard or law. Regulatory compliance describes the goal that organisations aspire to achieve in their efforts to ensure that they are aware of and take steps to comply with relevant laws and regulations. Due to the increasing number of regulations and need for operational transparency, organizations are increasingly adopting the use of consolidated and harmonized sets of compliance controls. This approach is used to ensure that all necessary governance requirements can be met without the unnecessary duplication of effort and activity from resources. (source: wikipedia)
has d bpedia resource: Regulatory compliance
supports: Reliability

Concern
creator: sebastian
type: Class
type: NamedIndividual
comment: A concern regards a specific challenge or topic as defined by ISO42010. Each concern should at least be regarded by one view of an architecture.
has d bpedia resource: IEC_42010
has official resource: http://www.iso-architecture.org/42010/
has wikipedia article: Conceptual Model - Concern

Confidentiality
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: Confidentiality involves a set of rules or a promise usually executed through confidentiality agreements that limits access or places restrictions on certain types of information.
has wikipedia article: Confidentiality
supports: Privacy

Connectivity
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: Internet of Things associates various smart devices through the Internet, and it gives a facility to concentrated checking and control of associated equipment.
has d bpedia resource: connectivity
has wikipedia article: Connectivity
supports: Syntactic Interoperability

Connectivity Layer
type: Class
comment: Connectivity Layer of the Internet Connectivity Framework
subclass of: Standard Classification

Constrained Devices
creator: sebastian
has stakeholder: System Architect TODO
type: NamedIndividual
type: Concern
comment: Data-memory-constrained devices must be able to participate in communication. This means that a system built using the ARM shall support communication stacks with small data footprint.
comment: Small devices with limited CPU, memory, and power resources, so-called "constrained devices" (often used as sensors/actuators, smart objects, or smart devices) can form a network, becoming "constrained nodes" in that network. Such a network may itself exhibit constraints, e.g., with unreliable or lossy channels, limited and unpredictable bandwidth, and a highly dynamic topology. (source: https://tools.ietf.org/html/rfc7228)
see also: IoT-A Requirement UNI.306
see also: IoT-A Requirement UNI.307
supports: Internet of Things

Context Awareness
has stakeholder: Developer
type: NamedIndividual
type: Concern
comment: The look-up service of the system shall withold or grant information depending on context. Context includes application involved, requesting entity, and security permissions.
see also: IoT-A Requirement UNI.407
see also: IoT-A Requirement UNI.420
see also: IoT-A Requirement UNI.421
note: Publications referred: '<https://doi.org/10.1016/j.jksuci.2016.10.003>' '1.2. Utilities of IoT' 'Page 296'
has d bpedia resource: Context awareness
supports: Autonomous Communication

Cost Efficiency
creator: SebastianBader
type: NamedIndividual
type: Concern
label: DataRecovery
supports: Business Context

Cross-domain Identity Management
creator: sebastian
has stakeholder: System Architect
type: NamedIndividual
type: Concern
comment: A system built using the ARM shall support identity-locator split, i.e. making the device's identity independent from its locator.
see also: IoT-A Requirement UNI.314
has d bpedia resource: System for Cross-domain Identity Management
supports: Identity Management

Customization
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: The resources sharing by contrasting users keeps cloud service provider from having the capacity to customize their services to meet the diverse necessities of customers
has wikipedia article: Customization
supports: Business Context
supports: Scalability

DIN 77005-1:2018-09
type: NamedIndividual
type: Standard
frames: Data lifecycle management

DIN EN 50129
type: NamedIndividual
type: Standard
has Classification: IDS RAM Certification Perspective
has Target Concern: Safety

DIN EN 50155
type: NamedIndividual
type: Standard
has Classification: IDS RAM Certification Perspective
has Target Concern: Safety

DIN EN 61511
type: NamedIndividual
type: Standard
has Classification: IDS RAM Certification Perspective
has Target Concern: Safety

Data Access
creator: sebastian
type: NamedIndividual
type: Concern
comment: Data access typically refers to software and activities related to storing, retrieving, or acting on data housed in a database or other repository. [...] Data access crucially involves authorization to access different data repositories. (source: wikipedia)
see also: IoT-A Requirement UNI.022
has d bpedia resource: Data access

Data Access Control
creator: sebastian
has stakeholder: EndUser
has stakeholder: DataOwner
type: NamedIndividual
type: Concern
comment: Automated access control based on formalized descriptions.
comment: In the fields of physical security and information security, access control (AC) is the selective restriction of access to a place or other resource. The act of accessing may mean consuming, entering, or using. Permission to access a resource is called authorization. Locks and login credentials are two analogous mechanisms of access control. (source: wikipedia)
see also: IoT-A Requirement UNI.002
see also: IoT-A Requirement UNI.067
see also: IoT-A Requirement UNI.410
see also: IoT-A Requirement UNI.411
see also: IoT-A Requirement UNI.412
see also: IoT-A Requirement UNI.413
see also: IoT-A Requirement UNI.504
has d bpedia resource: Access control
supports: Authorization

Data Aggregation
type: NamedIndividual
type: Concern
comment: Data Aggregation is the compiling the data before Data Processing
narrower: Data Processing
has wikipedia article: Data aggregation

Data Analytics
creator: sebastian
type: NamedIndividual
type: Concern
comment: Analysis of data is a process of inspecting, cleaning, transforming, and modeling data with the goal of discovering useful information, suggesting conclusions, and supporting decision-making. Data analysis has multiple facets and approaches, encompassing diverse techniques under a variety of names, in different business, science, and social science domains. Data mining is a particular data analysis technique that focuses on modeling and knowledge discovery for predictive rather than purely descriptive purposes. Business intelligence covers data analysis that relies heavily on aggregation, focusing on business information. (source: wikipedia)
see also: IoT-A Requirement UNI.232
has d bpedia resource: Data analysis

Data at rest
creator: sebastian
type: NamedIndividual
type: Concern
comment: Data at rest in information technology means inactive data that is stored physically in any digital form (e.g. databases, data warehouses, spreadsheets, archives, tapes, off-site backups, mobile devices etc.). Data at rest is used as a complement to the terms data in use and data in transit which together define the three states of digital Data. (source: wikipedia)
has d bpedia resource: Data at rest
supports: Communication

Data Description
creator: sebastian
has stakeholder: developer
type: NamedIndividual
type: Concern
comment: Data model
comment: Methods to unambiguously describe data resources.
see also: IoT-A Requirement UNI.004
see also: IoT-A Requirement UNI.240
supports: Semantic Interoperability

Data Discovery
creator: sebastian
type: NamedIndividual
type: Concern
comment: How to find desired resources, Data Assets, Data Artifacts in a defined environment.
see also: IoT-A Requirement UNI.236
see also: IoT-A Requirement UNI.408
see also: IoT-A Requirement UNI.422
supports: Interoperability

Data Economy
creator: sebastian
type: NamedIndividual
type: Concern
comment: Business aspects of data exchange
comment: Digital economy refers to an economy that is based on digital computing technologies. The digital economy is also sometimes called the Internet Economy, the New Economy, or Web Economy. Increasingly, the "digital economy" is intertwined with the traditional economy making a clear delineation harder. (source: wikipedia)
has d bpedia resource: Digital economy
supports: Business Context

Customization
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: The resources sharing by contrasting users keeps cloud service provider from having the capacity to customize their services to meet the diverse necessities of customers
label: Data secrecy and encryption
has wikipedia article: Customization
has wikipedia article: Encryption
supports: Business Context
supports: Secure Communication

Data Integrity
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: Data integrity is the maintenance of, and the assurance of the accuracy and consistency of, data over its entire life-cycle, and is a critical aspect to the design, implementation and usage of any system which stores, processes, or retrieves data.
has wikipedia article: Data integrity
supports: Privacy

Data Isolation
type: NamedIndividual
type: Concern
comment: Isolation is one of the ACID (Atomicity, Consistency, Isolation, Durability) properties adopted by the database systems
narrower: Isolation
has wikipedia article: Isolation (database systems)
supports: Data Integrity

DataLifecycleManagement
see also: IoT-A Requirement UNI.097

Data lifecycle management
type: NamedIndividual
type: Concern
comment: Data lifecycle management includes every phase of a "record" from its beginning to its end. And while it is generally applied to information that rises to the classic definition of a record (and thus related to records management), it applies to all informational assets. During its existence, information can become a record by being identified as documenting a business transaction or as satisfying a business need. (source: wikipedia)
has d bpedia resource: Information lifecycle management
supports: Data Analytics

Data Location
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: One of the features of cloud computing is geodistribution of data among several servers. But this can be an issue for the enterprise, as the location of the data is unknown to the user.
supports: Data Usage Control

Data Market Austria
creator: sebastian
type: NamedIndividual
type: Organization
type: Data Sharing Initiative
type: StandardOrganization
label: DMA
has official resource: www.datamarket.at

Data Markets
creator: sebastian
type: NamedIndividual
type: Concern
comment: Data as an economic good; it's offered, demanded, and priced.
supports: Data Economy

Data Ownership
creator: sebastian
type: NamedIndividual
type: Concern
comment: Data Ownership declare the possesion on an information resource that is independent of its location, e.g. personal data belongs to the related person no matter where it is stored.
has d bpedia resource: Data ownership
supports: Privacy

Data Processing
creator: sebastian
has stakeholder: Q1548249
type: NamedIndividual
type: Concern
comment: Data processing and analytic components from the App Store create flexible data processing pipelines.
see also: IoT-A Requirement UNI.018
has d bpedia resource: Data processing

Data Protection
creator: sebastian
type: NamedIndividual
type: Concern
comment: Data protection is the relationship between collection and dissemination of data, technology, the public expectation of privacy, and the legal and political issues surrounding them. Privacy concerns exist wherever personally identifiable information or other sensitive information is collected, stored, used, and finally destroyed or deleted – in digital form or otherwise. Improper or non-existent disclosure control can be the root cause for privacy issues. (source: wikipedia)
alternative label: Datenschutz @de
alternative label: Information privacy
has d bpedia resource: Information privacy
supports: Privacy

Data Publishing
creator: sebastian
type: NamedIndividual
type: Concern
comment: Data Publishing is the concern regarding all aspects of getting data (publicly) available.
supports: Data Access Control

Data Quality
creator: sebastian
type: NamedIndividual
type: Concern
comment: Data quality refers to the level of quality of data. There are many definitions of data quality but data are generally considered high quality if "they are fit for their intended uses in operations, decision making and planning." (Tom Redman<Redman, T.C. (2008). Data driven: Profiting from your most important business asset (p. 56). Boston, Mass.: Harvard Business Press.>). Alternatively, data is deemed of high quality if it correctly represents the real-world construct to which it refers. Furthermore, apart from these definitions, as data volume increases, the question of internal consistency within data becomes significant, regardless of fitness for use for any particular external purpose. People's views on data quality can often be in disagreement, even when discussing the same set of data used for the same purpose. (source: wikipedia)
see also: IoT-A Requirement UNI.235
see also: IoT-A Requirement UNI.236
see also: IoT-A Requirement UNI.237
has d bpedia resource: Data quality
supports: Quality of Service

Data Sharing Initiative
creator: sebastian
type: Class
type: NamedIndividual
comment: This class frames all organizations with the main intend to create, specify and implement a data sharing concept with according interfaces, components, data descriptions, and retrieval algorithms.
subclass of: Organization

Data Sovereignty
creator: sebastian
type: NamedIndividual
type: Concern
type: Standard Classification
has d bpedia resource: Cyber sovereignty
has wikipedia article: Data sovereignty

Data Storage
creator: Muhammad Usman
creator: sebastian
type: NamedIndividual
type: Concern
comment: The IoT data are collected from various data sources in different structures and formats. IoT enables the collected data to be stored both in physical devices and cloud storage.
has wikipedia article: Data storage
supports: Data Processing

Data Transfer Project
creator: sebastian
associated with: Data Transfer Project Architecture
type: NamedIndividual
type: Organization
type: Data Sharing Initiative
comment: The Data Transfer Project (DTP) extends data portability beyond a user’s ability to download a copy of their data from their service provider (“provider”), to providing the user the ability 1 to initiate a direct transfer of their data into and out of any participating provider. The Data Transfer Project is an open source initiative to encourage participation of as many providers as possible. The DTP will enhance the data portability ecosystem by reducing the infrastructure burden on both providers and users, which should in turn increase the number of services offering portability. The protocols and methodology of the DTP enable direct, service-to-service data transfer with streamlined engineering work.
has official resource: data-transfer-project

Data Transfer Project Whitepaper
creator: Data Transfer Project
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
comment: The Data Transfer Project Whitepaper provides a brief overview on the intends of the Data Transfer Project and the targeted approach.
maker: Data Transfer Project
has Classification: DTP Deployment
has Classification: DTP Ecosystem
has Classification: DTP Security & Privacy
has Classification: DTP System
has d bpedia resource: Data Transfer Project
has Developer: Data Transfer Project
has Publisher: Data Transfer Project
has wikipedia article: Data Transfer Project
has Target Concern: Data Sovereignty
has Target Concern: Identity Management
has Target Concern: Privacy
has Target Concern: Secure Communication
has Target Concern: User Preferences

Data Usage Control
creator: sebastian
type: NamedIndividual
type: Concern
comment: Data usage control can be seen as an extension of data access control. It is about the specification and enforcement of restrictions regulating what is allowed to happen with data, and what is not. Data usage control thus is concerned with requirements that pertain to data processing (obligations) rather than data access (provisions). It is primarily relevant in the context of intellectual property protection, privacy protection, compliance with regulations, and digital rights management.
supports: Authorization

Data Collection
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: The data in IoT are always mass, distributed, and time-related and position related. At the same time, the data sources of the IoT are heterogeneous. There is a vast amount of real-time data collected by the IoT devices.
has d bpedia resource: Data collection
has wikipedia article: Data collection
supports: Data Analytics

Data Confidentiality
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: In edge computing, user private data is outsourced to the edge server and its ownership and control are separated, which causes users to lose their physical control over the outsourced data.
supports: Privacy

Data Transfer Project Overview and Fundamentals
type: NamedIndividual
type: oaSpecificResource
has open resource: dtp-overview.pdf

Decision maker
type: NamedIndividual
type: Layer
comment: These are business Decision makers
note: Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.1 BUSINESS VIEWPOINT' 'Page 15' 'Priyanka'

Device Security
creator: SebastianBader
type: NamedIndividual
type: Concern
narrower: Security
supports: Objects Safety and Security

Device Authentication
creator: Muhammad Usman
type: NamedIndividual
type: Concern
has wikipedia article: Authentication
supports: Authentication

DMA Architecture
creator: sebastian
type: NamedIndividual
type: Architecture Description
type: Standarization Framework
has Publisher: Data Market Austria

DMA Service Technology Specification and Development Roadmap
creator: Data Market Austria
associated with: Blockchain
associated with: REST
associated with: RFC 6750
type: NamedIndividual
type: Document
type: Publication
type: Standarization Framework
comment: This document presents the DMA Data Technology Specification and Development Roadmap regarding the ongoing work in WP6 of the DMA project. The document relates to deliverable D2.2 “D2.2 Community-driven Data-Services Ecosystem Requirements (1st version)” which formulates the requirements of the DMA community. It will be explained in what way the requirements formulated in D2.2 are going to be addressed. The document gives an overview about the components which are going to be developed in WP6 and how these components are planned to be employed to provide DMA core services. The expected outputs of these services are described and a procedure of describing a 3rd party service for DMA platform is addressed.
maker: Data Market Austria
has official resource: DMA Deliverable D6.1 FINAL v01.pdf
has Publisher: Data Market Austria
has Target Concern: Authentication
has Target Concern: Authorization
has Target Concern: Big Data Applications
has Target Concern: Billing
has Target Concern: Cloud Computing Capability
has Target Concern: Data Access
has Target Concern: Data Quality
has Target Concern: Privacy
has Target Concern: Secure Communication
has Target Concern: Security
has Target Concern: Semantic Interoperability
has Target Concern: Stream processing
has Target Concern: Syntactic Interoperability
has Target Concern: Trustworthiness

Domain
type: Class
comment: Represents the Domains in which the Standards can be used

Data Transfer Project Architecture
creator: sebastian
type: NamedIndividual
type: Architecture Description
type: Standarization Framework
comment: The architecture description of the Data Transfer Project has not yet been published in a sufficient manner.
has Publisher: Data Transfer Project

DTP Deployment
associated with: IDS RAM Process Layer
associated with: IIRA Implementation Viewpoint
type: NamedIndividual
type: Standard Classification
type: Viewpoint
is Described in: Data Transfer Project Architecture
alignes With: IDS RAM Process Layer
alignes With: IIRA Implementation Viewpoint
frames: Identification
frames: Identity Management
frames: Security
frames: Service Deployment
frames: Service life-cycle management
frames: Trustworthiness
frames: User Interaction

DTP Ecosystem
associated with: IDS RAM Governance Perspective
associated with: IIRA Usage Viewpoint
type: NamedIndividual
type: Standard Classification
type: Viewpoint
is Described in: Data Transfer Project Architecture
alignes With: IDS RAM Governance Perspective
alignes With: IIRA Usage Viewpoint

DTP Security & Privacy
associated with: Security
associated with: IDS RAM Governance Perspective
associated with: IIRA Privacy
associated with: IIRA Security
type: NamedIndividual
type: Standard Classification
type: Viewpoint
is Described in: Data Transfer Project Architecture
alignes With: Security
alignes With: IDS RAM Governance Perspective
alignes With: IIRA Privacy

DTP System
associated with: IDS RAM System Layer
associated with: IIRA Connectivity
associated with: IIRA Operation Domain
associated with: InformationDomain
associated with: RAMI Functional Layer
associated with: RAMI Integration Layer
associated with: RFC 6750
type: NamedIndividual
type: Standard Classification
type: Viewpoint
is Described in: Data Transfer Project Architecture
alignes With: IDS RAM System Layer
alignes With: IIRA Connectivity
alignes With: IIRA Operation Domain
alignes With: InformationDomain
alignes With: RAMI Functional Layer
alignes With: RAMI Integration Layer
frames: Authentication
frames: Communication
frames: Data Access
frames: Interoperability
frames: Secure Communication
frames: Security
frames: Semantic Interoperability
frames: Syntactic Interoperability
frames: Trustworthiness

Dynamic Adjustability
type: NamedIndividual
type: Concern
comment: A systems ability to adjust its behaviour on dynamic changes in its environment.
see also: IoT-A Requirement UNI.713
supports: Service Choreography
supports: Service Composition
supports: Service Orchestration

Dynamic Discovery
type: NamedIndividual
type: Concern
comment: A systems ability to retrive according information on required assets and components on-the-fly.
see also: IoT-A Requirement UNI.418
see also: IoT-A Requirement UNI.419
see also: IoT-A Requirement UNI.420
see also: IoT-A Requirement UNI.421
supports: Data Discovery
supports: Service Discovery

Edge Analytics
creator: Priyanka
type: NamedIndividual
type: Concern
comment: The concern of being able to understanding the states, conditions and behaviors of the systems under control and other systems by interpreting and correlating data gathered from sensors and other systems.
narrower: Analytics
note: Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.1 THE CONTROL DOMAIN' 'Page 29'
has wikipedia article: Edge computing

Edge computing
type: NamedIndividual
type: Concern
comment: Edge Computing is pushing the frontier of computing applications, data, and services away from centralized nodes to the logical extremes of a network. It enables analytics and knowledge generation to occur at the source of the data. This approach requires leveraging resources that may not be continuously connected to a network such as laptops, smartphones, tablets and sensors. Edge Computing covers a wide range of technologies including wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer-to-peer ad hoc networking and processing also classifiable as Local Cloud/Fog computing and Grid/Mesh Computing, dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented reality, and more. (source: wikipedia)
has d bpedia resource: Edge computing
supports: Cloud Computing Capability
supports: Data Processing

Edgecross Architecture
type: NamedIndividual
type: Architecture Description
type: Standarization Framework
has Publisher: Edgecross Consortium

Edgecross Consortium
type: NamedIndividual
type: Organization
type: IIoTConsortium
type: StandardOrganization
has official resource: en

Edgecross Edgecomputing Layer
associated with: IDS RAM System Layer
associated with: IIRA Control Domain
associated with: IIRA Operation Domain
associated with: InformationDomain
associated with: RAMI Information Layer
associated with: RAMI Integration Layer
type: NamedIndividual
type: Edgecross Layer
type: Standard Classification
is Described in: Edgecross Architecture
alignes With: IDS RAM System Layer
alignes With: IIRA Control Domain
alignes With: IIRA Operation Domain
alignes With: InformationDomain
alignes With: RAMI Information Layer
alignes With: RAMI Integration Layer
frames: Cloud Computing Capability
frames: Data Processing
frames: Edge computing
frames: Interoperability
frames: Semantic Interoperability

EdgecrossEdgeComputingLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: Edgecross Edgecomputing Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 15
    oahas start selector: Page 9
  oahas source: Edgecross Consortium to Address Edge Integration in IIoT-enabled Architectures
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 15
    oahas start selector: Page 9
  oahas source: Edgecross Consortium to Address Edge Integration in IIoT-enabled Architectures

Edgecross FA
associated with: IIRA Physical Systems
associated with: RAMI Asset Layer
type: NamedIndividual
type: Edgecross Layer
type: Standard Classification
is Described in: Edgecross Architecture
alignes With: IIRA Physical Systems
alignes With: RAMI Asset Layer

EdgecrossFacilityLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: Edgecross FA
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 15
    oahas start selector: Page 9
  oahas source: Edgecross Consortium to Address Edge Integration in IIoT-enabled Architectures
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 15
    oahas start selector: Page 9
  oahas source: Edgecross Consortium to Address Edge Integration in IIoT-enabled Architectures

Edgecross IT Systems Layer
associated with: IDS RAM System Layer
associated with: IIRA Application Domain
associated with: RAMI Integration Layer
type: NamedIndividual
type: Edgecross Layer
type: Standard Classification
is Described in: Edgecross Architecture
alignes With: IDS RAM System Layer
alignes With: IIRA Application Domain
alignes With: RAMI Integration Layer
frames: Communication
frames: Data Analytics
frames: DataInMotion

EdgecrossItSystemsLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: Edgecross IT Systems Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 15
    oahas start selector: Page 9
  oahas source: Edgecross Consortium to Address Edge Integration in IIoT-enabled Architectures
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 15
    oahas start selector: Page 9
  oahas source: Edgecross Consortium to Address Edge Integration in IIoT-enabled Architectures

Edgecross Layer
type: Class
subclass of: Standard Classification
subclass of: Restriction
  has value: Edgecross Architecture
  on property: is Described in

EdgecrossLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: Edgecross Layer
oahas target: oaSpecificResource
  format: pdf
  oahas source: Edgecross Consortium to Address Edge Integration in IIoT-enabled Architectures
oahas target: oaSpecificResource
  format: pdf
  oahas source: Edgecross Consortium to Address Edge Integration in IIoT-enabled Architectures

Edgecross Whitepaper
creator: Edgecross Consortium
type: NamedIndividual
type: Document
type: Publication
maker: Edgecross Consortium
has Classification: Edgecross Edgecomputing Layer
has Classification: Edgecross FA
has Classification: Edgecross IT Systems Layer
has official resource: Edgecross Consortium WP(E).pdf
has Publisher: Edgecross Consortium
has Target Concern: Edge computing
has Target Concern: Interoperability

Edgecross Consortium to Address Edge Integration in IIoT-enabled Architectures
type: NamedIndividual
type: oaSpecificResource
has open resource: Edgecross Consortium WP(E).pdf

Endpoint Description
creator: sebastian
type: NamedIndividual
type: Concern
comment: Methods to unambiguously describe client and server endpoints.
supports: Semantic Interoperability

Endpoint Invocation
creator: sebastian
type: NamedIndividual
type: Concern
comment: Mechanisms to interact with a service and to access it through the network.
see also: IoT-A Requirement UNI.100
see also: IoT-A Requirement UNI.417
supports: Syntactic Interoperability

Energy Control
type: NamedIndividual
type: Concern
see also: IoT-A Requirement UNI.100
see also: IoT-A Requirement UNI.101
see also: IoT-A Requirement UNI.309
see also: IoT-A Requirement UNI.310
see also: IoT-A Requirement UNI.505
see also: IoT-A Requirement UNI.512
see also: IoT-A Requirement UNI.714
has wikipedia article: Energy management
supports: Energy Efficiency

Energy Efficiency
type: NamedIndividual
type: Admin Shell Sub Model
type: Concern
type: Standard Classification
comment: Efficient energy use, sometimes simply called energy efficiency, is the goal to reduce the amount of energy required to provide products and services.
has wikipedia article: Efficient energy use
is Described in: Administration Shell
supports: Internet of Things

BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017
type: NamedIndividual
type: oaSpecificResource
has open resource: BDVA SRIA v4 Ed1.1.pdf

Event-Driven Messaging
has stakeholder: Q1548249
type: NamedIndividual
type: Concern
see also: IoT-A Requirement UNI.005
see also: IoT-A Requirement UNI.233
has d bpedia resource: Event-Driven Messaging
supports: DataInMotion

Evolvability
creator: sebastian
type: NamedIndividual
type: Concern
comment: A system shall accomodate fast developmental changes in applications and network.
see also: IoT-A Requirement UNI.701
see also: IoT-A Requirement UNI.702
has d bpedia resource: Evolving intelligent system
has d bpedia resource: Software evolution
supports: Dynamic Adjustability

Execution Variability
creator: sebastian
type: NamedIndividual
type: Concern
comment: The system's ability to flexibly connect/adjust data flows in order to reach a defined target.

Extensibility
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: "Extensibility could be a huge challenge at the edge of the network, unlike a mobile system, the things in the IoT could be very dynamic. When the owner purchases a new thing, can it be easily added to the current service without any problem? Or when one thing is replaced due to wearing out, can the previous service adopt a new node easily? These problems should be solved with a flexible and extensible design of service management layer in the edgeOS."
has wikipedia article: Extensibility
supports: Evolvability

FIWARE Architecture
creator: sebastian
associated with: IDS RAM System Layer
associated with: IIRA Implementation Viewpoint
type: NamedIndividual
type: Architecture Description
type: Standarization Framework
comment: The FIWARE platform contains market-ready open source software, combining components that enable the connection to IoT with Context Information Management and Big Data services in the Cloud.
has official resource: www.fiware.org
has Publisher: FIWARE
alignes With: IDS RAM System Layer
alignes With: IIRA Implementation Viewpoint

Fairness
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: How can a fair and non-discriminating access to (compute and storage) resources be established?
has wikipedia article: Fairness
supports: Business Context

Fault Tolerance
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: Fault tolerance is the property that enables a system to continue operating properly in the event of the failure of some (one or more faults within) of its components. If its operating quality decreases at all, the decrease is proportional to the severity of the failure, as compared to a naively designed system in which even a small failure can cause total breakdown.
has d bpedia resource: Category:Fault-tolerant computer systems
has wikipedia article: Fault tolerance
supports: Availability

FIWARE
type: NamedIndividual
type: Organization

FIWARE Advanced Web-based User Interface
creator: sebastian
associated with: EndUser
associated with: IIRA Application Domain
associated with: IIRA Usage Viewpoint
type: NamedIndividual
type: Fiware Chapter
type: Standard Classification
comment: The Generic Enablers (GEs) from the Advanced Web-based User Interface (WebUI) chapter cover a set of GEs that provide an advanced user experience using HTML-5 and a Web-based UI approach. The objective of the Advanced Web-based UI GE is to significantly improve the user experience for the Future Internet by adding new user input and interaction capabilities, such as interactive 3D graphics, immersive interaction with the real and virtual world via Augmented Reality, virtualizing the display and driving them over the network, and many more.
is Described in: FIWARE Architecture
alignes With: IIRA Application Domain
alignes With: IIRA Usage Viewpoint
frames: User Interaction

FIWARE Applications Services and Data Delivery
creator: sebastian
associated with: IDS RAM Process Layer
associated with: IIRA Connectivity
associated with: NGSI-LD Architecture
type: NamedIndividual
type: Fiware Chapter
type: Standard Classification
comment: The Generic Enablers (GE) for the Apps Chapter together build an ecosystem of applications, services and data that is sustainable and fosters innovation as well as cross-fertilization. In particular the Apps Generic Enablers supports managing applications, services and data in a business framework across the whole service life cycle from creation through composition of applications and data to monetization and revenue sharing. A couple of basic GEs are important to realize the vision of such an applications, services and data business framework, which enables new business models in an agile and flexible way. Among them: a store, a marketplace, a revenue sharing engine, an application composer through mashup and a data visualization and analysis component. The Business Framework is heavily relying on USDL as common uniform description format for services which does not only focus on technical aspects of service, but also on business aspects as well as functional and non-functional service attributes. The Application Mashup GE aims at allowing end users without programming skills to quickly compose beautiful web applications and dashboards/cockpits mashing up widgets, operators and data sources from a shared catalogue. The Data Visualisation GE aims at creating agile, beautiful visualizations and meaningful reports useful to present the large variety of datasets. Data stakeholders will bring in the play as well as providing customisable data analytics.
is Described in: FIWARE Architecture
alignes With: IDS RAM Process Layer
alignes With: IIRA Connectivity
alignes With: NGSI-LD Architecture
frames: Data Analytics
frames: DataSelection
frames: Service Composition
frames: Service Selection

Fiware Chapter
creator: sebastian
type: Class
type: NamedIndividual
comment: Following is a description of the Reference Architecture linked to the different chapters of FIWARE. A description of FIWARE Generic Enablers (GEs) being supported in each chapter is provided, including the high-level description of the APIs that each FIWARE Generic Enabler (GE) exposes to application developers or it uses to connect to another FIWARE GEs.
subclass of: Standard Classification

FIWARE Cloud Hosting
creator: sebastian
associated with: IDS RAM System Layer
associated with: IIRA Application Domain
associated with: IIRA Distributed Data Management
associated with: IIRA Scalability
associated with: NGSI-LD Architecture
type: NamedIndividual
type: Fiware Chapter
type: Standard Classification
comment: The Cloud Chapter offers Generic Enablers (GEs) that comprise the foundation for designing a modern cloud hosting infrastructure that can be used to develop, deploy and manage Future Internet applications and services. Provided hosting capabilities are of several kinds and at several levels of resource abstraction -- aiming at the needs of different applications hosted on the cloud. The IaaS Data Center Resource Management (DCRM) GE is offering provisioning and life cycle management of virtualized resources (compute, storage, network) associated with virtual machines. The Object Storage GE offers provisioning and life cycle management of object-based storage containers and elements. The Job Scheduler GE offers the application to submit and manage computational jobs in a unified and scalable manner. The Edgelet Management GE offers the capability to host lightweight application components, called edgelets. Moreover, the IaaS Service Management (SM) GE provides the means to host complex applications. Lastly, the PaaS Management GE uses the above capabilities to offer provisioning and management of complete PaaS environments, leveraging also the Software Deployment and Configuration (SDC) GE which offers a flexible framework for installation and customization of software products (via Chef recipes) within individual virtual machines.
is Described in: FIWARE Architecture
alignes With: IDS RAM System Layer
alignes With: IIRA Application Domain
alignes With: IIRA Distributed Data Management
alignes With: IIRA Scalability
alignes With: NGSI-LD Architecture
frames: Availability
frames: Cloud Computing Capability
frames: Data Processing
frames: Data Sovereignty
frames: Integrity Protection and Verification
frames: Privacy
frames: Reliability
frames: Safety
frames: Security
frames: Service Composition
frames: Service Deployment
frames: Service life-cycle management
frames: Service Orchestration
frames: Trustworthiness

FIWARE Data/Context Management
creator: sebastian
associated with: NGSI-LD API Operation
associated with: NGSI-LD Data Representation
associated with: NGSI-LD Information Model
type: NamedIndividual
type: Fiware Chapter
type: Standard Classification
comment: The Data/Context Management FIWARE chapter aims at providing outperforming and platform-like GEs that will ease development and provision of innovative Applications that require gathering, publication, processing and exploitation of information and data streams in real-time and at massive scale. Combined with GEs coming from the Apps Chapters, Application Providers will be able to build innovative business models based on exploitation of massive data provided by end users. FIWARE Data/Context Management GEs allow to gather information from context and other sources (Context Broker), mediate metadata among GEs and applications (Metadata pre-processor) query stored information through an homogeneous layer (Query Broker), , annotate existing information (Semantic Annotation), store and manage semantic information (Semantic Application Support), generate new knowledge from big data stores using a Map & Reduce paradigm (Big Data analysis) and react to different types of scenarios (Complex Event Processing). It also provides GEs for media management, as easy creation of advanced video applications (Stream Oriented GE) and specifically, video analysis in the compressed domain (CDVA).
is Described in: FIWARE Architecture
alignes With: NGSI-LD API Operation
alignes With: NGSI-LD Data Representation
alignes With: NGSI-LD Information Model
frames: Big Data Applications
frames: Data Discovery
frames: Data Processing
frames: Interoperability
frames: Stream processing

FIWARE IoT Services Enablement
creator: sebastian
associated with: IDS RAM System Layer
associated with: IIRA Control Domain
associated with: RAMI Communication Layer
associated with: RAMI Integration Layer
type: NamedIndividual
type: Fiware Chapter
type: Standard Classification
comment: The deployment of the architecture of the IoT Service Enablement chapter is typically distributed across a large number of Devices, several Gateways and the Backend. A device is a hardware entity, component or system that either measures properties of a thing/group of things or influences the properties of a thing/group of things or both measures/influences. Sensors and actuators are devices. IoT Resources are computational elements (software) that provide the technical means to perform sensing and/or actuation on the device. The resource is usually hosted on the device. IoT GEs have been spread in two different domains: Gateway and Backend. While IoT Gateway GEs provide inter-networking and protocol conversion functionalities between devices and the IoT Backend GEs, the IoT Backend GEs provide management functionalities for the devices and IoT domain-specific support for the applications.
is Described in: FIWARE Architecture
alignes With: IDS RAM System Layer
alignes With: IIRA Control Domain
alignes With: RAMI Communication Layer
alignes With: RAMI Integration Layer
frames: Cloud Computing Capability
frames: Data Discovery
frames: Data Processing
frames: Edge computing
frames: Endpoint Invocation
frames: Interoperability
frames: Internet of Things
frames: Syntactic Interoperability

FIWARE Security
creator: sebastian
associated with: Security
associated with: IDS RAM Security Perspective
associated with: IIRA Security
associated with: XACML
type: NamedIndividual
type: Fiware Chapter
type: Standard Classification
comment: The Future Internet services will always be exposed to different types of threats that can lead to severe misuse and damage. Creating secured and trusted services without sacrificing much of the desired functionality, usability, performance and cost efficiency is a great challenge, especially in a dynamic environment where new threats and attack methods emerge on a daily basis. The overall ambition of the Security Architecture of FIWARE is to demonstrate that the Vision of an Internet that is "secure by design" is becoming reality. Based on achievements to date and/or to come in the short-term (both from a technological but also a standardization perspective) we will show that "secure by design" is possible. Security, Privacy and Trust in FIWARE is mainly focusing on delivering tools and techniques to have the above-mentioned security needs properly met. Furthermore a decision making support and the automation of countermeasures allow alleviating the workload of users and administrators while raising their security awareness. The high-level Reference Architecture is formed by four main blocks of GEs: Cybersecurity, Identity and Access Management (and Enforcement), Privacy, Trust and Trustworthiness.
is Described in: FIWARE Architecture
alignes With: Security
alignes With: IDS RAM Security Perspective
alignes With: IIRA Security
frames: Authentication
frames: Authorization
frames: Data Access Control
frames: Data Sovereignty
frames: Identity Management
frames: Privacy
frames: Security
frames: Trustworthiness

Geo tracking
has stakeholder: EndUser
type: NamedIndividual
type: Concern
comment: A system built using the ARM shall support physical entity location tracking (geo spatial and/or logical location)
see also: IoT-A Requirement UNI.016
has d bpedia resource: Track and trace
supports: Context Awareness

Geospatial data and information
type: NamedIndividual
type: Concern
comment: Discovery and lookup services of the system shall allow locating physical entities based on geographical parameters.
see also: IoT-A Requirement UNI.402
see also: IoT-A Requirement UNI.403
see also: IoT-A Requirement UNI.404
see also: IoT-A Requirement UNI.405
see also: IoT-A Requirement UNI.406
see also: IoT-A Requirement UNI.415
see also: IoT-A Requirement UNI.420
see also: IoT-A Requirement UNI.421
has d bpedia resource: Geographic data and information
supports: Data Analytics

GeospatialQuery
see also: IoT-A Requirement UNI.401

Greening of IoT
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: The system energy consumption is expanding at a high rate because of increment in information rates, an increment in quantity of Internet-empowered services and fast development of Internet associated edgedevices. The future IoT will cause a critical increase in the network energy consumption.
has wikipedia article: Green computing
supports: Energy Control

International Data Spaces Association
creator: sebastian
type: NamedIndividual
type: Organization
type: IIoTConsortium
comment: IDSA ensures that the special economic interests of business are specifically integrated into the research work of Industrial Date Space.
label: IDSA
has official resource: en
has wikipedia article: Industrial Data Space Association

IDS RAM Business Layer
associated with: IIRA Business Domain
associated with: Ocean Protocol System Viewpoint
associated with: RAMI Business Layer
associated with: x-road System Components
type: NamedIndividual
type: IDS RAM Layer
type: Standard Classification
is Described in: Industrial Data Space Reference Architecture Model
alignes With: IIRA Business Domain
alignes With: Ocean Protocol System Viewpoint
alignes With: RAMI Business Layer
alignes With: x-road System Components
frames: Role Categorization

IDSRAMBusinessLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IDS RAM Business Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 21
    oahas start selector: Page 17
  oahas source: IDS REFERENCE ARCHITECTURE MODEL INDUSTRIAL DATA SPACE VERSION 2.0

IDS RAM Certification Perspective
type: NamedIndividual
type: IDS RAM Perspective
type: Standard Classification
is Described in: Industrial Data Space Reference Architecture Model
frames: Certification
frames: Safety
frames: Security

IDSRAMCertificationAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IDS RAM Certification Perspective
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 84
    oahas start selector: Page 79
  oahas source: IDS REFERENCE ARCHITECTURE MODEL INDUSTRIAL DATA SPACE VERSION 2.0

IDS Data Market
type: NamedIndividual
type: Standard Classification
is Described in: Industrial Data Space Reference Architecture Model

IDS RAM Functional Layer
associated with: Data Sovereignty
associated with: Interoperability
type: NamedIndividual
type: IDS RAM Layer
type: Standard Classification
is Described in: Industrial Data Space Reference Architecture Model

IDSRAMFunctionalLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IDS RAM Functional Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 25
    oahas start selector: Page 21
  oahas source: IDS REFERENCE ARCHITECTURE MODEL INDUSTRIAL DATA SPACE VERSION 2.0

IDS RAM Governance Perspective
associated with: DTP Ecosystem
associated with: DTP Security & Privacy
associated with: IICF Framework Layer
associated with: RAMI Business Layer
type: NamedIndividual
type: IDS RAM Perspective
type: Standard Classification
is Described in: Industrial Data Space Reference Architecture Model
alignes With: DTP Ecosystem
alignes With: DTP Security & Privacy
alignes With: IICF Framework Layer
alignes With: RAMI Business Layer
frames: Compliance
frames: Trustworthiness

IDSRAMGovernanceAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IDS RAM Governance Perspective
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 88
    oahas start selector: Page 84
  oahas source: IDS REFERENCE ARCHITECTURE MODEL INDUSTRIAL DATA SPACE VERSION 2.0

IDS RAM Information Layer
associated with: BDVA Data Management
associated with: InformationDomain
associated with: IoT-A Information Viewpoint
associated with: NGSI-LD Data Representation
associated with: NGSI-LD Information Model
associated with: RAMI Information Layer
associated with: Vocabulary
type: NamedIndividual
type: IDS RAM Layer
type: Standard Classification
is Described in: Industrial Data Space Reference Architecture Model
alignes With: BDVA Data Management
alignes With: InformationDomain
alignes With: IoT-A Information Viewpoint
alignes With: NGSI-LD Data Representation
alignes With: NGSI-LD Information Model
alignes With: RAMI Information Layer
alignes With: Vocabulary

IDSRAMInformationLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IDS RAM Information Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 56
    oahas start selector: Page 32
  oahas source: IDS REFERENCE ARCHITECTURE MODEL INDUSTRIAL DATA SPACE VERSION 2.0

IDS Interoperability
type: NamedIndividual
type: Standard Classification
is Described in: Industrial Data Space Reference Architecture Model

IDS RAM Layer
creator: sebastian
type: Class
subclass of: Standard Classification
equivalent class: Class
  one of: IDS RAM Business Layer
  one of: IDS RAM Functional Layer
  one of: IDS RAM Information Layer
  one of: IDS RAM Process Layer
  one of: IDS RAM System Layer

IDSRAMLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IDS RAM Layer
oahas target: oaSpecificResource
  format: pdf
  oahas source: IDS REFERENCE ARCHITECTURE MODEL INDUSTRIAL DATA SPACE VERSION 2.0
oahas target: oaSpecificResource
  format: pdf
  oahas source: IDS REFERENCE ARCHITECTURE MODEL INDUSTRIAL DATA SPACE VERSION 2.0

IDS RAM Process Layer
associated with: BDVA Data Analytics
associated with: BDVA Data Management
associated with: BDVA Data Processing Architectures
associated with: DTP Deployment
associated with: FIWARE Applications Services and Data Delivery
associated with: IIRA Application Domain
associated with: IIRA Operation Domain
associated with: InformationDomain
associated with: FIWARE Interface to Networks and Devices
associated with: IoT-A Functional Viewpoint
associated with: IoT-A Information Viewpoint
associated with: NGSI-LD API Operation
associated with: Ocean Protocol System Viewpoint
associated with: RAMI Functional Layer
associated with: x-road Protocols and Interfaces
associated with: x-road System Components
type: NamedIndividual
type: IDS RAM Layer
type: Standard Classification
is Described in: Industrial Data Space Reference Architecture Model
alignes With: BDVA Data Analytics
alignes With: BDVA Data Management
alignes With: BDVA Data Processing Architectures
alignes With: DTP Deployment
alignes With: FIWARE Applications Services and Data Delivery
alignes With: IIRA Application Domain
alignes With: IIRA Operation Domain
alignes With: InformationDomain
alignes With: FIWARE Interface to Networks and Devices
alignes With: IoT-A Functional Viewpoint
alignes With: IoT-A Information Viewpoint
alignes With: NGSI-LD API Operation
alignes With: Ocean Protocol System Viewpoint
alignes With: RAMI Functional Layer
alignes With: x-road Protocols and Interfaces
alignes With: x-road System Components
frames: Service Choreography
frames: Service Composition
frames: Service Orchestration

IDSRAMProcessLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IDS RAM Process Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 32
    oahas start selector: Page 25
  oahas source: IDS REFERENCE ARCHITECTURE MODEL INDUSTRIAL DATA SPACE VERSION 2.0

Industrial Data Space Reference Architecture Model
associated with: IIRA Functional Viewpoint
type: NamedIndividual
type: Architecture Description
type: Standarization Framework
label: IDS RAM
has Publisher: International Data Spaces Association
alignes With: IIRA Functional Viewpoint

IDS RAM Security Perspective
associated with: BDVA Cybersecurity and Trust
associated with: BDVA Data Protection
associated with: FIWARE Security
associated with: IIRA Security
associated with: IIC Security Framework
associated with: IoT-A Functional Viewpoint
associated with: IoT-A Trust Security and Privacy
associated with: RAMI
type: NamedIndividual
type: IDS RAM Perspective
type: Standard Classification
comment: The IDS Security Architecture provides means to identify participants, protect communication and data exchange transactions between them, and control the use of data after it has been sent.
is Described in: Industrial Data Space Reference Architecture Model
alignes With: BDVA Cybersecurity and Trust
alignes With: BDVA Data Protection
alignes With: FIWARE Security
alignes With: IIRA Security
alignes With: IIC Security Framework
alignes With: IoT-A Functional Viewpoint
alignes With: IoT-A Trust Security and Privacy
alignes With: OCF Security
frames: Authentication
frames: Authorization
frames: Communication
frames: Data Access Control
frames: Data Sovereignty
frames: Data Usage Control
frames: Identification
frames: Identity Management
frames: Privacy
frames: Secure Communication
frames: Security
frames: Service Isolation
frames: Trustworthiness

IDSRAMSecurityAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IDS RAM Security Perspective
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 79
    oahas start selector: Page 63
  oahas source: IDS REFERENCE ARCHITECTURE MODEL INDUSTRIAL DATA SPACE VERSION 2.0

IDS RAM System Layer
creator: sebastian
associated with: DTP System
associated with: Edgecross Edgecomputing Layer
associated with: Edgecross IT Systems Layer
associated with: FIWARE Architecture
associated with: FIWARE Cloud Hosting
associated with: FIWARE IoT Services Enablement
associated with: IICF Framework Layer
associated with: IIRA Control Domain
associated with: IIRA Implementation Viewpoint
associated with: IIRA Physical Systems
associated with: FIWARE Interface to Networks and Devices
associated with: IoT-A Deployment and Operation
associated with: NGSI-LD API Operation
associated with: NGSI-LD Architecture
associated with: RAMI Communication Layer
associated with: RAMI Integration Layer
associated with: x-road Deplyoment View
type: NamedIndividual
type: IDS RAM Layer
type: Standard Classification
is Described in: Industrial Data Space Reference Architecture Model
alignes With: DTP System
alignes With: Edgecross Edgecomputing Layer
alignes With: Edgecross IT Systems Layer
alignes With: FIWARE Architecture
alignes With: FIWARE Cloud Hosting
alignes With: FIWARE IoT Services Enablement
alignes With: IICF Framework Layer
alignes With: IIRA Control Domain
alignes With: IIRA Physical Systems
alignes With: FIWARE Interface to Networks and Devices
alignes With: IoT-A Deployment and Operation
alignes With: NGSI-LD API Operation
alignes With: NGSI-LD Architecture
alignes With: RAMI Communication Layer
alignes With: RAMI Integration Layer
alignes With: x-road Deplyoment View

IDSRAMSystemLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IDS RAM System Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 62
    oahas start selector: Page 56
  oahas source: IDS REFERENCE ARCHITECTURE MODEL INDUSTRIAL DATA SPACE VERSION 2.0

IDS REFERENCE ARCHITECTURE MODEL INDUSTRIAL DATA SPACE VERSION 2.0
type: NamedIndividual
type: oaSpecificResource
has open resource: IDS Referenz Architecture.pdf

IIC
creator: sebastian
associated with: Industrial Internet Reference Architecture
type: NamedIndividual
type: Organization
type: IIoTConsortium
type: StandardOrganization
comment: Founded in 2014 to further development, adoption and wide-spread use of interconnected machines, intelligent analytics and people at work. (source: https://www.postscapes.com/internet-of-things-protocols/)
label: Industrial Internet Consortium
has official resource: www.iiconsortium.org

Industrial Internet Connectivity Framework
type: NamedIndividual
type: Document
type: Publication
label: IICF
has Classification: IIRA Connectivity

IICF Framework Layer
associated with: DDS
associated with: IDS RAM Governance Perspective
associated with: IDS RAM System Layer
associated with: IEC_62541
associated with: oneM2M
associated with: Q1548249
is part of: IIRA Connectivity
type: NamedIndividual
type: Connectivity Layer
type: Standard Classification
comment: IICF Framework Layer
comment: IICF Framework Layer an instance of the IICF Connectivity Layer
alignes With: IDS RAM Governance Perspective
alignes With: IDS RAM System Layer
frames: Authentication
frames: Communication
frames: Data Access
frames: Data Discovery
frames: Governance
frames: Identification
frames: Identity Management
frames: Integrity Protection and Verification
frames: Interoperability
frames: Quality of Service
frames: Secure Communication
frames: Security
frames: Semantic Interoperability
frames: Service Description
frames: Service Discovery
frames: Syntactic Interoperability
frames: Trustworthiness

IICFFrameworkLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IICF Framework Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 17
    oahas start selector: Page 14
  oahas source: The Industrial Internet of Things Volume G5: Connectivity Framework
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 17
    oahas start selector: Page 14
  oahas source: The Industrial Internet of Things Volume G5: Connectivity Framework

IICF Link Layer
associated with: IEEE 802
associated with: IEEE 802 16-2012
associated with: WiFi
is part of: IIRA Connectivity
type: NamedIndividual
type: Connectivity Layer
type: Standard Classification
frames: Communication

IICFLinkLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IICF Link Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 17
    oahas start selector: Page 14
  oahas source: The Industrial Internet of Things Volume G5: Connectivity Framework
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 17
    oahas start selector: Page 14
  oahas source: The Industrial Internet of Things Volume G5: Connectivity Framework

IICF Network Layer
associated with: IPv6
is part of: IIRA Connectivity
type: NamedIndividual
type: Connectivity Layer
type: Standard Classification
frames: Communication
frames: IPv4 Support
frames: IPv6 Support
frames: Interoperability
frames: Syntactic Interoperability

IICFNetworkLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IICF Network Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 17
    oahas start selector: Page 14
  oahas source: The Industrial Internet of Things Volume G5: Connectivity Framework
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 17
    oahas start selector: Page 14
  oahas source: The Industrial Internet of Things Volume G5: Connectivity Framework

IICF Physical Layer
associated with: IEEE 802
associated with: IEEE 802 16-2012
is part of: IIRA Connectivity
type: NamedIndividual
type: Connectivity Layer
type: Standard Classification
frames: Communication

IICFPhysicalLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IICF Physical Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 17
    oahas start selector: Page 14
  oahas source: The Industrial Internet of Things Volume G5: Connectivity Framework
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 17
    oahas start selector: Page 14
  oahas source: The Industrial Internet of Things Volume G5: Connectivity Framework

IICF Transport Layer
associated with: HTTP
associated with: HTTP2
associated with: IEC_61158
associated with: ISO_20922
associated with: HTTP/1.1
associated with: TRANSMISSION CONTROL PROTOCOL
associated with: CoAP
associated with: UDP
is part of: IIRA Connectivity
type: NamedIndividual
type: Connectivity Layer
type: Standard Classification
frames: CardinalityOfDataSources
frames: Cardinality of Participants
frames: Communication
frames: Endpoint Invocation
frames: Interoperability
frames: Multilateralism
frames: Secure Communication
frames: Security
frames: Service Composition
frames: Syntactic Interoperability
frames: Time Synchronization
frames: Trustworthiness
frames: Unicast

IICFTansportLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IICF Transport Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 17
    oahas start selector: Page 14
  oahas source: The Industrial Internet of Things Volume G5: Connectivity Framework
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 17
    oahas start selector: Page 14
  oahas source: The Industrial Internet of Things Volume G5: Connectivity Framework

IIC Vocabulary
creator: IIC
creator: sebastian
associated with: IDS RAM Information Layer
type: NamedIndividual
type: Document
type: Publication
type: Standard Classification
maker: IIC
has Publisher: IIC
is Described in: Industrial Internet Reference Architecture
alignes With: IDS RAM Information Layer

The Industrial Internet of Things Volume G1: Reference Architecture IIC:PUB:G1:V1.80:20170131
type: NamedIndividual
type: oaSpecificResource
has open resource: IIC PUB G1 V1.80 2017-01-31.pdf

Industrial Internet Reference Architecture
type: NamedIndividual
type: Architecture Description
type: Standarization Framework
comment: The IIRA addresses the need for a common architecture framework to develop interoperable IIoT systems for diverse applications across a broad spectrum of industrial verticals in the public and private sectors to achieve the true promise of IIoT.
alternative label: IIRA
note: Publications referred: 1. The Industrial Internet of Things Volume G1: Reference Architecture (IIC:PUB:G1:V1.80:20170131)
has official resource: IIRA.htm
has Publisher: IIC
has Target Concern: EndUser
has Target Concern: Business Value
has Target Concern: Decision maker
has Target Concern: Developer
has Target Concern: Maintenance Cost
has Target Concern: Product Liability
has Target Concern: Product Manager
has Target Concern: Return On Investment
has Target Concern: System Engineer
has Target Concern: SystemOperator
has Target Concern: Q1548249

IIRA Application Domain
creator: sebastian
associated with: BDVA Cloud and High Performance Computing
associated with: Edgecross IT Systems Layer
associated with: FIWARE Advanced Web-based User Interface
associated with: FIWARE Cloud Hosting
associated with: IDS RAM Process Layer
associated with: RAMI Functional Layer
associated with: RAMI Information Layer
is part of: IIRA Functional Viewpoint
type: NamedIndividual
type: IIRA Functional Domain
type: Standard Classification
note: Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.4 THE APPLICATION DOMAIN' 'Page 34'
is Described in: Industrial Internet Reference Architecture
alignes With: BDVA Cloud and High Performance Computing
alignes With: Edgecross IT Systems Layer
alignes With: FIWARE Advanced Web-based User Interface
alignes With: FIWARE Cloud Hosting
alignes With: IDS RAM Process Layer
alignes With: RAMI Functional Layer
alignes With: RAMI Information Layer
frames: BdvaDataViualisationAndUserInteraction
frames: Data Processing
frames: Endpoint Invocation
frames: Interoperability
frames: Syntactic Interoperability

IIRAApplicationDomainAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IIRA Application Domain
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 35
    oahas start selector: Page 34
  oahas source: Industrial Internet Architecture Version 1
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 35
    oahas start selector: Page 34
  oahas source: Industrial Internet Architecture Version 1

IIRA Business Domain
creator: sebastian
associated with: IDS RAM Business Layer
associated with: Ocean Protocol System Viewpoint
associated with: RAMI Business Layer
is part of: IIRA Functional Viewpoint
type: NamedIndividual
type: IIRA Functional Domain
type: Standard Classification
note: Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.5 THE BUSINESS DOMAIN' 'Page 34'
is Described in: Industrial Internet Reference Architecture
alignes With: IDS RAM Business Layer
alignes With: Ocean Protocol System Viewpoint
alignes With: RAMI Business Layer
frames: ProcessPlanning

IIRABusinessDomainAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IIRA Business Domain
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 35
    oahas start selector: Page 34
  oahas source: Industrial Internet Architecture Version 1
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 35
    oahas start selector: Page 34
  oahas source: Industrial Internet Architecture Version 1

IIRA Business Viewpoint
creator: sebastian
associated with: IVI Business Layer
associated with: Ocean Protocol Business Viewpoint
associated with: Ocean Protocol Marketplace Viewpoint
type: NamedIndividual
type: Standard Classification
type: Viewpoint
comment: The business viewpoint frames economic aspects and business relations regarded by the IIC Reference Architecture.
note: Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.1 BUSINESS VIEWPOINT' 'Page 15'
is Described in: Industrial Internet Reference Architecture
alignes With: IVI Business Layer
alignes With: Ocean Protocol Business Viewpoint
alignes With: Ocean Protocol Marketplace Viewpoint
frames: Business Context
frames: Business Value
frames: Maintenance Cost
frames: Product Liability
frames: Resilience
frames: Return On Investment
frames: Safety
frames: Security
frames: Trustworthiness

IIRABusinessViewpointAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IIRA Business Viewpoint
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 22
    oahas start selector: Page 20
  oahas source: Industrial Internet Architecture Version 1
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 22
    oahas start selector: Page 20
  oahas source: Industrial Internet Architecture Version 1

IIRA Connectivity
creator: sebastian
associated with: BDVA Data Processing Architectures
associated with: Decision maker
associated with: DTP System
associated with: FIWARE Applications Services and Data Delivery
associated with: IEC_62541
associated with: Industrial Internet Connectivity Framework
associated with: IoT-A Evolution and Interoperability
associated with: LinkLayer
associated with: NGSI-LD API Operation
associated with: RAMI Communication Layer
associated with: REST
associated with: oneM2M
associated with: Q1548249
is part of: IIRA Functional Viewpoint
type: NamedIndividual
type: IIRA Crosscutting Function
type: Standard Classification
is Described in: Industrial Internet Reference Architecture
alignes With: BDVA Data Processing Architectures
alignes With: DTP System
alignes With: FIWARE Applications Services and Data Delivery
alignes With: IoT-A Evolution and Interoperability
alignes With: NGSI-LD API Operation
alignes With: RAMI Communication Layer
frames: Authentication
frames: CardinalityOfDataSources
frames: Cardinality of Participants
frames: Communication
frames: Data Access
frames: Data Discovery
frames: Dynamic Adjustability
frames: Endpoint Invocation
frames: Evolvability
frames: Governance
frames: IPv4 Support
frames: IPv6 Support
frames: Identification
frames: Identity Management
frames: Integrity Protection and Verification
frames: Interoperability
frames: Multilateralism
frames: Network performance
frames: Quality of Service
frames: Reliability
frames: Resilience
frames: Safety
frames: Scalability
frames: Secure Communication
frames: Security
frames: Semantic Interoperability
frames: Service Choreography
frames: Service Composition
frames: Service Deployment
frames: Service Description
frames: Service Discovery
frames: Service life-cycle management
frames: Service Orchestration
frames: Syntactic Interoperability
frames: Time Synchronization
frames: Trustworthiness
frames: Unicast

IIRAConnectivityAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IIRA Connectivity
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 127
    oahas start selector: Page 8
  oahas source: The Industrial Internet of Things Volume G5: Connectivity Framework
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 127
    oahas start selector: Page 8
  oahas source: The Industrial Internet of Things Volume G5: Connectivity Framework

IIRA Control Domain
creator: sebastian
associated with: Edgecross Edgecomputing Layer
associated with: FIWARE IoT Services Enablement
associated with: IDS RAM System Layer
associated with: IoT-A Information Viewpoint
associated with: NGSI-LD API Operation
associated with: RAMI Integration Layer
associated with: x-road Protocols and Interfaces
is part of: IIRA Functional Viewpoint
type: NamedIndividual
type: IIRA Functional Domain
type: Standard Classification
note: Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.1 THE CONTROL DOMAIN' 'Page 27'
is Described in: Industrial Internet Reference Architecture
alignes With: Edgecross Edgecomputing Layer
alignes With: FIWARE IoT Services Enablement
alignes With: IDS RAM System Layer
alignes With: IoT-A Information Viewpoint
alignes With: NGSI-LD API Operation
alignes With: RAMI Integration Layer
alignes With: x-road Protocols and Interfaces
frames: Actuation
frames: Asset Management
frames: Communication
frames: Edge Analytics
frames: Internet of Things
frames: Sensing
frames: Virtual Entity

IIRAControlDomainAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IIRA Control Domain
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 30
    oahas start selector: Page 27
  oahas source: Industrial Internet Architecture Version 1
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 30
    oahas start selector: Page 27
  oahas source: Industrial Internet Architecture Version 1

IIRA Crosscutting Function
creator: sebastian
type: Class
type: NamedIndividual
comment: Often these enabling functions, the so-called crosscutting functions, need to be made available across many of the system functional components. For Reference Architecture 6: Functional Viewpoint example, system functions need to be connected so they can interact with each other to complete functionality at the system level.
subclass of: Standard Classification
subclass of: Restriction
  has value: IIRA Functional Viewpoint
  on property: isPartOf
note: Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.6 CROSSCUTTING FUNCTIONS AND SYSTEM CHARACTERISTICS' 'Page 34'

IIRACrosscuttingFunctionAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IIRA Crosscutting Function
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 36
    oahas start selector: Page 34
  oahas source: Industrial Internet Architecture Version 1
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 36
    oahas start selector: Page 34
  oahas source: Industrial Internet Architecture Version 1

IIRA Distributed Data Management
creator: sebastian
associated with: FIWARE Cloud Hosting
associated with: RAMI Communication Layer
is part of: IIRA Functional Viewpoint
type: NamedIndividual
type: IIRA Crosscutting Function
type: Standard Classification
is Described in: Industrial Internet Reference Architecture
alignes With: FIWARE Cloud Hosting
alignes With: RAMI Communication Layer
frames: Interoperability
frames: Semantic Interoperability

IIRA Functional Domain
creator: sebastian
type: Class
type: NamedIndividual
subclass of: Standard Classification
subclass of: Restriction
  has value: IIRA Functional Viewpoint
  on property: isPartOf
subclass of: Restriction
  has value: Industrial Internet Reference Architecture
  on property: is Described in

IIRA Functional Viewpoint
creator: sebastian
associated with: Industrial Data Space Reference Architecture Model
associated with: IoT-A Functional Viewpoint
associated with: Ocean Protocol System Viewpoint
type: NamedIndividual
type: Standard Classification
type: Viewpoint
comment: The IIRA Functional Viewpoint contains the IIRA Domains in order to describe technical relations and communications between the several dimensions of IoT devices.
note: Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.3 FUNCTIONAL VIEWPOINT' 'Page 16'
is Described in: Industrial Internet Reference Architecture
alignes With: Industrial Data Space Reference Architecture Model
alignes With: IoT-A Functional Viewpoint
alignes With: Ocean Protocol System Viewpoint
frames: ProcessPlanning
frames: Access Policy
frames: Actuation
frames: Authentication
frames: Authorization
frames: Availability
frames: BdvaDataViualisationAndUserInteraction
frames: CardinalityOfDataSources
frames: Cardinality of Participants
frames: Cloud Computing Capability
frames: Communication
frames: Data Access
frames: Data Access Control
frames: Data Analytics
frames: Data at rest
frames: Data Discovery
frames: DataInMotion
frames: Data Processing
frames: Data Protection
frames: Data Sovereignty
frames: Dynamic Adjustability
frames: Endpoint Invocation
frames: Evolvability
frames: Governance
frames: IPv4 Support
frames: IPv6 Support
frames: Identification
frames: Identity Management
frames: Integrity Protection and Verification
frames: Interoperability
frames: Internet of Things
frames: Multilateralism
frames: Network performance
frames: Privacy
frames: Quality of Service
frames: Real Time Analytics
frames: Reliability
frames: Resilience
frames: Safety
frames: Scalability
frames: Secure Communication
frames: Security
frames: Security Configuration
frames: Semantic Interoperability
frames: Sensing
frames: Service Access Control
frames: Service Choreography
frames: Service Composition
frames: Service Deployment
frames: Service Description
frames: Service Discovery
frames: Service Isolation
frames: Service level agreement
frames: Service life-cycle management
frames: Service Orchestration
frames: Stream processing
frames: Syntactic Interoperability
frames: Time Synchronization
frames: Trustworthiness
frames: Unicast

IIRAFunctionalViewpointAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IIRA Functional Viewpoint
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 38
    oahas start selector: Page 25
  oahas source: Industrial Internet Architecture Version 1
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 38
    oahas start selector: Page 25
  oahas source: Industrial Internet Architecture Version 1

IIRA Implementation Viewpoint
associated with: ControlDomain
associated with: DTP Deployment
associated with: FIWARE Architecture
associated with: IDS RAM System Layer
associated with: IIRA Application Domain
associated with: IIRA Business Domain
associated with: IIRA Operation Domain
associated with: InformationDomain
associated with: IoT-A Deployment and Operation
associated with: NGSI-LD Architecture
associated with: x-road Deplyoment View
type: NamedIndividual
type: Standard Classification
type: Viewpoint
note: Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.4 IMPLEMENTATION VIEWPOINT' 'Page 16'
is Described in: Industrial Internet Reference Architecture
alignes With: DTP Deployment
alignes With: FIWARE Architecture
alignes With: IoT-A Deployment and Operation
alignes With: NGSI-LD Architecture
alignes With: x-road Deplyoment View
frames: Cloud Computing Capability
frames: Communication
frames: Data Processing
frames: Edge computing
frames: Endpoint Description
frames: Interoperability
frames: Semantic Interoperability

IIRAImplementationViewpointAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IIRA Implementation Viewpoint
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 47
    oahas start selector: Page 38
  oahas source: Industrial Internet Architecture Version 1
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 47
    oahas start selector: Page 38
  oahas source: Industrial Internet Architecture Version 1

IIRA Information Domain
associated with: BDVA Data Analytics
associated with: BDVA Data Processing Architectures
associated with: DTP System
associated with: Edgecross Edgecomputing Layer
associated with: IDS RAM Information Layer
associated with: IDS RAM Process Layer
associated with: IoT-A Information Viewpoint
associated with: NGSI-LD Information Model
associated with: RAMI Information Layer
is part of: IIRA Functional Viewpoint
type: NamedIndividual
type: IIRA Functional Domain
type: Standard Classification
note: Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.3 THE INFORMATION DOMAIN' 'Page 32'
is Described in: Industrial Internet Reference Architecture
alignes With: BDVA Data Analytics
alignes With: BDVA Data Processing Architectures
alignes With: DTP System
alignes With: Edgecross Edgecomputing Layer
alignes With: IDS RAM Information Layer
alignes With: IDS RAM Process Layer
alignes With: IoT-A Information Viewpoint
alignes With: NGSI-LD Information Model
alignes With: RAMI Information Layer
frames: Data Analytics
frames: Data Processing
frames: Interoperability
frames: Semantic Interoperability
frames: Stream processing
frames: Syntactic Interoperability

IIRAInformationDomainAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IIRA Information Domain
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 34
    oahas start selector: Page 32
  oahas source: Industrial Internet Architecture Version 1
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 34
    oahas start selector: Page 32
  oahas source: Industrial Internet Architecture Version 1

IIRA Intelligent and Resilient Control
is part of: IIRA Functional Viewpoint
type: NamedIndividual
type: IIRA Crosscutting Function
type: Standard Classification
comment: There is a renewed movement to distribute computational capability toward the network peripheries, away from concentrated computation centers, to benefit from a reduction in movement of data and communication latency, and enhancement in local intelligent control and, more importantly, resilience. source: Industrial Internet Reference Archietcture
is Described in: Industrial Internet Reference Architecture

IIRA Operation Domain
associated with: DTP System
associated with: Edgecross Edgecomputing Layer
associated with: IDS RAM Process Layer
associated with: IoT-A Information Viewpoint
associated with: IVI Activity View
associated with: RAMI Functional Layer
is part of: IIRA Functional Viewpoint
type: NamedIndividual
type: IIRA Functional Domain
type: Standard Classification
note: Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.2 THE OPERATIONS DOMAIN' 'Page 30'
is Described in: Industrial Internet Reference Architecture
alignes With: DTP System
alignes With: Edgecross Edgecomputing Layer
alignes With: IDS RAM Process Layer
alignes With: IoT-A Information Viewpoint
alignes With: IVI Activity View
alignes With: RAMI Functional Layer
frames: Data Analytics
frames: Real Time Analytics
frames: Service Deployment
frames: Service life-cycle management

IIRAOperationsDomainAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IIRA Operation Domain
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 32
    oahas start selector: Page 30
  oahas source: Industrial Internet Architecture Version 1
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 32
    oahas start selector: Page 30
  oahas source: Industrial Internet Architecture Version 1

IIRA Physical Systems
creator: sebastian
associated with: Edgecross FA
associated with: IDS RAM System Layer
associated with: IVI Asset View
associated with: RAMI Asset Layer
is part of: IIRA Functional Viewpoint
type: NamedIndividual
type: Standard Classification
comment: Computational capabilities ranging from very limited (e.g. in a smart sensor) to reasonably rich (e.g. a cluster of servers) are placed in, attached to or collocated with physical systems (e.g. in smart sensors, devices or machines). These capabilities are connected through a variety of connectivity technologies including wireless.
has official resource: IIRA.htm
is Described in: Industrial Internet Reference Architecture
alignes With: Edgecross FA
alignes With: IDS RAM System Layer
alignes With: IVI Asset View
alignes With: RAMI Asset Layer

IIRA Privacy
associated with: DTP Security & Privacy
is part of: IIRA Functional Viewpoint
type: NamedIndividual
type: IIRA System Characteristic
type: Standard Classification
is Described in: Industrial Internet Reference Architecture
alignes With: DTP Security & Privacy
frames: Data Sovereignty
frames: Privacy
frames: Trustworthiness

IIRA Reliability
is part of: IIRA Functional Viewpoint
type: NamedIndividual
type: IIRA System Characteristic
type: Standard Classification
note: Publications referred: '<https://www.iiconsortium.org/pdf/IIC_PUB_G4_V1.00_PB-3.pdf IIC:PUB:G4:V1.0:PB:20160926>' '3.4 RELIABILITY' 'Page 18'
is Described in: Industrial Internet Reference Architecture
frames: Reliability
frames: Trustworthiness

IIRAReliabilityAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IIRA Reliability
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 19
    oahas start selector: Page 18
  oahas source: Industrial Internet of Things Volume G4: Security Framework
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 19
    oahas start selector: Page 18
  oahas source: Industrial Internet of Things Volume G4: Security Framework

IIRA Resilience
is part of: IIRA Functional Viewpoint
type: NamedIndividual
type: IIRA System Characteristic
type: Standard Classification
is Described in: Industrial Internet Reference Architecture

IIRAResilienceAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IIRA Resilience
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 20
    oahas start selector: Page 19
  oahas source: Industrial Internet of Things Volume G4: Security Framework
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 19
    oahas start selector: Page 18
  oahas source: Industrial Internet of Things Volume G4: Security Framework
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 19
    oahas start selector: Page 18
  oahas source: Industrial Internet of Things Volume G4: Security Framework
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 20
    oahas start selector: Page 19
  oahas source: Industrial Internet of Things Volume G4: Security Framework

IIRA Safety
is part of: IIRA Functional Viewpoint
type: NamedIndividual
type: IIRA System Characteristic
type: Standard Classification
is Described in: Industrial Internet Reference Architecture

IIRASafetyAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IIRA Safety
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 18
    oahas start selector: Page 17
  oahas source: Industrial Internet of Things Volume G4: Security Framework
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 18
    oahas start selector: Page 17
  oahas source: Industrial Internet of Things Volume G4: Security Framework

IIRA Scalability
associated with: FIWARE Cloud Hosting
is part of: IIRA Functional Viewpoint
type: NamedIndividual
type: IIRA System Characteristic
type: Standard Classification
is Described in: Industrial Internet Reference Architecture
alignes With: FIWARE Cloud Hosting
frames: Scalability

IIRA Security
creator: sebastian
associated with: DataOwner
associated with: Decision maker
associated with: DTP Security & Privacy
associated with: FIWARE Security
associated with: IDS RAM Security Perspective
associated with: IoT-A Availability and Resilience
associated with: IoT-A Trust Security and Privacy
associated with: Q1548249
is part of: IIRA Functional Viewpoint
type: NamedIndividual
type: IIRA System Characteristic
type: Standard Classification
is Described in: Industrial Internet Reference Architecture
alignes With: DTP Security & Privacy
alignes With: FIWARE Security
alignes With: IDS RAM Security Perspective
alignes With: IoT-A Availability and Resilience
alignes With: IoT-A Trust Security and Privacy
frames: Access Policy
frames: Authorization
frames: Availability
frames: Cloud Computing Capability
frames: Communication
frames: Data Access Control
frames: Data at rest
frames: DataInMotion
frames: Data Processing
frames: Data Protection
frames: Data Sovereignty
frames: Identification
frames: Identity Management
frames: Integrity Protection and Verification
frames: Privacy
frames: Reliability
frames: Resilience
frames: Safety
frames: Secure Communication
frames: Security
frames: Security Configuration
frames: Service Access Control
frames: Service Isolation
frames: Service level agreement
frames: Service life-cycle management
frames: Trustworthiness

IIRASecurityAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IIRA Security
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 121
    oahas start selector: Page 11
  oahas source: Industrial Internet of Things Volume G4: Security Framework
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 121
    oahas start selector: Page 11
  oahas source: Industrial Internet of Things Volume G4: Security Framework

IIC Security Framework
creator: sebastian
associated with: BDVA Cybersecurity and Trust
associated with: BDVA Data Protection
associated with: IDS RAM Security Perspective
associated with: x-road System Components
type: NamedIndividual
type: Standard Classification
note: Publications referred: '<https://www.iiconsortium.org/pdf/IIC_PUB_G4_V1.00_PB-3.pdf IIC:PUB:G4:V1.0:PB:20160926>'
has official resource: IISF.htm
alignes With: BDVA Cybersecurity and Trust
alignes With: BDVA Data Protection
alignes With: IDS RAM Security Perspective
alignes With: x-road System Components

IIRASecurityFrameworkAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IIC Security Framework
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 121
    oahas start selector: Page 11
  oahas source: Industrial Internet of Things Volume G4: Security Framework
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 121
    oahas start selector: Page 11
  oahas source: Industrial Internet of Things Volume G4: Security Framework
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 121
    oahas start selector: Page 11
  oahas source: Industrial Internet of Things Volume G4: Security Framework
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 121
    oahas start selector: Page 11
  oahas source: Industrial Internet of Things Volume G4: Security Framework

IIRA System Characteristic
creator: sebastian
type: Class
type: NamedIndividual
subclass of: Standard Classification
subclass of: Restriction
  has value: IIRA Functional Viewpoint
  on property: isPartOf
subclass of: Restriction
  has value: Industrial Internet Reference Architecture
  on property: is Described in

IIRA Usage Viewpoint
associated with: BdvaDataViualisationAndUserInteraction
associated with: DTP Ecosystem
associated with: FIWARE Advanced Web-based User Interface
associated with: IVI Management View
type: NamedIndividual
type: Standard Classification
type: Viewpoint
note: Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.2 USAGE VIEWPOINT' 'Page 16'
is Described in: Industrial Internet Reference Architecture
alignes With: BdvaDataViualisationAndUserInteraction
alignes With: DTP Ecosystem
alignes With: FIWARE Advanced Web-based User Interface
alignes With: IVI Management View
frames: ProcessPlanning
frames: Dynamic Adjustability
frames: Evolvability
frames: Role Categorization
frames: Service Choreography
frames: Service Composition
frames: Service Deployment
frames: Service life-cycle management
frames: Service Orchestration

IIRAUsageViewpointAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IIRA Usage Viewpoint
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 25
    oahas start selector: Page 22
  oahas source: Industrial Internet Architecture Version 1
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 25
    oahas start selector: Page 22
  oahas source: Industrial Internet Architecture Version 1

IICF
type: NamedIndividual
type: Standarization Framework
comment: Industrial Internet Connectivity Framework

IIoTConsortium
creator: sebastian
type: Class
subclass of: Organization

IPSO
creator: sebastian
type: NamedIndividual
type: Organization
type: IIoTConsortium
comment: The Alliance is a global non-profit organization serving the various communities seeking to establish the Internet Protocol as the network for the connection of Smart Objects by providing coordinated marketing efforts available to the general public. (source: https://www.postscapes.com/internet-of-things-protocols/)
has official resource: www.ipso-alliance.org

IPv4 Support
creator: sebastian
has stakeholder: System Architect
type: NamedIndividual
type: Concern
comment: Communication with non-IPv6 networks must be possible (IPv4, others).
see also: IoT-A Requirement UNI.313
has d bpedia resource: Internet Protocol
supports: Syntactic Interoperability

IPv6
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: IPv6, is an Internet Layer protocol for packet-switched internetworking and provides end-to-end datagram transmission across multiple IP networks. (source: https://www.postscapes.com/internet-of-things-protocols/)
has wikipedia article: IPv6
has Target Concern: Syntactic Interoperability

IPv6 Support
creator: sebastian
has stakeholder: System Architect
type: NamedIndividual
type: Concern
comment: A system built using the ARM shall use/support common-addressing-schemes such as IPv6.
see also: IoT-A Requirement UNI.312
has d bpedia resource: Internet Protocol
supports: Syntactic Interoperability

ISA 95 Level
type: Class
comment: Describes the ISA95 levels to classify the industry Standards according to those levels. Eg., Device, SCADA, etc. It has strong relation to the RAMI Hierarchy levels
subclass of: Standard Classification

ISO/IEC 29115
type: NamedIndividual
type: Standard
has Target Concern: Authentication
has Target Concern: Identification

ISO 50001
type: NamedIndividual
type: Standard
has Target Concern: Energy management

ISO 9000
type: NamedIndividual
type: Standard
has Classification: CrossLevel
has Classification: IDS RAM Certification Perspective
has Target Concern: Quality of Service

ISO/IEC 9594
type: NamedIndividual
type: Standard
label: X.509
has Classification: Data Sovereignty
has Classification: IDS RAM Certification Perspective
has Classification: IDS RAM Security Perspective

ISO/IEC 9594-8
type: NamedIndividual
type: Standard
has Classification: Data Sovereignty
has Classification: IDS RAM Certification Perspective
has Classification: IDS RAM Security Perspective

IT Manager
comment: An IT manager is responsible for the functioning of the IT services of an organisation.
note: Publications referred: 'IIC:PUB:G1:V1.80:20170131' '1.5 AUDIENCE' 'Page 7'
has wikipedia article: IT managers

Industrial Value Chain Reference Architecture
associated with: Industrial Value Chain Initiative
type: NamedIndividual
type: Architecture Description
type: Standarization Framework
comment: The Reference Architecture (IVRA) of the Industrial Value Chain Initive (IVI) proposes a system architecture for the manufactoring domain targeting interoperability and communicational aspects.
alternative label: IVRA
has official resource: doc 161208 Industrial Value Chain Reference Architecture.pdf

Identification
associated with: Identification
associated with: IEC_24760
associated with: IEC_62443
associated with: ISO_24760
type: NamedIndividual
type: Concern
type: Standard Classification
comment: The concern how to identify a participant (client, endpoint etc.) in the internet.
see also: IoT-A Requirement UNI.030
see also: IoT-A Requirement UNI.425
see also: IoT-A Requirement UNI.428
see also: IoT-A Requirement UNI.622
note: Publications referred: '<https://doi.org/10.1016/j.jksuci.2016.10.003>' 'Survey on domain specific IoT architectures' 'Page 299'
has d bpedia resource: Identification (information)
alignes With: Identification
alignes With: IEC_24760
alignes With: IEC_62443
alignes With: ISO_24760
supports: Identity Management

Identity Management
creator: sebastian
type: NamedIndividual
type: Concern
comment: In computer security, identity and access management (IAM) is the security and business discipline that "enables the right individuals to access the right resources at the right times and for the right reasons".It addresses the need to ensure appropriate access to resources across increasingly heterogeneous technology environments and to meet increasingly rigorous compliance requirements. (source: wikipedia)
see also: IoT-A Requirement UNI.048
see also: IoT-A Requirement UNI.432
has d bpedia resource: Identity management
supports: Non-repudiation

IDS RAM Perspective
creator: sebastian
type: Class
type: NamedIndividual
subclass of: Standard Classification
equivalent class: Class
  one of: IDS RAM Certification Perspective
  one of: IDS RAM Governance Perspective
  one of: IDS RAM Security Perspective

Connectivity Layer
creator: sebastian
type: Class
type: NamedIndividual
comment: Connectivity Layer of the Internet Connectivity Framework
label: IICF Connectivity Layer
subclass of: Standard Classification
subclass of: Restriction
  has value: IIRA Connectivity
  on property: isPartOf

IicfConnectivityLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: Connectivity Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 17
    oahas start selector: Page 14
  oahas source: The Industrial Internet of Things Volume G5: Connectivity Framework
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 17
    oahas start selector: Page 14
  oahas source: The Industrial Internet of Things Volume G5: Connectivity Framework

AII Industrial Internet Architecture
type: NamedIndividual
type: Architecture Description
has official resource: Industrial.pdf
has Publisher: Alliance of Industrial Internet

Industrial Internet Architecture Version 1
type: NamedIndividual
type: oaSpecificResource
has open resource: Industrial.pdf

Industrial Internet of Things Volume G4: Security Framework
type: NamedIndividual
type: oaSpecificResource
note: Industrial Internet of Things Volume G4: Security Framework IIC:PUB:G4:V1.0:PB:20160926
has open resource: IIC PUB G4 V1.00 PB-3.pdf

Industrial Value Chain Reference Architecture (IVRA)
type: NamedIndividual
type: oaSpecificResource
comment: Industrial Value Chain Reference Architecture (IVRA) Industrial Value Chain Initiative
has open resource: doc 161208 Industrial Value Chain Reference Architecture.pdf

Industrial Value Chain Reference Architecture (IVRA)- Next
type: NamedIndividual
type: oaSpecificResource
note: Industrial Value Chain Reference Architecture (IVRA) Industrial Value Chain Initiative Next
has open resource: r26680

Information Security
creator: SebastianBader
type: NamedIndividual
type: Concern
supports: Security

Information Privacy
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: The IoT utilizes different sort of object distinguishing proof advancements, e.g., RFID, 2D-standardized tags and so forth. Since each kind of day by day use articles will convey these recognizable proof labels and insert the particular object data, it is important to take legal protection measures and prevent unauthorized access.
has wikipedia article: Information privacy
supports: Privacy

Integrity Protection and Verification
creator: sebastian
has stakeholder: Device/Service Owner
type: NamedIndividual
type: Concern
comment: In telecommunications, the term system integrity has the following meanings: 1. * That condition of a system wherein its mandated operational and technical parameters are within the prescribed limits. 2. * The quality of an AIS when it performs its intended function in an unimpaired manner, free from deliberate or inadvertent unauthorized manipulation of the system. 3. * The state that exists when there is complete assurance that under all conditions an IT system is based on the logical correctness and reliability of the operating system, the logical completeness of the hardware and software that implement the protection mechanisms, and data integrity. (source: wikipedia)
comment: Integrity protection and verification of the software stack installed; local integrity protection would be something like trusted boot; remote integrity verification means support for remote attestation.
see also: IoT-A Requirement UNI.066
see also: IoT-A Requirement UNI.603
see also: IoT-A Requirement UNI.620
alternative label: Attestation
has d bpedia resource: System integrity
supports: Device Security

FIWARE Interface to Networks and Devices
creator: sebastian
associated with: IDS RAM Process Layer
associated with: IDS RAM System Layer
associated with: NGSI-LD Architecture
associated with: OpenDaylight
type: NamedIndividual
type: Fiware Chapter
type: Standard Classification
comment: The GEs in the I2ND chapter provide three sets of functionalities. The first is an advanced integration middleware to be used by all FIWARE GEs with high performance communication needs Open networking elements enable cloud network application developers to build value-added services in private, enterprise and public settings. The third set of functionalities enables the management of robots by means of platform components and interfaces towards other FIWARE GEs, allowing users to develop smarter and faster robotic applications.
is Described in: FIWARE Architecture
alignes With: IDS RAM Process Layer
alignes With: IDS RAM System Layer
alignes With: NGSI-LD Architecture
frames: Cloud Computing Capability
frames: Data Description
frames: Data Processing
frames: Data Sovereignty
frames: Endpoint Description
frames: Endpoint Invocation
frames: Interoperability
frames: Internet of Things
frames: Privacy
frames: Quality of Service
frames: Scalability
frames: Security
frames: Semantic Interoperability
frames: Service Composition
frames: Service Description
frames: Service Orchestration
frames: Syntactic Interoperability
frames: Trustworthiness

Interoperability
has stakeholder: GeneralMAnager
has stakeholder: Q1548249
type: NamedIndividual
type: Concern
comment: A systems ability to connect with other systems.
comment: Interoperability refers to the ability of two or more devices from the same vendor, or different vendors, to exchange information and use that information for correct co-operation [IEC61850-2010].
see also: IoT-A Requirement UNI.008
see also: IoT-A Requirement UNI.010
see also: IoT-A Requirement UNI.023
see also: IoT-A Requirement UNI.042
see also: IoT-A Requirement UNI.047
see also: IoT-A Requirement UNI.093
see also: IoT-A Requirement UNI.094
see also: IoT-A Requirement UNI.232
see also: IoT-A Requirement UNI.712
has d bpedia resource: Interoperability

Internet of Things
type: NamedIndividual
type: Concern
comment: The internet of things (IoT) is the internetworking of physical devices, vehicles (also referred to as "connected devices" and "smart devices"), buildings and other items—embedded with electronics, software, sensors, actuators, and network connectivity that enable these objects to collect and exchange data. (source: wikipedia)
label: IoT
see also: IoT-A Requirement UNI.213
has d bpedia resource: Internet of things

IoT Architecture
associated with: IoT-A Reference Architecture
type: NamedIndividual
type: Organization
type: IIoTConsortium
comment: After much discussion about the core concepts of the IoT for several years, in 2009 a group of researchers from more than 20 large industrial companies and research institutions joined forces to lay the foundation for the much needed common ground or a common “architecture” for the Internet of Things: the IoTArchitecture project (IoT-A) was born. IoT-A has become the European Commission’s flagship project in the European Union’s Seventh Framework Program for Research and Development with respect to establishing an architecture for the Internet of Things.
label: IoT-A

IoTivity
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: IoTivity is an open source project hosted by the Linux Foundation, and sponsored by the OIC. (source: https://www.postscapes.com/internet-of-things-protocols/)
has official resource: www.iotivity.org

IoT-A Availability and Resilience
associated with: Security
type: NamedIndividual
type: IoT-A Perspective
type: Standard Classification
is Described in: IoT-A Reference Architecture
alignes With: Security
frames: Availability
frames: Resilience
frames: Security
frames: Trustworthiness

IotaAvailabilityResilienceAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IoT-A Availability and Resilience
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 156
    oahas start selector: Page 155
  oahas source: Final architectural reference model for the IoT v3 0
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 156
    oahas start selector: Page 155
  oahas source: Final architectural reference model for the IoT v3 0

IoT-A Deployment and Operation
creator: sebastian
associated with: IDS RAM System Layer
associated with: IIRA Implementation Viewpoint
type: NamedIndividual
type: Standard Classification
type: Viewpoint
is Described in: IoT-A Reference Architecture
alignes With: IDS RAM System Layer
alignes With: IIRA Implementation Viewpoint
frames: EnergyEfficiency
frames: Dynamic Adjustability
frames: Evolvability
frames: Service Choreography
frames: Service Composition
frames: Service Deployment
frames: Service life-cycle management
frames: Service Orchestration

IotaDeploymentOperationViewpointAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IoT-A Deployment and Operation
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 149
    oahas start selector: Page 141
  oahas source: Final architectural reference model for the IoT v3 0
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 149
    oahas start selector: Page 141
  oahas source: Final architectural reference model for the IoT v3 0

IoT-A Evolution and Interoperability
associated with: IIRA Connectivity
associated with: RAMI Integration Layer
type: NamedIndividual
type: IoT-A Perspective
type: Standard Classification
is Described in: IoT-A Reference Architecture
alignes With: IIRA Connectivity
alignes With: RAMI Integration Layer
frames: Dynamic Adjustability
frames: Evolvability
frames: Interoperability
frames: Service Choreography
frames: Service Composition
frames: Service Orchestration

IotaEvolutionInteroperabilityAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IoT-A Evolution and Interoperability
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 151
    oahas start selector: Page 150
  oahas source: Final architectural reference model for the IoT v3 0
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 151
    oahas start selector: Page 150
  oahas source: Final architectural reference model for the IoT v3 0

IoT-A Functional Viewpoint
creator: sebastian
associated with: IDS RAM Process Layer
associated with: IDS RAM Security Perspective
associated with: IIRA Functional Viewpoint
associated with: RAMI Asset Layer
associated with: RAMIFunctional
type: NamedIndividual
type: Standard Classification
type: Viewpoint
is Described in: IoT-A Reference Architecture
alignes With: IDS RAM Process Layer
alignes With: IDS RAM Security Perspective
alignes With: IIRA Functional Viewpoint
alignes With: RAMI Asset Layer
alignes With: RAMI Functional Layer
frames: Configuration
frames: ProcessPlanning
frames: Authentication
frames: Authorization
frames: Communication
frames: Data Sovereignty
frames: Identity Management
frames: Privacy
frames: Security
frames: Service Choreography
frames: Service Composition
frames: Service Orchestration
frames: Thing representation
frames: Trustworthiness
frames: Virtual Entity

IotaFunctionalViewpointAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IoT-A Functional Viewpoint
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 126
    oahas start selector: Page 105
  oahas source: Final architectural reference model for the IoT v3 0
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 126
    oahas start selector: Page 105
  oahas source: Final architectural reference model for the IoT v3 0

IoT-A Information Viewpoint
creator: sebastian
associated with: IDS RAM Information Layer
associated with: IDS RAM Process Layer
associated with: IIRA Control Domain
associated with: IIRA Operation Domain
associated with: InformationDomain
associated with: RAMI Communication Layer
type: NamedIndividual
type: Standard Classification
type: Viewpoint
comment: One of the main purposes of connected and smart objects in the IoT is the exchange of information between each other and also with external systems. Therefore the way how to define, structure, store, process, manage and exchange information is very important. The information view helps to generate an overview about static information structure and dynamic information flow. (source: Bassi et al.: Enabling Things to Talk)
has official resource: http://doi.org/10.1007/978-3-642-40403-0
is Described in: IoT-A Reference Architecture
alignes With: IDS RAM Information Layer
alignes With: IDS RAM Process Layer
alignes With: IIRA Control Domain
alignes With: IIRA Operation Domain
alignes With: InformationDomain
alignes With: RAMI Communication Layer
frames: Communication
frames: Data Analytics
frames: Data at rest
frames: DataInMotion
frames: Data lifecycle management
frames: Endpoint Invocation
frames: Interoperability
frames: Semantic Interoperability
frames: Service Description
frames: Syntactic Interoperability
frames: Thing representation
frames: Virtual Entity

IotaInformationViewpointAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IoT-A Information Viewpoint
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 141
    oahas start selector: Page 126
  oahas source: Final architectural reference model for the IoT v3 0
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 141
    oahas start selector: Page 126
  oahas source: Final architectural reference model for the IoT v3 0

IoT-A Performance and Scalability
type: NamedIndividual
type: IoT-A Perspective
type: Standard Classification
is Described in: IoT-A Reference Architecture
frames: Communication
frames: Interoperability
frames: Network performance
frames: Quality of Service
frames: Scalability
frames: Semantic Interoperability
frames: Service Description

IotaPerformanceScalabilityAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IoT-A Performance and Scalability
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 152
    oahas start selector: Page 151
  oahas source: Final architectural reference model for the IoT v3 0
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 152
    oahas start selector: Page 151
  oahas source: Final architectural reference model for the IoT v3 0

IoT-A Perspective
creator: sebastian
type: Class
type: NamedIndividual
subclass of: Standard Classification

IotaPerspectiveAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IoT-A Perspective
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 156
    oahas start selector: Page 149
  oahas source: Final architectural reference model for the IoT v3 0
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 156
    oahas start selector: Page 149
  oahas source: Final architectural reference model for the IoT v3 0

IoT-A Reference Architecture
creator: sebastian
type: NamedIndividual
type: Architecture Description
type: Standarization Framework
has Publisher: IoT Architecture

IotaReferenceArchitectureAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IoT-A Reference Architecture
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 482
    oahas start selector: Page 1
  oahas source: Final architectural reference model for the IoT v3 0
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 482
    oahas start selector: Page 1
  oahas source: Final architectural reference model for the IoT v3 0

IoT-A Trust Security and Privacy
associated with: IDS RAM Security Perspective
associated with: IIRA Security
type: NamedIndividual
type: IoT-A Perspective
type: Standard Classification
is Described in: IoT-A Reference Architecture
alignes With: IDS RAM Security Perspective
alignes With: Security
frames: Data Sovereignty
frames: Privacy
frames: Security
frames: Trustworthiness

IotaTrustSecurityPrivacyAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IoT-A Trust Security and Privacy
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 155
    oahas start selector: Page 152
  oahas source: Final architectural reference model for the IoT v3 0
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 155
    oahas start selector: Page 152
  oahas source: Final architectural reference model for the IoT v3 0

IPSO App Framework
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: IPSO Application Framework (PDF): This design defines sets of REST interfaces that may be used by a smart object to represent its available resources, interact with other smart objects and backend services. This framework is designed to be complementary to existing Web profiles including SEP2 and oBIX. (source: https://www.postscapes.com/internet-of-things-protocols/)
has official resource: draft-ipso-app-framework-04.pdf

Industrial Value Chain Initiative
creator: sebastian
type: NamedIndividual
type: Organization
type: IIoTConsortium
comment: The Industrial Value Chain Initiative (IVI) is a forum to design a new society by combining manufacturing and information technologies, and for all enterprises to take an initiative collaboratively.
label: IVI
has official resource: iv-i.org

IVI Activity Layer
creator: sebastian
associated with: Engineering
associated with: Manufacturing
type: NamedIndividual
type: IVI Layer
type: Standard Classification
comment: The activity layer has a view point of activities actually conducted at various places in manufacturers. People and machines acting voluntarily, human activity, machine processes, and information as an object og such activities and processes are brought up for discussion. In every production site of every manufacturer, concrete manufacturing activities are conducted in a different way. (source: IVRA-Next)
is Described in: Industrial Value Chain Reference Architecture
alignes With: Engineering
alignes With: Manufacturing
frames: ProcessPlanning

IviActivityLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IVI Activity Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 5
    oahas start selector: Page 4
  oahas source: Industrial Value Chain Reference Architecture (IVRA)- Next
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 6
    oahas start selector: Page 5
  oahas source: Industrial Value Chain Reference Architecture (IVRA)- Next

IVI Activity View
creator: sebastian
associated with: Engineering
associated with: IIRA Operation Domain
type: NamedIndividual
type: Standard Classification
type: Viewpoint
is Described in: Industrial Value Chain Reference Architecture
alignes With: Engineering
alignes With: IIRA Operation Domain
frames: Manufacturing

IviActivityViewAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IVI Activity View
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 3
    oahas start selector: Page 2
  oahas source: Industrial Value Chain Reference Architecture (IVRA)
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 4
    oahas start selector: Page 2
  oahas source: Industrial Value Chain Reference Architecture (IVRA)

IVI Asset View
creator: sebastian
associated with: IIRA Physical Systems
associated with: RAMI Asset Layer
type: NamedIndividual
type: Standard Classification
type: Viewpoint
is Described in: Industrial Value Chain Reference Architecture
alignes With: IIRA Physical Systems
alignes With: RAMI Asset Layer
frames: Thing representation

IviAssetViewAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IVI Asset View
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 2
    oahas start selector: Page 1
  oahas source: Industrial Value Chain Reference Architecture (IVRA)
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 2
    oahas start selector: Page 1
  oahas source: Industrial Value Chain Reference Architecture (IVRA)

IVI Business Layer
creator: sebastian
associated with: IIRA Business Viewpoint
associated with: RAMI Business Layer
type: NamedIndividual
type: IVI Layer
type: Standard Classification
comment: In the business layer, from a perspective of enterprise management, the focus of discussions is placed on the fundamentel structure of manufacturing, organization forms for manufacturing, presence of essential perspectives and axes as well as a philosophy and concept of values underpinning the big picture. (source: IVRA-Next)
is Described in: Industrial Value Chain Reference Architecture
alignes With: IIRA Business Viewpoint
alignes With: RAMI Business Layer
frames: Business Context
frames: Business Transactions

IviBusinessLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IVI Business Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 5
    oahas start selector: Page 4
  oahas source: Industrial Value Chain Reference Architecture (IVRA)- Next
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 6
    oahas start selector: Page 5
  oahas source: Industrial Value Chain Reference Architecture (IVRA)- Next

IVI Layer
creator: sebastian
type: Class
comment: A IVI Layer describes one of three layers of smart manufactoring as proposed by the Industrial Value Chain Initiative (IVI).
subclass of: Standard Classification

IVI Management View
creator: sebastian
associated with: IIRA Usage Viewpoint
associated with: RAMI Functional Layer
type: NamedIndividual
type: Standard Classification
type: Viewpoint
is Described in: Industrial Value Chain Reference Architecture
alignes With: IIRA Usage Viewpoint
alignes With: RAMI Functional Layer
frames: Business Context
frames: Business Transactions
frames: Maintenance Cost
frames: Quality of Service
frames: Service level agreement
frames: Service life-cycle management

IviManagementViewAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IVI Management View
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 4
    oahas start selector: Page 3
  oahas source: Industrial Value Chain Reference Architecture (IVRA)
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 4
    oahas start selector: Page 3
  oahas source: Industrial Value Chain Reference Architecture (IVRA)

IVI Specification Layer
creator: sebastian
associated with: Engineering
associated with: TypeDevelopment
type: NamedIndividual
type: IVI Layer
type: Standard Classification
comment: In the specification layer, the following will be considered: Specific operations based on human activities and machine processes and the things and information items that are their subjects, as well as the data and their attributes that are the subject of the processes executed by logic in software. (source: IVRA-Next)
is Described in: Industrial Value Chain Reference Architecture
alignes With: Engineering
alignes With: TypeDevelopment
frames: Data Processing

IviSpecificationLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: IVI Specification Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 5
    oahas start selector: Page 4
  oahas source: Industrial Value Chain Reference Architecture (IVRA)- Next
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 6
    oahas start selector: Page 5
  oahas source: Industrial Value Chain Reference Architecture (IVRA)- Next

JMS
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: JMS (Java Message Service) - A Java Message Oriented Middleware (MOM) API for sending messages between two or more clients. (source: https://www.postscapes.com/internet-of-things-protocols/)

Jurisdictional Issues
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: It is often challenging to alter resources, for example, the server or data centres to a particular geographic area. Load balancing service provider of the cloud, the availability of the network, or the performance of the data centre are few factors that determine where the data is stored. Accordingly, an organization data might be stored in a different location with various legal jurisdictions and diverse laws concerning the security issues, such as the protection and interruptions of the data
has wikipedia article: Jurisdiction
supports: Cloud Computing Capability

LatencyReduction
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: Latency is a time interval between the stimulation and response, or, from a more general point of view, a time delay between the cause and the effect of some physical change in the system being observed.
has wikipedia article: Latency (engineering)
supports: Communication

Layer
type: Class
comment: Describes the layers of the standardization frameworks. In some cases, the layers are connected to dimensions of the frameworks.

6LoWPAN
creator: IETF
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: 6LoWPAN is an acronym of IPv6 over Low power Wireless Personal Area Networks. It is an adaption layer for IPv6 over IEEE802.15.4 links. This protocol operates only in the 2.4 GHz frequency range with 250 kbps transfer rate. (source: https://www.postscapes.com/internet-of-things-protocols/)
maker: IETF
has Classification: IIRA Connectivity
has Classification: RAMI Communication Layer
has d bpedia resource: 6LoWPAN
has Developer: IETF
has Publisher: IETF
has wikipedia article: 6LoWPAN
has Target Concern: Communication

Local Data Confidentiality
creator: sebastian
type: NamedIndividual
type: Concern
comment: Describes the means by which local data is protected.

Logging
type: NamedIndividual
type: Concern
comment: The process of recording incidents and events regarding a specific service, data resource or device in order to make status changes transparent.
see also: IoT-A Requirement UNI.409
see also: IoT-A Requirement UNI.710
has d bpedia resource: Data logger
supports: Data Usage Control
supports: Service Access Control

Long Term Business Sustainability
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: The provider should not go broke, be financially in a close-fitting corner or close down the business. Organizations should be sure and know how to move your data to another cloud provider. And should know how to have a backup at another public cloud of data for redundancy
has wikipedia article: Sustainability
supports: Business Context

Machine Learning
creator: sebastian
type: NamedIndividual
type: Concern
comment: Machine learning is the subfield of computer science that "gives computers the ability to learn without being explicitly programmed" (Arthur Samuel, 1959). Evolved from the study of pattern recognition and computational learning theory in artificial intelligence, machine learning explores the study and construction of algorithms that can learn from and make predictions on data – such algorithms overcome following strictly static program instructions by making data-driven predictions or decisions, through building a model from sample inputs. (source: wikipedia)
has d bpedia resource: Machine learning
supports: Artificial Intelligence

Maintenance Cost
type: NamedIndividual
type: Concern
comment: The ability of a system to be maintained.
note: Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '3 Use Cases for Fog' 'Page 13'
note: Publications referred: 'IIC:PUB:G1:V1.80:20170131' '4 BUSINESS VIEWPOINT' 'Page 20'
supports: Business Context

Message precedence
has stakeholder: Q1548249
has stakeholder: Developer
type: NamedIndividual
type: Concern
comment: Message precedence is an indicator attached to a message indicating its level of urgency. (source: wikipedia)
see also: IoT-A Requirement UNI.028
has d bpedia resource: Message precedence
supports: Communication

Mobil Devices
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: How to handle the massive mobility of vehicles? In the case of an application scenario that involves connected vehicles, mobility is a major issue and includes data consumer as well as data producer. In this particular case, one of the influencing factors is the potential speed of a vehicle. High-speed mobility may lead to situations in which a request for data or a service may not be answered before the vehicle disconnects and re-connects to another network entry point. This leads to unfulfilled requests and potential duplication of efforts.
supports: Internet of Things

Muhammad Usman
type: NamedIndividual
type: Person

Multicast
see also: IoT-A Requirement UNI.302
see also: IoT-A Requirement UNI.303
see also: IoT-A Requirement UNI.304
see also: IoT-A Requirement UNI.305

Multilateralism
creator: sebastian
type: NamedIndividual
type: Concern
comment: Data Artefacts are received by 1 to m Data Consumer.
alternative label: Cardinality of Participants
alternative label: Multicast
supports: CardinalityOfDataSources

MultipleIdenities
see also: IoT-A Requirement UNI.320

Multiple Identities
creator: sebastian
type: NamedIndividual
type: Concern
comment: Devices must be able to switch between different networks without losing connections (Network handover/handoff support).
supports: Identity Management

Next Generation Service Interface
creator: FIWARE Architecture
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: The FIWARE NGSI (Next Generation Service Interface) API defines - a data model for context information, based on a simple information model using the notion of context entities - a context data interface for exchanging information by means of query, subscription, and update operations - a context availability interface for exchanging information on how to obtain context information (whether to separate the two interfaces is currently under discussion).
label: NGSI
maker: FIWARE Architecture
has official resource: stable
has Publisher: FIWARE Architecture

NGSI-LD
creator: sebastian
type: Class
label: NGSI Context Information Management API
subclass of: Standard Classification
subclass of: Restriction
  has value: FIWARE Architecture
  on property: is Described in

Network performance
type: NamedIndividual
type: Concern
comment: Network performance refers to measures of service quality of a network as seen by the customer. There are many different ways to measure the performance of a network, as each network is different in nature and design. (source: wikidata)
see also: IoT-A Requirement UNI.252
has d bpedia resource: Network performance
supports: Communication
supports: Quality of Service

network security
creator: SebastianBader
type: NamedIndividual
type: Concern
comment: Data flow is an integral part of any cloud service over the network of computers or clusters of systems using internet. Any intruder can analyze the data packet to detect any weakness in the system and can gain access to applications and data using some kind of remote access mechanism and injection like SQL and some bad command, Denial of Service (DoS), Distributed DoS (DDoS), man in the middle attacks, social networking attacks and some unauthorized attacks are the major entrance level attacks in cloud computing environment.
has wikipedia article: Audit
has wikipedia article: Network security
supports: Security

Network Virtualization
creator: sebastian
type: NamedIndividual
type: Concern
comment: The system shall support network virtualisation, i.e. the usage of virtual overlay networks.
see also: IoT-A Requirement UNI.328
has wikipedia article: Network virtualization
supports: Communication

NGSI-LD API Operation
associated with: FIWARE Data/Context Management
associated with: IDS RAM Process Layer
associated with: IDS RAM System Layer
associated with: IIRA Connectivity
associated with: IIRA Control Domain
type: NamedIndividual
type: NGSI-LD
type: Standard Classification
is Described in: FIWARE Architecture
alignes With: FIWARE Data/Context Management
alignes With: IDS RAM Process Layer
alignes With: IDS RAM System Layer
alignes With: IIRA Connectivity
alignes With: IIRA Control Domain
frames: Communication
frames: Endpoint Invocation
frames: Interoperability
frames: Syntactic Interoperability

NGSI-LD Architecture
associated with: FIWARE Applications Services and Data Delivery
associated with: FIWARE Cloud Hosting
associated with: IDS RAM System Layer
associated with: IIRA Implementation Viewpoint
associated with: FIWARE Interface to Networks and Devices
associated with: RAMI Integration Layer
type: NamedIndividual
type: NGSI-LD
type: Standard Classification
is Described in: FIWARE Architecture
alignes With: FIWARE Applications Services and Data Delivery
alignes With: FIWARE Cloud Hosting
alignes With: IDS RAM System Layer
alignes With: IIRA Implementation Viewpoint
alignes With: FIWARE Interface to Networks and Devices
alignes With: RAMI Integration Layer
frames: ProcessPlanning
frames: Interoperability
frames: Syntactic Interoperability

NGSI-LD Data Representation
associated with: FIWARE Data/Context Management
associated with: IDS RAM Information Layer
associated with: RAMI Functional Layer
associated with: RDF
type: NamedIndividual
type: NGSI-LD
type: Standard Classification
is Described in: FIWARE Architecture
alignes With: FIWARE Data/Context Management
alignes With: IDS RAM Information Layer
alignes With: RAMI Functional Layer
frames: Data Description
frames: Interoperability
frames: Semantic Interoperability

NGSI-LD Information Model
creator: sebastian
associated with: FIWARE Data/Context Management
associated with: IDS RAM Information Layer
associated with: InformationDomain
associated with: RAMI Information Layer
type: NamedIndividual
type: NGSI-LD
type: Standard Classification
comment: The FIWARE data models have been harmonized to enable data portability for different applications including, but not limited, to Smart Cities. They are intended to be used together with FIWARE NGSI version 2. If you want to contribute and create additional data models, please have a look at our repository of data models and the data model development guidelines. (source: https://www.fiware.org/developers/data-models/)
is Described in: FIWARE Architecture
alignes With: FIWARE Data/Context Management
alignes With: IDS RAM Information Layer
alignes With: InformationDomain
alignes With: RAMI Information Layer
frames: Data Analytics
frames: Data Description
frames: Geospatial data and information
frames: Interoperability
frames: Semantic Interoperability

Non-repudiation
creator: sebastian
type: NamedIndividual
type: Concern
comment: In digital security, non-repudiation means: (a) A service that provides proof of the integrity and origin of data. (b) An authentication that can be said to be genuine with high confidence. The most common method of verifying the digital origin of data is through digital certificates, a form of public key infrastructure that includes digital signatures.
see also: IoT-A Requirement UNI.619
has d bpedia resource: Non-repudiation
has wikipedia article: Non-repudiation
supports: Integrity Protection and Verification

ODRL
creator: W3C
type: NamedIndividual
type: Document
type: Publication
type: Standard
comment: The Open Digital Rights Language (ODRL) is a policy expression language that provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for representing statements about the usage of content and services. The ODRL Information Model describes the underlying concepts, entities, and relationships that form the foundational basis for the semantics of the ODRL policies. Policies are used to represent permitted and prohibited actions over a certain asset, as well as the obligations required to be meet by stakeholders. In addition, policies may be limited by constraints (e.g., temporal or spatial constraints) and duties (e.g. payments) may be imposed on permissions.
label: Open Digital Rights Language
maker: W3C
has Classification: IDS RAM Information Layer
has Classification: IDS RAM Security Perspective
has official resource: odrl-model
has Publisher: W3C

OpenFog Agility Pillar
creator: sebastian
type: NamedIndividual
type: Standard Classification
comment: The agility pillar addresses business operational decisions for an OpenFog RA deployment. It is not possible for humans alone to analyze the data generated at the scale predicted by IoT as the basis for rapid, sound business and operational decisions. The agility pillar focuses on transforming this volume of data into actionable insights. Agility also deals with the highly dynamic nature of fog deployments and the need to respond quickly to change. source: OpenFog Reference Architecture
note: Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.7 Agility Pillar' 'Page 31'
is Described in: OpenFog Reference Architecture
frames: Agility

OFRAAgilityPillarAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OpenFog Agility Pillar
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 32
    oahas start selector: Page 31
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 32
    oahas start selector: Page 31
  oahas source: OpenFog Reference Architecture for Fog Computing

OpenFog AutonomyPillar
creator: sebastian
type: NamedIndividual
type: Standard Classification
comment: The autonomy pillar enables fog nodes to continue to deliver the designed functionality in the face of the external service failures. In this architecture, autonomy is supported throughout the hierarchy. Decision making will be made at all levels of a deployment’s hierarchy including near the device or higher order layers. Centralized decision-making in the cloud is no longer the only option. Autonomy at the network edge means intelligence from local devices and peer data can be used to fulfill the business’ mission at the point where it makes the most business sense.
note: Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.4 Autonomy Pillar' 'Page 27'
is Described in: OpenFog Reference Architecture
frames: Autonomous Communication
frames: Autonomous Configuration

OFRAAutonomyPillarAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OpenFog AutonomyPillar
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 29
    oahas start selector: Page 27
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 29
    oahas start selector: Page 27
  oahas source: OpenFog Reference Architecture for Fog Computing

OpenFog Data Analytics and Control Perspective
creator: sebastian
type: NamedIndividual
type: Standard Classification
is Described in: OpenFog Reference Architecture
alignes With: IIRA Control Domain
alignes With: InformationDomain
frames: Data Analytics

OFRADataAnalyticsAndControlPerspectiveAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OpenFog Data Analytics and Control Perspective
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 56
    oahas start selector: Page 54
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 56
    oahas start selector: Page 54
  oahas source: OpenFog Reference Architecture for Fog Computing

OpenFog Deployment Viewpoint
creator: sebastian
type: NamedIndividual
type: Viewpoint
comment: How fog software and fog systems are deployed to address a given scenario is also very important. There are many deployment types ranging from embedded to large clustered systems that are fully interconnected. The deployment type(s) chosen are scenario specific, but key aspects of the architecture remain visible regardless of deployment type. However, some may grow or shrink in importance. source: OpenFog Reference Architecture
is Described in: OpenFog Reference Architecture
alignes With: IIRA Implementation Viewpoint
frames: Service Deployment

OFRADeploymentViewpointAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OpenFog Deployment Viewpoint
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 39
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 40
    oahas start selector: Page 39
  oahas source: OpenFog Reference Architecture for Fog Computing

OpenFog Functional Viewpoint
creator: sebastian
type: NamedIndividual
type: Viewpoint
comment: The functional viewpoint of the architecture shows how we apply the OpenFog architectural elements and views to address the various concerns of the stakeholders to satisfy a given scenario. Each scenario chosen will focus on a different aspects and market opportunities for fog computing. We fully expect that the architectural description, views, and perspective may change over time. This change and refinement should be driven from testbeds and application of the OpenFog RA to multiple different markets we see as important to fog computing. source: OpenFog Reference Architecture
is Described in: OpenFog Reference Architecture

OFRAFunctionalViewpointAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OpenFog Functional Viewpoint
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 39
    oahas start selector: Page 38
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 39
    oahas start selector: Page 38
  oahas source: OpenFog Reference Architecture for Fog Computing

OpenFog Hierarchy Pillar
creator: sebastian
type: NamedIndividual
type: Standard Classification
comment: OpenFog RA computing resources can be seen as a logical hierarchy based on the functional requirements of an end-to-end IoT system. Depending on the scale and nature of the scenario being addressed, the hierarchy may be a network of smart and connected partitioned systems arranged in physical or logical layers, or it may collapse into a single physical system (scalability pillar). source: OpenFog Reference Architecture
note: Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.8 Hierarchy Pillar' 'Page 31'
is Described in: OpenFog Reference Architecture
frames: Business Value
frames: Data Analytics
frames: Sensing

OFRAHierarchyPillarAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OpenFog Hierarchy Pillar
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 34
    oahas start selector: Page 31
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 34
    oahas start selector: Page 31
  oahas source: OpenFog Reference Architecture for Fog Computing

OpenFog IT Business and Cross-fog Applications Perspective
creator: sebastian
type: NamedIndividual
type: Standard Classification
comment: Fog applications and services should have the flexibility to span and interoperate with various levels in a fog hierarchy. This is a foundational aspect of fog computing that enables a multi-vendor ecosystem. In addition, the data that is collected or generated by one fog node should be shareable with other nodes in the hierarchy. The figure below shows a cross-fog application spanning east to west nodes (it would also be able to span north to south). source: OpenFog Reference Architecture
is Described in: OpenFog Reference Architecture
frames: Business Context

OFRAItBusinessAndCrossFogApplicationsPerspectiveAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OpenFog IT Business and Cross-fog Applications Perspective
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 57
    oahas start selector: Page 56
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 57
    oahas start selector: Page 56
  oahas source: OpenFog Reference Architecture for Fog Computing

OpenFog Manageability Perspective
creator: sebastian
type: NamedIndividual
type: Standard Classification
comment: Many fog computing deployments involve machine vision, and associated human-like functions. As such, they have the ability to see, respond, remember, move, and make autonomous decisions in order to participate in other fog services. This range of actions requires a higher level of manageability than a traditional static model. In addition, fog nodes may be deployed in a wide range of locations: remote, fixed and non-fixed, and environmentally harsh conditions. source: OpenFog Reference Architecture
is Described in: OpenFog Reference Architecture
frames: Autonomous Configuration
frames: Service life-cycle management

OFRAManageabilityPerspectiveAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OpenFog Manageability Perspective
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 54
    oahas start selector: Page 51
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 54
    oahas start selector: Page 51
  oahas source: OpenFog Reference Architecture for Fog Computing

OpenFog Node View
creator: sebastian
associated with: WiFi
type: NamedIndividual
type: Viewpoint
comment: The node view is the lowest level view we currently utilize in the architectural description. The stakeholders involved in formulating the viewpoint (and subsequently this view) are the system on a chip designers, silicon manufacturers, firmware architects, and system architects. source: OpenFog Reference Architecture
is Described in: OpenFog Reference Architecture
alignes With: IDS RAM System Layer
alignes With: IIRA Physical Systems
alignes With: RAMI Asset Layer
frames: Data Storage
frames: Network performance
frames: Physical Connectivity
frames: Security

OFRANodeViewAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OpenFog Node View
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 73
    oahas start selector: Page 56
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 73
    oahas start selector: Page 56
  oahas source: OpenFog Reference Architecture for Fog Computing

OpenFog Opennes Pillar
creator: sebastian
type: NamedIndividual
type: Standard Classification
comment: Openness is essential for the success of a ubiquitous fog computing ecosystem for IoT platforms and applications. Proprietary or single vendor solutions can result in limited supplier diversity, which can have a negative impact on system cost, quality and innovation. The openness pillar importance is highlighted in our desire for fully interoperable systems, supported by a vibrant supplier ecosystem. source: OpenFog Reference Architecture
note: Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.3 Openness Pillar' 'Page 26'
is Described in: OpenFog Reference Architecture
frames: Interoperability
frames: Service Composition

OFRAOpennessPillarAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OpenFog Opennes Pillar
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 27
    oahas start selector: Page 26
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 27
    oahas start selector: Page 26
  oahas source: OpenFog Reference Architecture for Fog Computing

Performance and Scale Perspective
creator: sebastian
type: NamedIndividual
type: Standard Classification
is Described in: OpenFog Reference Architecture

OFRAPerformancePerspectiveAnno
type: NamedIndividual
type: oaAnnotation
oahas body: Performance and Scale Perspective
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 47
    oahas start selector: Page 46
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 47
    oahas start selector: Page 46
  oahas source: OpenFog Reference Architecture for Fog Computing

OpenFog Programmability Pillar
creator: sebastian
type: NamedIndividual
type: Standard Classification
comment: The programmability pillar enables highly adaptive deployments including support for programming at the software and hardware layers. This means that re-tasking a fog node or cluster of fog nodes for accommodating operational dynamics, can be completely automated. The re-tasking can be done with the help of the fog nodes inherent programmability interfaces which we describe using general purpose compute or accelerator interfaces. source: OpenFog Reference Architecture
note: Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.5 Programmability Pillar' 'Page 29'
is Described in: OpenFog Reference Architecture
frames: Programmability

OFRAProgrammabilityPillarAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OpenFog Programmability Pillar
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 30
    oahas start selector: Page 29
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 30
    oahas start selector: Page 29
  oahas source: OpenFog Reference Architecture for Fog Computing

OpenFog Scalability Pillar
creator: sebastian
type: NamedIndividual
type: Standard Classification
comment: The scalability pillar addresses the dynamic technical and business needs behind fog deployments. Elastic scalability cuts across all fog computing applications and verticals. The hierarchical properties of fog and its location at logical edges of networks add additional scaling opportunities. source: OpenFog Reference Architecture
note: Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.2 Scalability Pillar' 'Page 24'
is Described in: OpenFog Reference Architecture
frames: Scalability

OFRAScalabilityPillarAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OpenFog Scalability Pillar
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 26
    oahas start selector: Page 24
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 26
    oahas start selector: Page 24
  oahas source: OpenFog Reference Architecture for Fog Computing

OpenFog Security Perspective
creator: sebastian
type: NamedIndividual
type: Standard Classification
is Described in: OpenFog Reference Architecture
alignes With: Security
alignes With: BDVA Cybersecurity and Trust
alignes With: FIWARE Security
alignes With: IDS RAM Security Perspective
alignes With: IIRA Security
alignes With: IIC Security Framework
alignes With: IoT-A Trust Security and Privacy
alignes With: OCF Security
frames: Availability
frames: Identification
frames: Integrity Protection and Verification
frames: Privacy
frames: Service Access Control
frames: Trustworthiness

OFRASecurityPerspectiveAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OpenFog Security Perspective
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 51
    oahas start selector: Page 47
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 51
    oahas start selector: Page 47
  oahas source: OpenFog Reference Architecture for Fog Computing

OpenFog Security Pillar
creator: sebastian
type: NamedIndividual
type: Standard Classification
comment: Security implementations have many different descriptions and attributes such as privacy, anonymity, integrity, trust, attestation, verification, and measurement. These are key attributes for the OpenFog RA. Achieving the foundational elements for security requires an approach to discover, attest, and verify all smart and connected “things” before trust can be established source: OpenFog Reference Architecture
comment: Security in the OpenFog RA is not a one-size-fits-all architecture. Rather, it describes all of the mechanisms that can be applied to make a fog node secure from silicon to software application. Business case, target market, and vertical use case, as well as the location of the node itself, will all create a set of requirements for that node. However, there are certain foundational parts of the architecture, which must be in place in order to build a secure execution environment. source: OpenFog Reference Architecture
note: Publications referred: ' <https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.1 Security Pillar' 'Page 23'
is Described in: OpenFog Reference Architecture
alignes With: Security
alignes With: BDVA Cybersecurity and Trust
alignes With: FIWARE Security
alignes With: IDS RAM Security Perspective
alignes With: IIRA Security
alignes With: IIC Security Framework
alignes With: IoT-A Trust Security and Privacy
alignes With: OCF Security
alignes With: OpenFogSecurityPerspective
frames: Security

OFRASecurityPillarAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OpenFog Security Pillar
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 24
    oahas start selector: Page 23
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 24
    oahas start selector: Page 23
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 24
    oahas start selector: Page 23
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 24
    oahas start selector: Page 23
  oahas source: OpenFog Reference Architecture for Fog Computing

OFRASoftwareView
creator: sebastian
type: NamedIndividual
type: Viewpoint
comment: OpenFog Software Architecture View
comment: The software view of the OpenFog RA is composed of software running on a platform that is comprised of one or more node views coupled with other components to create a system addressing a given scenario. The stakeholders of the software view include the system integrators, software architects, solution designers, and application developers of a fog computing environment. The software running on fog platforms is used to satisfy a given deployment scenario. A robust fog deployment requires that the relationship between a fog node, fog platform, and fog software are seamless. source: OpenFog Reference Architecture
alignes With: IIRA Application Domain
frames: Service Discovery

OFRASoftwareViewAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OFRASoftwareView
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 89
    oahas start selector: Page 77
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 89
    oahas start selector: Page 77
  oahas source: OpenFog Reference Architecture for Fog Computing

OpenFog System Architecture View
creator: sebastian
type: NamedIndividual
type: Viewpoint
comment: The system view of the OpenFog RA is composed of one or more node views coupled with other components to create a platform. The stakeholders which typically create these systems to facilitate a fog deployment comprise the concerns of this viewpoint. Subsequently this view is intended to address the concerns of the system architects, hardware OEMs, and platform manufacturers. They also need to understand the Node view such that the systems they create can be deployed to address a given scenario. source: OpenFog Reference Architecture
is Described in: OpenFog Reference Architecture
frames: Physical Connectivity

OFRASystemViewAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OpenFog System Architecture View
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 78
    oahas start selector: Page 73
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 78
    oahas start selector: Page 73
  oahas source: OpenFog Reference Architecture for Fog Computing

OpenFog RAS Pillar
creator: sebastian
type: NamedIndividual
type: Standard Classification
comment: Reliability, availability, and serviceability (RAS) is resident throughout successful system architectures and, as such, takes on great importance in the OpenFog RA. Hardware, software, and operations are the three main areas of the RAS pillar. source: OpenFog Reference Architecture
note: Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.6 Reliability, Availability, and Serviceability (RAS)Pillar' 'Page 29'
is Described in: OpenFog Reference Architecture
frames: Availability
frames: Maintenance Cost
frames: Reliability

OFRA RASPillarAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OpenFog RAS Pillar
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 31
    oahas start selector: Page 29
  oahas source: OpenFog Reference Architecture for Fog Computing
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 31
    oahas start selector: Page 29
  oahas source: OpenFog Reference Architecture for Fog Computing

Open Mobile Alliance
creator: sebastian
type: NamedIndividual
type: Organization
type: IIoTConsortium
comment: OMA (Open Mobile Alliance) is the Leading Industry Forum for Developing Market Driven, Interoperable Mobile Service Enablers (source: https://www.postscapes.com/internet-of-things-protocols/)
has official resource: m2m-enablers

Lightweight M2M v1.0
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: The motivation of LightweightM2M is to develop a fast deployable client-server specification to provide machine to machine service. LightweightM2M is principly a device management protocol, but it should be designed to be able to extend to meet the requirements of applications. LightweightM2M is not restricted to device management, it should be able transfer service / application data. (source: https://www.postscapes.com/internet-of-things-protocols/)
has official resource: lightweightM2M v1 0.aspx

OMG DDS
creator: OMG
type: NamedIndividual
type: Document
type: Publication
type: Standard
comment: The Data Distribution Service for real-time systems (DDS) is an Object Management Group (OMG) machine-to-machine (sometimes called middleware) standard that aims to enable scalable, real-time, dependable, high-performance and interoperable data exchanges using a publish–subscribe pattern. DDS addresses the needs of applications like financial trading, air-traffic control, smart grid management, and other big data applications. The standard is used in applications such as smartphone operating systems, transportation systems and vehicles, software-defined radio, and by healthcare providers. DDS was promoted for use in the Internet of things.
maker: OMG
has Classification: IICF Framework Layer
has Classification: IIRA Connectivity
has d bpedia resource: Data Distribution Service
has official resource: dds
has Publisher: OMG
has tag: Data Distribution Service for real-time systems
has wikipedia article: Data Distribution Service
related To: IEC 29182-1
related To: IEC_61158
related To: IEC_61784

Objects Safety and Security
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: The IoT comprises of a huge number of perception objects that spread over a few geographic zone; it is important to keep the intruder's access to the items that may make physical harm them or may change their operation
supports: Safety
supports: Security

Ocean Protocol Business Viewpoint
associated with: IIRA Business Viewpoint
type: NamedIndividual
type: Standard Classification
type: Viewpoint
is Described in: Ocean Protocol
alignes With: IIRA Business Viewpoint
frames: Business Context
frames: Business Transactions
frames: Role Categorization
frames: Trustworthiness

OceanBusinessViewpointAnno
type: NamedIndividual
type: oaAnnotation
oahas body: Ocean Protocol Business Viewpoint
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 41
    oahas start selector: Page 1
  oahas source: Ocean Protocol: A Decentralized Data Exchange Protocol,powered by blockchain technology and a cryptotoken. Business Strategy. Oct 2017
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 41
    oahas start selector: Page 1
  oahas source: Ocean Protocol: A Decentralized Data Exchange Protocol,powered by blockchain technology and a cryptotoken. Business Strategy. Oct 2017

Ocean Protocol Marketplace Viewpoint
associated with: IIRA Business Viewpoint
type: NamedIndividual
type: Standard Classification
type: Viewpoint
is Described in: Ocean Protocol
alignes With: IIRA Business Viewpoint
frames: Business Context

OceanMarketplaceViewpointAnno
type: NamedIndividual
type: oaAnnotation
oahas body: Ocean Protocol Marketplace Viewpoint
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 27
    oahas start selector: Page 1
  oahas source: Ocean Protocol: A Decentralized Data Exchange Protocol to Unlock Data for Artificial Intelligence. Reference Marketplace Framework. Feb 2019
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 27
    oahas start selector: Page 1
  oahas source: Ocean Protocol: A Decentralized Data Exchange Protocol to Unlock Data for Artificial Intelligence. Reference Marketplace Framework. Feb 2019

Ocean Protocol
creator: Ocean Protocol Foundation
type: NamedIndividual
type: Document
type: Publication
type: Standarization Framework
type: Technical Specification
comment: Ocean is a decentralized protocol and network of artificial intelligence (AI) data/services. It incentivizes for a vast supply of relevant AI data/services. This network helps to power AI data/service marketplaces, as well as public commons data. The heart of Ocean’s network is a new construction: a Curated Proofs Market. CPMs bridge predicted relevance with actual relevance of each AI service, by having curation markets for cryptographic proofs (e.g. proof of data availability). (source: https://oceanprotocol.com/tech-whitepaper.pdf)
maker: Ocean Protocol Foundation
has Developer: Ocean Protocol Foundation
has official resource: oceanprotocol.com
has Publisher: Ocean Protocol Foundation

Ocean Protocol Foundation
creator: sebastian
type: NamedIndividual
type: Organization
type: StandardOrganization
comment: Ocean Protocol is supported by a Singapore based non-profit foundation, whose mandate is to ensure open access to the protocol and platform, provide data governance, encourage the network ecosystem growth and take measures to ensure that the platform becomes ever more decentralized with time.
has official resource: oceanprotocol.com

Ocean Protocol System Viewpoint
associated with: DataConsumer
associated with: DataProvider
associated with: IDS RAM Business Layer
associated with: IDS RAM Process Layer
associated with: IIRA Business Domain
associated with: IIRA Functional Viewpoint
associated with: RAMI Functional Layer
type: NamedIndividual
type: Standard Classification
type: Viewpoint
is Described in: Ocean Protocol
alignes With: IDS RAM Business Layer
alignes With: IDS RAM Process Layer
alignes With: IIRA Business Domain
alignes With: IIRA Functional Viewpoint
alignes With: RAMI Functional Layer
frames: Artificial Intelligence
frames: Authorization
frames: Availability
frames: Business Context
frames: Business Transactions
frames: Data Access
frames: Data Access Control
frames: Data Analytics
frames: Data Discovery
frames: Data Sovereignty
frames: Governance
frames: Identification
frames: Identity Management
frames: Integrity Protection and Verification
frames: Interoperability
frames: Privacy
frames: Provenance Tracking
frames: Security
frames: Service level agreement
frames: Service life-cycle management
frames: Syntactic Interoperability
frames: Trustworthiness

OceanSystemViewpointAnno
type: NamedIndividual
type: oaAnnotation
oahas body: Ocean Protocol System Viewpoint
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 59
    oahas start selector: Page 1
  oahas source: Ocean Protocol: A Decentralized Substrate for AI Data & Services . Technical Whitepaper. Apr 2019
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 59
    oahas start selector: Page 1
  oahas source: Ocean Protocol: A Decentralized Substrate for AI Data & Services . Technical Whitepaper. Apr 2019

Ocean Protocol: A Decentralized Data Exchange Protocol,powered by blockchain technology and a cryptotoken. Business Strategy. Oct 2017
type: NamedIndividual
type: oaSpecificResource
has open resource: business-strategy.pdf

Ocean Protocol: A Decentralized Data Exchange Protocol to Unlock Data for Artificial Intelligence. Reference Marketplace Framework. Feb 2019
type: NamedIndividual
type: oaSpecificResource
has open resource: marketplace-framework.pdf

Ocean Protocol: A Decentralized Substrate for AI Data & Services . Technical Whitepaper. Apr 2019
type: NamedIndividual
type: oaSpecificResource
has open resource: tech-whitepaper.pdf

OCF Framework Block
creator: sebastian
type: Class
subclass of: Standard Classification

OCF Core Framework
creator: sebastian
type: NamedIndividual
type: OCF Framework Block
is Described in: OCF Framework
frames: Communication
frames: Endpoint Invocation
frames: Identification
frames: Service Discovery
frames: Syntactic Interoperability

OcfCoreFrameworkAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OCF Core Framework
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 14
    oahas start selector: Page 11
  oahas source: OCF Core Specification VERSION 2 0 1

OCF Data Models
type: NamedIndividual
type: OCF Framework Block
is Described in: OCF Framework
frames: Semantic Interoperability

OcfDataModelsAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OCF Data Models
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 14
    oahas start selector: Page 11
  oahas source: OCF Core Specification VERSION 2 0 1

OCF Framework
creator: sebastian
type: NamedIndividual
type: Standarization Framework
has Publisher: Open Connectivity Foundation

OcfFrameworkAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OCF Framework
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 14
    oahas start selector: Page 11
  oahas source: OCF Core Specification VERSION 2 0 1

OCF L2 Connectivity
type: NamedIndividual
type: OCF Framework Block
is Described in: OCF Framework
frames: Connectivity
frames: Syntactic Interoperability

OcfL2ConnectivityAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OCF L2 Connectivity
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 14
    oahas start selector: Page 11
  oahas source: OCF Core Specification VERSION 2 0 1

OCF Networking
creator: sebastian
associated with: IPv6
type: NamedIndividual
type: OCF Framework Block
is Described in: OCF Framework
frames: Connectivity
frames: IPv6 Support

OcfNetworkingAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OCF Networking
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 14
    oahas start selector: Page 11
  oahas source: OCF Core Specification VERSION 2 0 1

OCF Security
creator: sebastian
associated with: RAML
type: NamedIndividual
type: OCF Framework Block
has Publisher: Open Connectivity Foundation
is Described in: OCF Framework
alignes With: Security
alignes With: BDVA Cybersecurity and Trust
alignes With: FIWARE Security
alignes With: IDS RAM Security Perspective
alignes With: IIRA Security
alignes With: IIC Security Framework
alignes With: IoT-A Trust Security and Privacy
alignes With: OpenFogSecurityPerspective
frames: Certification
frames: Connectivity
frames: Secure Communication

OcfSecurityAnno
type: NamedIndividual
type: oaAnnotation
oahas body: OCF Security
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 14
    oahas start selector: Page 11
  oahas source: OCF Core Specification VERSION 2 0 1

OpenAPI
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: The OpenAPI Specification (originally known as the Swagger Specification) is a specification for machine-readable interface files for describing, producing, consuming, and visualizing RESTful web services. A variety of tools can generate code, documentation and test cases given an interface file. Development of the OpenAPI Specification (OAS) is overseen by the Open API Initiative, an open source collaborative project of the Linux Foundation. (source: wikipedia)
has d bpedia resource: OpenAPI Specification

Open Connectivity Foundation
type: NamedIndividual
type: StandardOrganization
comment: The Open Connectivity Foundation (OCF) is an industry group whose stated mission is to develop specification standards, promote a set of interoperability guidelines, and provide a certification program for devices involved in the Internet of Things (IoT). It has become one of the biggest industrial connectivity standards organizations for IoT, including in its membership Samsung Electronics, Intel, Microsoft, Qualcomm and Electrolux. Currently, there are more than 300 member companies. source: wikipedia
has d bpedia resource: Open Connectivity Foundation

OpenFog Architecture Whitepaper
title: OpenFog Architecture Overview
creator: sebastian
type: NamedIndividual
type: Publication
comment: The OpenFog Architecture is a system-level architecture that extends elements of compute, networking and storage across the cloud through to the edge of the network. This approach is particularly suited to IoT systems and accelerates the decision-making velocity. This architecture serves a specific subset of business problems that can’t be successfully implemented using “cloud only” based architectures or relying solely on intelligent edge devices. OpenFog should be thought of as complementary to, and an extension of the traditional cloud based model where implementations of the architecture can reside in multiple layers of a network’s topology. The goal of the OpenFog architecture is to facilitate deployments which highlight interoperability, performance, security, scalability, programmability, reliability, availability, serviceability, and agility. Proprietary or single vendor solutions can result in limited supplier diversity, which can have a negative impact on market adoption, system cost, quality and innovation.
has d bpedia resource: OpenFog Consortium
has official resource: white-paper-download-open-fog-reference-architecture
has Publisher: OpenFog Consortium

OpenFog Consortium
type: NamedIndividual
type: IIoTConsortium
comment: The OpenFog Consortium work is done by committees and workgroups focused on specific tasks aligned to our mission. This work includes technical work; influencing standards development through liaisons with other organizations; testbed; promoting innovation and industry interest in fog computing; and industry education.
has official resource: www.openfogconsortium.org
see also: www.openfogconsortium.org

OpenFog Reference Architecture
creator: sebastian
type: NamedIndividual
type: Architecture Description
type: Standarization Framework
comment: The OpenFog Reference Architecture (OpenFog RA) is intended to help business leaders, software developers, silicon architects, and system designers create and maintain the hardware, software and system elements necessary for fog computing.
has official resource: ra
has Publisher: OpenFog Consortium

OpenFog Reference Architecture for Fog Computing
type: NamedIndividual
type: oaSpecificResource
has open resource: OpenFog Reference Architecture 2 09 17-FINAL.pdf

ORION Context Broker
creator: sebastian
associated with: FIWARE Architecture
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification

Performance
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: Performance is completion of a task with application of knowledge, skills and abilities
has wikipedia article: Performance
supports: Business Context

Periodic Communication
has stakeholder: Q1548249
type: NamedIndividual
type: Concern
see also: IoT-A Requirement UNI.005
supports: Event-Driven Messaging

Physical Connectivity
creator: sebastian
type: NamedIndividual
type: Concern
comment: Physical Connectivity is the concern including all aspects of low-level connectivity and transporting a physical (electrical) signal from A to B. This might be achieved through wired connections (e.g. ethernet) but also wireless (e.g. WIFI).
supports: Interoperability

Physical Web
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: Physical Web - The Physical Web enables you to see a list of URLs being broadcast by objects in the environment around you with a Bluetooth Low Energy (BLE) beacon. (source: https://www.postscapes.com/internet-of-things-protocols/)
has official resource: faq

Plant Manager
comment: A plant manager is responsible for the functioning of a plant/facility.
alternative label: Facility Manager
note: Publications referred: 'IIC:PUB:G1:V1.80:20170131' '1.5 AUDIENCE' 'Page 7'
has wikipedia article: Role of the facilities manager

Platform Industry 4.0
creator: sebastian
associated with: RAMI
type: NamedIndividual
type: Organization
type: IIoTConsortium
label: Plattform Industrie 4.0 @de

Privacy
creator: sebastian
type: NamedIndividual
type: Concern
comment: Information privacy, or data privacy (or data protection), is the relationship between collection and dissemination of data, technology, the public expectation of privacy, and the legal and political issues surrounding them. Privacy concerns exist wherever personally identifiable information or other sensitive information is collected, stored, used, and finally destroyed or deleted – in digital form or otherwise. Improper or non-existent disclosure control can be the root cause for privacy issues. Data privacy issues can arise in response to information from a wide range of sources, such as: * Healthcare records * Criminal justice investigations and proceedings * Financial institutions and transactions * Biological traits, such as genetic material * Residence and geographic records * Ethnicity * Privacy breach * Location-based service and geolocation * Web surfing behavior or user preferences using persistent cookies. (source: wikipedia)
see also: IoT-A Requirement UNI.423
see also: IoT-A Requirement UNI.424
see also: IoT-A Requirement UNI.606
see also: IoT-A Requirement UNI.623
has d bpedia resource: Information privacy
supports: Data Sovereignty
supports: Trustworthiness

Isolation
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: "Isolation would be another issue at the edge of the network. In mobile OS, if an application fails or crashes, the whole system will usually crash and reboot. Or in a distributed system the shared resource could be managed with different synchronization mechanisms such as a lock or token ring. "
has wikipedia article: Process isolation
supports: Integrity Protection and Verification

Product Development Life Cycle
type: Class
comment: PLM is the process of managing the entire lifecycle of a product from inception, through engineering design and manufacture, to service and disposal of manufactured products. Related areas are PLMManagement, Modeling Practice, Product Model Data exchange, Manufacturing Model Data, Product Catalog Data.
comment: Product Development Life-Cycle Phase
subclass of: Standard Classification

Product Liability
type: NamedIndividual
type: Concern
note: Publications referred: '(IIC:PUB:G1:V1.80:20170131' '4 BUSINESS VIEWPOINT' 'Page 20'
supports: Business Context

Product Manager
type: Stakeholder Group
type: NamedIndividual
type: Layer
note: Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.1 BUSINESS VIEWPOINT' 'Page 15' 'Priyanka'

Production System Life Cycle
type: Class
comment: Collections of machines, equipment, and auxiliary systems organized to create goods and services from various resources.
subclass of: Standard Classification

Programmability
is Component Of: Edge computing
type: NamedIndividual
type: Concern
comment: In the edge computing, computation is offloaded from the cloud, and the edge nodes are most likely heterogeneous platforms. In this case, the runtime of these nodes differ from each other, and the programmer faces huge difficulties to write an application that may be deployed in the edge computing paradigm.
note: Publications referred: ' <https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.5 Programmability Pillar' 'Page 29'
supports: Edge computing

Provenance Tracking
creator: sebastian
has stakeholder: EndUser
type: NamedIndividual
type: Concern
comment: Data provenance includes the data's origins, what happens to it and where it moves/moved over time.
see also: IoT-A Requirement UNI.041
see also: IoT-A Requirement UNI.606
has d bpedia resource: Data lineage
supports: Security

Pseudonimity
creator: sebastian
type: NamedIndividual
type: Concern
comment: While complete anonymity is not feasibe in an IoT scenario, pseudonimity should be supported.
see also: IoT-A Requirement UNI.624
has d bpedia resource: Pseudonymity
supports: Anonymity

Publication
comment: Specifies a Publication. E.g., International Standards,Technical Specifications,Publicly Available Specifications,Amendments Technical Corrigenda,Interpretation Sheets,Technical Reports,Guides
subclass of: Document

Quality of Service
type: NamedIndividual
type: Concern
comment: Quality of service (QoS) is the overall performance of a telephony or computer network, particularly the performance seen by the users of the network. To quantitatively measure quality of service, several related aspects of the network service are often considered, such as error rates, bit rate, throughput, transmission delay, availability, jitter, etc. In the field of computer networking and other packet-switched telecommunication networks, quality of service refers to traffic prioritization and resource reservation control mechanisms rather than the achieved service quality. (source: wikipedia)
see also: IoT-A Requirement UNI.613
see also: IoT-A Requirement UNI.614
see also: IoT-A Requirement UNI.717
has d bpedia resource: Quality of service
supports: Service Description

RAMI Asset Layer
associated with: Lifecycle Status
associated with: Edgecross FA
associated with: IIRA Physical Systems
associated with: IoT-A Functional Viewpoint
associated with: IVI Asset View
type: NamedIndividual
type: RAMI IT Layer
type: Standard Classification
is Described in: RAMI
alignes With: Edgecross FA
alignes With: IIRA Physical Systems
alignes With: IoT-A Functional Viewpoint
alignes With: IVI Asset View
frames: Communication
frames: Identification
frames: Identity Management
frames: Interoperability
frames: Security
frames: Semantic Interoperability
frames: Thing description
frames: Thing representation
frames: Trustworthiness
frames: Virtual Entity

RAMIAssetlayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: RAMI Asset Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 23
    oahas start selector: Page 22
  oahas source: DIN SPEC 91345
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 23
    oahas start selector: Page 22
  oahas source: DIN SPEC 91345

RAMIBodyAnno
type: NamedIndividual
type: oaAnnotation
oahas body: RAMIBody
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 31
    oahas start selector: Page 30
  oahas source: DIN SPEC 91345
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 31
    oahas start selector: Page 30
  oahas source: DIN SPEC 91345

RAMI Business Layer
associated with: IDS RAM Business Layer
associated with: IDS RAM Governance Perspective
associated with: IIRA Business Domain
associated with: IVI Business Layer
type: NamedIndividual
type: RAMI IT Layer
type: Standard Classification
is Described in: RAMI
alignes With: IDS RAM Business Layer
alignes With: IDS RAM Governance Perspective
alignes With: IIRA Business Domain
alignes With: IVI Business Layer
frames: ProcessPlanning
frames: Business Context
frames: Service Composition
frames: Service Orchestration

RAMIBusinessLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: RAMI Business Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 21
    oahas start selector: Page 20
  oahas source: DIN SPEC 91345
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 21
    oahas start selector: Page 20
  oahas source: DIN SPEC 91345

RAMI Communication Layer
associated with: FIWARE IoT Services Enablement
associated with: IDS RAM System Layer
associated with: IIRA Connectivity
associated with: IIRA Distributed Data Management
associated with: IoT-A Information Viewpoint
type: NamedIndividual
type: RAMI IT Layer
type: Standard Classification
is Described in: RAMI
alignes With: FIWARE IoT Services Enablement
alignes With: IDS RAM System Layer
alignes With: IIRA Connectivity
alignes With: IIRA Distributed Data Management
alignes With: IoT-A Information Viewpoint
frames: Data Access
frames: Endpoint Invocation
frames: Interoperability
frames: Provenance Tracking
frames: Security
frames: Syntactic Interoperability
frames: Trustworthiness

RAMICommunicationlayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: RAMI Communication Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 22
    oahas start selector: Page 21
  oahas source: DIN SPEC 91345
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 22
    oahas start selector: Page 21
  oahas source: DIN SPEC 91345

RAMIConnectedWorldAnno
type: NamedIndividual
type: oaAnnotation
oahas body: RAMIConnectedWorld
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 24
    oahas start selector: Page 23
  oahas source: DIN SPEC 91345
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 24
    oahas start selector: Page 23
  oahas source: DIN SPEC 91345

RAMIControlDeviceAnno
type: NamedIndividual
type: oaAnnotation
oahas body: RAMIControlDevice
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 24
    oahas start selector: Page 23
  oahas source: DIN SPEC 91345
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 24
    oahas start selector: Page 23
  oahas source: DIN SPEC 91345

RAMIEnterpriseAnno
type: NamedIndividual
type: oaAnnotation
oahas body: RAMIEnterprise
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 24
    oahas start selector: Page 23
  oahas source: DIN SPEC 91345
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 24
    oahas start selector: Page 23
  oahas source: DIN SPEC 91345

RAMIFieldDeviceAnno
type: NamedIndividual
type: oaAnnotation
oahas body: RAMIFieldDevice
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 24
    oahas start selector: Page 23
  oahas source: DIN SPEC 91345
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 24
    oahas start selector: Page 23
  oahas source: DIN SPEC 91345

RAMI Functional Layer
associated with: BDVA Data Analytics
associated with: BdvaDataViualisationAndUserInteraction
associated with: DTP System
associated with: IDS RAM Process Layer
associated with: IIRA Application Domain
associated with: IIRA Operation Domain
associated with: IoT-A Functional Viewpoint
associated with: IVI Management View
associated with: NGSI-LD Data Representation
associated with: Ocean Protocol System Viewpoint
associated with: x-road System Components
type: NamedIndividual
type: RAMI IT Layer
type: Standard Classification
is Described in: RAMI
alignes With: BDVA Data Analytics
alignes With: BdvaDataViualisationAndUserInteraction
alignes With: DTP System
alignes With: IDS RAM Process Layer
alignes With: IIRA Application Domain
alignes With: IIRA Operation Domain
alignes With: IoT-A Functional Viewpoint
alignes With: IVI Management View
alignes With: NGSI-LD Data Representation
alignes With: Ocean Protocol System Viewpoint
alignes With: x-road System Components
frames: Endpoint Description
frames: Interoperability
frames: Role Categorization
frames: Semantic Interoperability
frames: Service Description

RAMIFunctionalLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: RAMI Functional Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 21
    oahas start selector: Page 20
  oahas source: DIN SPEC 91345
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 21
    oahas start selector: Page 20
  oahas source: DIN SPEC 91345

Administration Shell Header
is part of: Administration Shell
type: NamedIndividual
type: Standard Classification
type: Standarization Framework
note: find better class assignment
has Publisher: Platform Industry 4.0
frames: Lifecycle Status
frames: Business Context
frames: Data Access
frames: Endpoint Invocation
frames: Identification
frames: Identity Management
frames: Interoperability
frames: Security
frames: Semantic Interoperability
frames: Syntactic Interoperability
frames: Thing description
frames: Thing representation
frames: Trustworthiness

RAMIHeaderAnno
type: NamedIndividual
type: oaAnnotation
oahas body: Administration Shell Header
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 31
    oahas start selector: Page 30
  oahas source: DIN SPEC 91345
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 31
    oahas start selector: Page 30
  oahas source: DIN SPEC 91345

RAMI Information Layer
associated with: BDVA Data Analytics
associated with: BDVA Data Management
associated with: Edgecross Edgecomputing Layer
associated with: IDS RAM Information Layer
associated with: IIRA Application Domain
associated with: InformationDomain
associated with: NGSI-LD Information Model
type: NamedIndividual
type: RAMI IT Layer
type: Standard Classification
is Described in: RAMI
alignes With: BDVA Data Analytics
alignes With: BDVA Data Management
alignes With: Edgecross Edgecomputing Layer
alignes With: IDS RAM Information Layer
alignes With: IIRA Application Domain
alignes With: InformationDomain
alignes With: NGSI-LD Information Model
frames: Data Analytics
frames: Data Description
frames: Data Processing
frames: Integrity Protection and Verification
frames: Interoperability
frames: Security
frames: Semantic Interoperability
frames: Stream processing
frames: Trustworthiness

RAMIInformationLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: RAMI Information Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 22
    oahas start selector: Page 21
  oahas source: DIN SPEC 91345
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 22
    oahas start selector: Page 21
  oahas source: DIN SPEC 91345

RAMI Integration Layer
associated with: DTP System
associated with: Edgecross Edgecomputing Layer
associated with: Edgecross IT Systems Layer
associated with: FIWARE IoT Services Enablement
associated with: IDS RAM System Layer
associated with: IIRA Control Domain
associated with: IoT-A Evolution and Interoperability
associated with: NGSI-LD Architecture
associated with: x-road Deplyoment View
associated with: x-road Protocols and Interfaces
type: NamedIndividual
type: RAMI IT Layer
type: Standard Classification
is Described in: RAMI
alignes With: DTP System
alignes With: Edgecross Edgecomputing Layer
alignes With: Edgecross IT Systems Layer
alignes With: FIWARE IoT Services Enablement
alignes With: IDS RAM System Layer
alignes With: IIRA Control Domain
alignes With: IoT-A Evolution and Interoperability
alignes With: NGSI-LD Architecture
alignes With: x-road Deplyoment View
alignes With: x-road Protocols and Interfaces
frames: Interoperability
frames: Semantic Interoperability
frames: Thing description
frames: Thing representation
frames: User Interaction

RAMIIntegrationLayerAnno
type: NamedIndividual
type: oaAnnotation
oahas body: RAMI Integration Layer
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 23
    oahas start selector: Page 22
  oahas source: DIN SPEC 91345
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 23
    oahas start selector: Page 22
  oahas source: DIN SPEC 91345

RAMIProductAnno
type: NamedIndividual
type: oaAnnotation
oahas body: RAMIProduct
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 24
    oahas start selector: Page 23
  oahas source: DIN SPEC 91345
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 24
    oahas start selector: Page 23
  oahas source: DIN SPEC 91345

RAMIStationAnno
type: NamedIndividual
type: oaAnnotation
oahas body: RAMIStation
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 24
    oahas start selector: Page 23
  oahas source: DIN SPEC 91345
oahas target: oaSpecificResource
  format: pdf
  oahas selector: oaRangeSelector
    oahas end selector: Page 24
    oahas start selector: Page 23
  oahas source: DIN SPEC 91345

RAML
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: RAML (RESTful API Modeling Language) - Makes it easy to manage the whole API lifecycle from design to sharing. It's concise - you only write what you need to define - and reusable. (source: https://www.postscapes.com/internet-of-things-protocols/)
has official resource: raml.org

REST
creator: sebastian
associated with: DTP Deployment
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: REST (Representational state transfer) - RESTful HTTP (source: https://www.postscapes.com/internet-of-things-protocols/)
has wikipedia article: Representational state transfer

Requirements for Internet Hosts -- Communication Layers
creator: IETF
type: NamedIndividual
type: Document
type: Publication
type: Standard
comment: This is one RFC of a pair that defines and discusses the requirements for Internet host software. This RFC covers the communications protocol layers: link layer, IP layer, and transport layer; its companion RFC-1123 covers the application and support protocols.
label: RFC 1122
maker: IETF
has Classification: IIRA Connectivity
has Classification: NetworkLayer
has official resource: rfc1122
has Publisher: IETF

HTTP/1.1
creator: IETF
type: NamedIndividual
type: Document
type: Publication
type: Standard
comment: The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name servers and distributed object management systems, through extension of its request methods, error codes and headers. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred.
label: RFC 2616
maker: IETF
has Classification: IDS RAM System Layer
has Classification: IIRA Functional Viewpoint
has Classification: RAMI Communication Layer
has Classification: TansportLayer
has official resource: rfc2817
has official resource: rfc2616
has Publisher: IETF

HTTPS
creator: IETF
type: NamedIndividual
type: Document
type: Publication
type: Standard
comment: This memo describes how to use TLS to secure HTTP connections over the Internet. Current practice is to layer HTTP over SSL (the predecessor to TLS), distinguishing secured traffic from insecure traffic by the use of a different server port. This document documents that practice using TLS. A companion document describes a method for using HTTP/TLS over the same port as normal HTTP [RFC2817].
label: RFC 2818
maker: IETF
has Classification: IDS RAM Security Perspective
has Classification: IDS RAM System Layer
has Publisher: IETF

Lightweight Directory Access Protocol
creator: IETF
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
label: LDAP
maker: IETF
has Developer: IETF
has official resource: rfc4511
has Publisher: IETF
has wikipedia article: Lightweight Directory Access Protocol
has Target Concern: Cross-domain Identity Management

RFC 5246
creator: IETF
description: This document specifies Version 1.2 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications security over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery.
type: NamedIndividual
type: Document
type: Publication
type: Standard
maker: IETF
has Classification: Data Sovereignty
has Classification: IDS RAM Security Perspective
has official resource: rfc5246
has Publisher: IETF

RFC 6750
creator: IETF
description: This specification describes how to use bearer tokens in HTTP requests to access OAuth 2.0 protected resources. Any party in possession of a bearer token (a "bearer") can use it to get access to the associated resources (without demonstrating possession of a cryptographic key). To prevent misuse, bearer tokens need to be protected from disclosure in storage and in transport.
associated with: Data Transfer Project Architecture
type: NamedIndividual
type: Document
type: Publication
type: Standard
alternative label: OAuth2.0
maker: IETF
has Classification: IDS RAM Security Perspective
has d bpedia resource: OAuth
has official resource: rfc6750
has Publisher: IETF

The Constrained Application Protocol
creator: IETF
type: NamedIndividual
type: Document
type: Publication
type: Standard
comment: The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) often have high packet error rates and a typical throughput of 10s of kbit/s. The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.
label: RFC 7252
alternative label: CoAP
maker: IETF
has Classification: IIRA Operation Domain
has Classification: TansportLayer
has official resource: rfc7252
has Publication Date: 2014-06-01
has Publisher: IETF

JSON Web Token
creator: IETF
description: JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.
type: NamedIndividual
type: Document
type: Publication
type: Standard
label: RFC 7519
maker: IETF
has Classification: Data Sovereignty
has Classification: IDS RAM Security Perspective
has official resource: rfc7519
has Publisher: IETF

HTTP/2
creator: IETF
type: NamedIndividual
type: Document
type: Publication
type: Standard
comment: This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol (HTTP), referred to as HTTP version 2 (HTTP/2). HTTP/2 enables a more efficient use of network resources and a reduced perception of latency by introducing header field compression and allowing multiple concurrent exchanges on the same connection. It also introduces unsolicited push of representations from servers to clients. This specification is an alternative to, but does not obsolete, the HTTP/1.1 message syntax. HTTP's existing semantics remain unchanged.
label: RFC 7540
maker: IETF
has Classification: IDS Interoperability
has Classification: IDS RAM System Layer
has Classification: IIRA Functional Viewpoint
has Classification: RAMI Communication Layer
has Classification: TansportLayer
has Publisher: IETF

SCIM Use Cases
creator: IETF
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Standard
comment: This document provides definitions and an overview of the System for Cross-domain Identity Management (SCIM). It lays out the system's concepts, models and flows, and includes user scenarios, use cases, and requirements.
label: RFC 7642
maker: IETF
has Classification: FIWARE Security
has Developer: IETF
has official resource: draft-ietf-scim-use-cases-08
has Publisher: IETF
has Target Concern: Identity Management

SCIM Core Schema
creator: IETF
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Standard
comment: This document provides a platform neutral schema and extension model for representing users and groups and other resource types in JSON format. This schema is intended for exchange and use with cloud service providers.
label: RFC 7643
maker: IETF
has Classification: FIWARE Security
has Developer: IETF
has official resource: draft-ietf-scim-core-schema-22
has Publisher: IETF
has Target Concern: Identity Management

SCIM API
creator: irlan
creator: sebastian
type: NamedIndividual
type: Standard
comment: The System for Cross-Domain Identity Management (SCIM) specification is an HTTP based protocol that makes managing identities in multi domain scenarios easier to support through a standardized service. Examples include but are not limited to enterprise to cloud service providers, and inter-cloud based scenarios. The specification suite seeks to build upon experience with existing schemas and deployments, placing specific emphasis on simplicity of development and integration, while applying existing authentication, authorization, and privacy models. SCIM's intent is to reduce the cost and complexity of user management operations by providing a common user schema, an extension model, and a service protocol defined by this document.
label: RFC 7644
maker: IETF
has Classification: FIWARE Security
has Developer: IETF
has official resource: draft-ietf-scim-api-19
has Publisher: IETF
has Target Concern: Identity Management

User Datagram Protocol (UDP)
creator: IETF
type: NamedIndividual
type: Standard
comment: In computer networking, the User Datagram Protocol (UDP) is one of the core members of the Internet protocol suite. The protocol was designed by David P. Reed in 1980 and formally defined in RFC 768. With UDP, computer applications can send messages, in this case referred to as datagrams, to other hosts on an Internet Protocol (IP) network. Prior communications are not required in order to set up communication channels or data paths.
label: RFC 768
maker: IETF
has Classification: TansportLayer
has d bpedia resource: User Datagram Protocol
has official resource: rfc768
has Publisher: IETF
has wikipedia article: User Datagram Protocol

TRANSMISSION CONTROL PROTOCOL
creator: irlan
creator: sebastian
type: NamedIndividual
type: Standard
comment: This document describes the DoD Standard Transmission Control Protocol (TCP). There have been nine earlier editions of the ARPA TCP specification on which this standard is based, and the present text draws heavily from them. There have been many contributors to this work both in terms of concepts and in terms of text. This edition clarifies several details and removes the end-of-letter buffer-size adjustments, and redescribes the letter mechanism as a push function.
label: RFC 793
maker: IETF
has Classification: IDS RAM System Layer
has Classification: TansportLayer
has official resource: rfc793
has Publisher: IETF

CoAP
creator: IETF
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: CoAP (Constrained Application Protocol) is an application layer protocol that is intended for use in resource-constrained internet devices, such as WSN nodes. CoAP is designed to easily translate to HTTP for simplified integration with the web, while also meeting specialized requirements such as multicast support, very low overhead, and simplicity. The CoRE group has proposed the following features for CoAP: RESTful protocol design minimizing the complexity of mapping with HTTP, Low header overhead and parsing complexity, URI and content-type support, Support for the discovery of resources provided by known CoAP services. Simple subscription for a resource, and resulting push notifications, Simple caching based on max-age. (source: https://www.postscapes.com/internet-of-things-protocols/)
maker: IETF
has Classification: IIRA Connectivity
has Classification: RAMI Communication Layer
has d bpedia resource: Constrained Application Protocol
has Developer: IETF
has official resource: rfc8323
has Publisher: IETF
has wikipedia article: Constrained Application Protocol

ROLL
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: ROLL / RPL (IPv6 routing for low power/lossy networks) (source: https://www.postscapes.com/internet-of-things-protocols/)
has official resource: roll

RPMA
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: RPMA (Random phase multiple access) A technology communication system employing direct-sequence spread spectrum (DSSS) with multiple access. (source: https://www.postscapes.com/internet-of-things-protocols/)
has wikipedia article: Random phase multiple access

Radio activity control
has stakeholder: developer
type: NamedIndividual
type: Concern
comment: The user shall be able to control the radio activity of the system.
see also: IoT-A Requirement UNI.021
supports: Energy Control

Reactive Streams
creator: sebastian
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: A standard for asynchronous stream processing with non-blocking back pressure on the JVM. (source: https://www.postscapes.com/internet-of-things-protocols/)
has official resource: www.reactive-streams.org

Real Time Analytics
has stakeholder: EndUser
type: NamedIndividual
type: Concern
comment: In computer science, real-time computing (RTC), or reactive computing describes hardware and software systems subject to a "real-time constraint", for example from event to system response. Real-time programs must guarantee response within specified time constraints, often referred to as "deadlines". Systems of this type whose correctness depends on their temporal aspects as well as their functional aspects. Real-time responses are often understood to be in the order of milliseconds, and sometimes microseconds.
see also: IoT-A Requirement UNI.020
has d bpedia resource: Real-time computing
supports: Data Analytics

Regulatory Compliance
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: Organizations are ultimately legally responsible for their process compliance and data security, Even though the data is in a public cloud.
narrower: Compliance
has wikipedia article: Regulatory compliance

Reliability
creator: sebastian
type: NamedIndividual
type: Concern
comment: In computer networking, a reliable protocol provides reliability properties with respect to the delivery of data to the intended recipient(s), as opposed to an unreliable protocol, which does not provide notifications to the sender as to the delivery of transmitted data. (source: wikipedia)
see also: IoT-A Requirement UNI.065
note: Publications referred: '<https://www.iiconsortium.org/pdf/IIC_PUB_G4_V1.00_PB-3.pdf IIC:PUB:G4:V1.0:PB:20160926>'
note: Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.6 Reliability, Availability, and Serviceability (RAS)Pillar' 'Page 29'
has d bpedia resource: Reliability (computer networking)
supports: Trustworthiness

Resilience
creator: sebastian
has stakeholder: generalManager
has stakeholder: Q1548249
type: NamedIndividual
type: Concern
comment: Resilience is the ability to provide and maintain an acceptable level of service in the face of faults and challenges to normal operation.” Threats and challenges for services can range from simple misconfiguration over large scale natural disasters to targeted attacks. As such, network resilience touches a very wide range of topics. In order to increase the resilience of a given communication network, the probable challenges and risks have to be identified and appropriate resilience metrics have to be defined for the service to be protected. (source: wikipedia)
see also: IoT-A Requirement UNI.012
see also: IoT-A Requirement UNI.040
see also: IoT-A Requirement UNI.058
see also: IoT-A Requirement UNI.064
see also: IoT-A Requirement UNI.718
has d bpedia resource: Resilience (network)
supports: Trustworthiness

Return On Investment
type: NamedIndividual
type: Concern
note: Publications referred: '(IIC:PUB:G1:V1.80:20170131' '4 BUSINESS VIEWPOINT' 'Page 20'
supports: Business Context

Risk Management
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: Organizations will be generally exposed to a broad range of different risks, by adopting the cloud computing. Managing these risks is very important concern, as the successful implementation of cloud computing relies upon the appropriate managing, reducing, as well as mitigating these risks linked to cloud computing
has d bpedia resource: Risk management
has wikipedia article: Risk management
supports: Business Context

Role Categorization
creator: sebastian
type: NamedIndividual
type: Concern
comment: The necessity to categorize participants of a network (users or components) by roles according to the contributions they provide and the demands they have. Examples are identity provider, analytics service, data provider etc. Not to be confused with 'role-based access control', which distinguishes users according to their organizational group, e.g. adimistrators, managers, data analysts etc.
supports: Identity Management

IETF System for Cross-domain Identity Management (SCIM) 2.0
creator: irlan
creator: sebastian
associated with: FIWARE Security
associated with: SCIM Use Cases
associated with: SCIM Core Schema
associated with: SCIM API
type: NamedIndividual
type: Document
type: Publication
type: Technical Specification
comment: The System for Cross-domain Identity Management (SCIM) specification is designed to make managing user identities in cloud-based applications and services easier. The specification suite seeks to build upon experience with existing schemas and deployments, placing specific emphasis on simplicity of development and integration, while applying existing authentication, authorization, and privacy models. Its intent is to reduce the cost and complexity of user management operations by providing a common user schema and extension model, as well as binding documents to provide patterns for exchanging this schema using standard protocols. In essence: make it fast, cheap, and easy to move users in to, out of, and around the cloud.
label: SCIM
maker: IETF
has d bpedia resource: System for Cross-domain Identity Management
has Publisher: IETF
has wikipedia article: System for Cross-domain Identity Management
has Target Concern: Cross-domain Identity Management

Safety
creator: sebastian
type: NamedIndividual
type: Concern
comment: Functional safety (as defined by the IDS) is the ability of a system to prevent physical damage.
comment: Safety is the state of being "safe" (from French sauf), the condition of being protected from harm or other non-desirable outcomes. Safety can also refer to the control of recognized hazards in order to achieve an acceptable level of risk. (source: wikipedia)
has d bpedia resource: Safety
supports: Trustworthiness

Scalability
creator: sebastian
type: NamedIndividual
type: Concern
comment: Scalability is the capability of a system, network, or process to handle a growing amount of work, or its potential to be enlarged in order to accommodate that growth. For example, it can refer to the capability of a system to increase its total output under an increased load when resources (typically hardware) are added. An analogous meaning is implied when the word is used in an economic context, where scalability of a company implies that the underlying business model offers the potential for economic growth within the company. Scalability, as a property of systems, is generally difficult to define and in any particular case it is necessary to define the specific requirements for scalability on those dimensions that are deemed important. It is a highly significant issue in electronics systems, databases, routers, and networking. (source: wikipedia)
see also: IoT-A Requirement UNI.026
see also: IoT-A Requirement UNI.234
see also: IoT-A Requirement UNI.511
see also: IoT-A Requirement UNI.711
has d bpedia resource: Scalability

Secure Communication
creator: sebastian
has stakeholder: developer
has stakeholder: EndUser
has stakeholder: SystemArchitect
type: NamedIndividual
type: Concern
comment: Secure communication
comment: This concern frames everything necessary to establish and conduct a secure communication channel, which cannot be read, intercepted or altered by a third party. Especially relevant are encrypting techniques.
see also: IoT-A Requirement UNI.022
see also: IoT-A Requirement UNI.062
see also: IoT-A Requirement UNI.501
see also: IoT-A Requirement UNI.607
see also: IoT-A Requirement UNI.608
see also: IoT-A Requirement UNI.609
supports: Communication
supports: Integrity Protection and Verification

Security
creator: sebastian
has stakeholder: generalManager
has stakeholder: Q1548249
type: NamedIndividual
type: Concern
comment: Information security, sometimes shortened to InfoSec, is the practice of defending information from unauthorized access, use, disclosure, disruption, modification, inspection, recording or destruction. It is a general term that can be used regardless of the form the data may take (e.g. electronic, physical). (source: wikipedia)
see also: IoT-A Requirement UNI.040
see also: IoT-A Requirement UNI.507
see also: IoT-A Requirement UNI.626
see also: IoT-A Requirement UNI.719
has d bpedia resource: Information security
supports: Privacy

Security Configuration
type: NamedIndividual
type: Concern
comment: Users should be able to monitor and control the security and privacy settings of all the devices that they own.
see also: IoT-A Requirement UNI.625
has d bpedia resource: Hardening (computing)
supports: Security

Selection of Service Provider
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: Due to the diversity of cloud computing service suppliers, it is a challenge for organizations to pick am appropriate service supplier. In selection of a cloud provider, organizations ought to look at different elements, like the reputation and size of the company of service supplier, in terms of number of employees, share of the market, as well as their other resources
has wikipedia article: Service provider
supports: Business Context
supports: Cloud Computing Capability

Semantic Interoperability
creator: sebastian
has stakeholder: developer
type: NamedIndividual
type: Concern
comment: Beyond the ability of two or more computer systems to exchange information, semantic interoperability is the ability to automatically interpret the information exchanged meaningfully and accurately in order to produce useful results as defined by the end users of both systems. To achieve semantic interoperability, both sides must refer to a common information exchange reference model. source: <https://en.wikipedia.org/wiki/Interoperability>
see also: IoT-A Requirement UNI.003
see also: IoT-A Requirement UNI.070
see also: IoT-A Requirement UNI.073
see also: IoT-A Requirement UNI.213
see also: IoT-A Requirement UNI.426
see also: IoT-A Requirement UNI.427
note: Publications referred: '<https://doi.org/10.1016/j.jksuci.2016.10.003>' '3.2. Direction toward Io<*>' 'Page 315'
has d bpedia resource: Semantic interoperability
supports: Interoperability

Sensing
creator: sebastian
type: NamedIndividual
type: Concern
comment: The concern of being able to measure values from a defined environment.
note: Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.1 THE CONTROL DOMAIN' 'Page 28'
has d bpedia resource: Sensor
supports: Internet of Things

Service Access Control
creator: sebastian
associated with: Data Access Control
type: NamedIndividual
type: Concern
comment: Service access control is the selective restriction of access to a specific (web) service or process. The act of accessing may mean consuming, entering, or using. Permission to access a service is called service authorization. Locks and login credentials are two analogous mechanisms of access control. (source: wikipedia)
see also: IoT-A Requirement UNI.611
has d bpedia resource: Network Access Control
supports: Authorization

Service Choreography
creator: sebastian
type: NamedIndividual
type: Concern
comment: 2 to n Data Apps/Services/Data Provider are connected (without a central coordinator)
comment: Service choreography is a form of service composition in which the interaction protocol between several partner services is defined from a global perspective.The intuition underlying the notion of service choreography can be summarised as follows: “Dancers dance following a global scenario without a single point of control" That is, at run-time each participant in a service choreography executes its part of it (i.e. its role) according to the behavior of the other participants.A choreography's role specifies the expected messaging behavior of the participants that will play it in terms of the sequencing and timing of the messages that they can consume and produce. (source: wikipedia)
see also: IoT-A Requirement UNI.096
see also: IoT-A Requirement UNI.704
has d bpedia resource: Service choreography
supports: Service Composition

Service Composition
creator: sebastian
has stakeholder: Q1548249
type: NamedIndividual
type: Concern
comment: 2 to n Data Apps/Devices/Services are connected
comment: In computing, service composability is a design principle, applied within the service-orientation design paradigm, that encourages the design of services that can be reused in multiple solutions that are themselves made up of composed services. The ability to recompose the service is ideally independent of the size and complexity of the service composition. This principle is directly responsible for the agility promised by SOA as it promotes composing new solutions by reusing existing services. (source: wikipedia)
see also: IoT-A Requirement UNI.014
see also: IoT-A Requirement UNI.031
see also: IoT-A Requirement UNI.043
see also: IoT-A Requirement UNI.089
see also: IoT-A Requirement UNI.094
see also: IoT-A Requirement UNI.234
see also: IoT-A Requirement UNI.244
see also: IoT-A Requirement UNI.245
see also: IoT-A Requirement UNI.247
see also: IoT-A Requirement UNI.251
see also: IoT-A Requirement UNI.253
has d bpedia resource: Service composition
supports: interoperability

Service Deployment
type: NamedIndividual
type: Concern
comment: Software deployment is all of the activities that make a software system available for use. The general deployment process consists of several interrelated activities with possible transitions between them. These activities can occur at the producer side or at the consumer side or both. Because every software system is unique, the precise processes or procedures within each activity can hardly be defined. Therefore, "deployment" should be interpreted as a general process that has to be customized according to specific requirements or characteristics. (source: wikipedia)
see also: IoT-A Requirement UNI.429
has d bpedia resource: Software deployment
supports: Service life-cycle management

Service Description
creator: sebastian
has stakeholder: developer
type: NamedIndividual
type: Concern
comment: A Service Description plays an important role in enabling access to a service. Most service description languages are designed for machine consumption, allowing for the automatic creation of code skeletons, easier search, and classification of services. However, people may also find descriptions useful to learn about the use of parameters or the precise semantics of some operation. (https://www.w3.org/standards/webofservices/description)
see also: IoT-A Requirement UNI.004
see also: IoT-A Requirement UNI.036
see also: IoT-A Requirement UNI.042
see also: IoT-A Requirement UNI.240
see also: IoT-A Requirement UNI.715
supports: Semantic Interoperability

ServiceDescriptions
see also: IoT-A Requirement UNI.244

Service Discovery
creator: sebastian
type: NamedIndividual
type: Concern
comment: How to find desired (Web) services, Data Apps, functionalities.
see also: IoT-A Requirement UNI.406
see also: IoT-A Requirement UNI.408
see also: IoT-A Requirement UNI.414
see also: IoT-A Requirement UNI.415
see also: IoT-A Requirement UNI.416
see also: IoT-A Requirement UNI.422
see also: IoT-A Requirement UNI.427
note: Publications referred: '<https://doi.org/10.1016/j.jksuci.2016.10.003>' '2.8.2. Societal data service' 'Page 309'
has d bpedia resource: Service discovery

Service Isolation
creator: sebastian
type: NamedIndividual
type: Concern
comment: Service isolation via a process group (as done with Docker) or by least privilege with clear separation and support for additional security modules (as done by trustme).
narrower: Isolation
has d bpedia resource: Process isolation

Service level agreement
creator: sebastian
type: NamedIndividual
type: Concern
comment: A service-level agreement (SLA) is defined as an official commitment that prevails between a service provider and the customer. Particular aspects of the service – quality, availability, responsibilities – are agreed between the service provider and the service user. The most common component of SLA is that the services should be provided to the customer as agreed upon in the contract. As an example, Internet service providers and telcos will commonly include service level agreements within the terms of their contracts with customers to define the level(s) of service being sold in plain language terms. In this case the SLA will typically have a technical definition in terms of mean time between failures (MTBF), mean time to repair or mean time to recovery (MTTR); identifying which party is responsible for reporting faults or paying fees; responsibility for various data rates; throughput; jitter; or similar measurable details. (source: wikipedia)
see also: IoT-A Requirement UNI.060
has d bpedia resource: Service-level agreement
supports: Service life-cycle management

Service life-cycle management
has stakeholder: SystemArchitect
type: NamedIndividual
type: Concern
comment: Information lifecycle management (ILM) refers to strategies for administering storage systems on computing devices. ILM is the practice of applying certain policies to effective information management. This practice had its basis in the management of information in paper or other physical forms (microfilm, negatives, photographs, audio or video recordings and other assets). ILM includes every phase of a "record" from its beginning to its end. And while it is generally applied to information that rises to the classic definition of a record (and thus related to records management), it applies to all informational assets. (source: wikipedia)
see also: IoT-A Requirement UNI.087
has d bpedia resource: Information lifecycle management

Service Orchestration
creator: sebastian
has stakeholder: Q1548249
type: NamedIndividual
type: Concern
comment: A Service/Data App are connected with Data Provider, other Services/Data Apps in order to fulfill a certain task, orchestrates by a central entity.
see also: IoT-A Requirement UNI.010
note: Publications referred: '<https://doi.org/10.1016/j.jksuci.2016.10.003>' '2.2.2. Middleware enablement' 'Page 300'
has d bpedia resource: Orchestration (computing)
has wikipedia article: Deployment
has wikipedia article: Orchestration (computing)
supports: Service Composition

Service Selection
creator: sebastian
type: NamedIndividual
type: Concern
comment: The ability of a system to invoke or deploy the desired service/Data App.
supports: Service Composition

Service Recovery
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: Organizations should make sure that the cloud provider imitates the data and provides services in case the major site is down. Find out the time to restore services and the data loss if any, in case the chief site goes down.
has wikipedia article: Service recovery
supports: Cloud Computing Capability
supports: Reliability

Software Updates
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: Software update is the process that prevents compromise an IoT based system. Organizations are yet to be geared up with mechanisms to Remotely Patch Connected Devices.
has wikipedia article: Wikipedia:Software updates
supports: Evolvability

Spatial modeling
type: NamedIndividual
type: Concern
comment: A system shall have a semantic understanding of distance and location.
see also: IoT-A Requirement UNI.098
has d bpedia resource: Spatial analysis
supports: Data Description
supports: Semantic Interoperability

Layer
type: Class
comment: A stakeholder is an individual, team, organization or classes thereof,having an interest in a concern and by extension an interest in the viewpoint and system.
comment: Describes the layers of the standardization frameworks. In some cases, the layers are connected to dimensions of the frameworks.
label: Stakeholder
subclass of: Person
note: Publications referred: 'IIC:PUB:G1:V1.80:20170131' '4.1 STAKEHOLDERS' 'Page 20'
has wikipedia article: Stakeholder

Standard
attribution name: Copyright © 2016 IEC Geneva, Switzerland.
attribution URL: http://www.iec.ch
type: Class
comment: A document, established by consensus and approved by a recognized body, that provides, for common and repeated use, rules, guidelines or characteristics for activities or their results, aimed at the achievement of the optimum degree of order in a given context.
subclass of: Publication
has Abbreviated Name: IS

Standard Classification
type: Class
comment: Describes categorization areas that the different Standardizations Initiatives use to category Standards.

StandardOrganization
creator: irlan
type: Class
comment: Define the standards organizations that develop and publish industry standards
subclass of: Organization

StandardPart
type: Class
comment: Typically Standards are divided into parts. E.g., ISA 95 has part Part 1: Models and Terminology, Part 2: Object Model Attributes, etc.
subclass of: Publication

Standarization Framework
creator: irlan
type: Class
comment: Describes existings Standardizations Initiatives, e.g, RAMI, NIST.
alternative label: Reference Architecture

Stream processing
creator: sebastian
type: NamedIndividual
type: Concern
comment: Stream processing is a computer programming paradigm, equivalent to dataflow programming, event stream processing, and reactive programming, that allows some applications to more easily exploit a limited form of parallel processing. (source: wikipedia)
has d bpedia resource: Stream processing
supports: Data Processing

Syntactic Interoperability
creator: sebastian
type: NamedIndividual
type: Concern
comment: If two or more systems are capable of communicating with each other, they exhibit syntactic interoperability when using specified data formats and communication protocols. XML or SQL standards are among the tools of syntactic interoperability. This is also true for lower-level data formats, such as ensuring alphabetical characters are stored in a same variation of ASCII or a Unicode format (for English or international text) in all the communicating systems. source: <https://en.wikipedia.org/wiki/Interoperability>
see also: IoT-A Requirement UNI.071
see also: IoT-A Requirement UNI.096
see also: IoT-A Requirement UNI.241
see also: IoT-A Requirement UNI.318
see also: IoT-A Requirement UNI.326
see also: IoT-A Requirement UNI.327
see also: IoT-A Requirement UNI.506
see also: IoT-A Requirement UNI.709
note: Publications referred: '<https://doi.org/10.1016/j.jksuci.2016.10.003>' '2.8.2. Societal data service' 'Page 308'
has wikipedia article: Syntactic interoperability
supports: Interoperability

SyntacticInteroperablity
see also: IoT-A Requirement UNI.311
see also: IoT-A Requirement UNI.312
see also: IoT-A Requirement UNI.313
see also: IoT-A Requirement UNI.315

System Engineer
type: Stakeholder Group
type: NamedIndividual
type: Layer
note: Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.1 BUSINESS VIEWPOINT' 'Page 15' 'Priyanka'

System evolution
creator: sebastian
type: NamedIndividual
type: Concern
comment: Software evolution is the term used in software engineering (specifically software maintenance) to refer to the process of developing software initially, then repeatedly updating it for various reasons. (source: wikipedia)
see also: IoT-A Requirement UNI.211
see also: IoT-A Requirement UNI.229
has d bpedia resource: Software evolution
supports: Evolvability

System Recovery
creator: sebastian
type: NamedIndividual
type: Concern
supports: Reliability

Technical Report
attribution URL: http://www.iec.ch
type: Class
type: namedIndividial
comment: Specifies that a given Publication is a Technical Report
comment: Technical Reports contain collected data of a kind different from that normally published as an International Standard, for example data obtained from a survey carried out among national committees, data of work in other international organizations or data on "the state of the art" in relation to standards of national committees on a particular subject.Technical Reports are entirely informative in nature and shall not contain matter implying that they are normative
subclass of: Publication
has Abbreviated Name: TR

Technical Specification
attribution URL: http://www.iec.ch
type: Class
type: namedIndividial
comment: Specifies that a given Publication is a Technical Specification
comment: Technical Specifications are often published when the subject under question is still under development or when insufficient consensus for approval of an International Standard is available.Technical Specifications approach International Standards in terms of detail and completeness, but have not yet passed through all approval stages either because consensus has not been reached or because standardization is seen to be premature.
subclass of: Publication
has Abbreviated Name: TS

Technology
creator: sebastian
type: Class
comment: A Technology is an implementation of one or many standards in order to achieve a goal.

Industrial Internet Architecture Version 1
type: NamedIndividual
type: oaSpecificResource
note: The Industrial Internet of Things Volume G1: Reference Architecture IIC:PUB:G1:V1.80:20170131
has open resource: IIC PUB G1 V1.80 2017-01-31.pdf

The Industrial Internet of Things Volume G5: Connectivity Framework
type: NamedIndividual
type: oaSpecificResource
note: The Industrial Internet of Things Volume G5: Connectivity Framework IIC:PUB:G5:V1.0:PB:20170228
has open resource: IIC PUB G5 V1.0 PB 20170228.pdf

Thing description
creator: sebastian
has stakeholder: Q1548249
has stakeholder: Developer
type: NamedIndividual
type: Concern
comment: 'Things' in terms of physical objects in the IoT need to be described in order to identify them and to provide further information.
see also: IoT-A Requirement UNI.036
see also: IoT-A Requirement UNI.042
see also: IoT-A Requirement UNI.213
see also: IoT-A Requirement UNI.237
see also: IoT-A Requirement UNI.240
see also: IoT-A Requirement UNI.404
see also: IoT-A Requirement UNI.509
see also: IoT-A Requirement UNI.512
supports: Semantic Interoperability

Thing mobility
creator: sebastian
type: NamedIndividual
type: Concern
comment: A Thing in terms of Internet of Things (IoT) needs to be moveable.
see also: IoT-A Requirement UNI.050
see also: IoT-A Requirement UNI.233
supports: Data Access
supports: Internet of Things
supports: Service Deployment

Thing representation
creator: sebastian
type: NamedIndividual
type: Concern
comment: Physical objects need to be represented.
see also: IoT-A Requirement UNI.239
supports: Internet of Things

Time Synchronization
creator: sebastian
has stakeholder: Developer
type: NamedIndividual
type: Concern
see also: IoT-A Requirement UNI.089
has d bpedia resource: Synchronization (computer science)
has d bpedia resource: Synchronization refers to one of two distinct but related concepts: synchronization of processes, and synchronization of data. Process synchronization refers to the idea that multiple processes are to join up or handshake at a certain point, in order to reach an agreement or commit to a certain sequence of action. Data synchronization refers to the idea of keeping multiple copies of a dataset in coherence with one another, or to maintain data integrity. Process synchronization primitives are commonly used to implement data synchronization. (sourc: wikipedia)
supports: Service Composition

IDS Trusted Connector
creator: sebastian
associated with: DIN SPEC 27070
associated with: Industrial Data Space Reference Architecture Model
type: NamedIndividual
type: Technology
comment: The advent of the Industrial Internet of Things (IIoT) also raises challenges with respect to security and privacy of sensitive and personal data that is created by sensors and processed by services hosted in different administrative domains. The Industrial Data Space initiative addresses these challenges and proposes a secure edge gateway platform named "Trusted Connector". In this report, we introduce the main security building blocks of the Trusted Connector and point out how they help protecting business-critical data and preserving the user's privacy.
has official resource: https://arxiv.org/abs/1804.09442
alignes With: DIN SPEC 27070

Trustworthiness
creator: sebastian
type: NamedIndividual
type: Concern
comment: Trustworthiness is the degree of confidence one has that the system performs as expected in respect to all the key system characteristics in the face of environmental disruptions, human errors, system faults and attacks. source: IISF
see also: IoT-A Requirement UNI.062
see also: IoT-A Requirement UNI.602
see also: IoT-A Requirement UNI.613
has d bpedia resource: Software trustworthiness

Unicast
creator: sebastian
type: NamedIndividual
type: Concern
comment: one-to-one connectivity
see also: IoT-A Requirement UNI.301
see also: IoT-A Requirement UNI.304
supports: CardinalityOfDataSources

Unreliable Network
creator: sebastian
has stakeholder: Developer
has stakeholder: System Architect
type: NamedIndividual
type: Concern
comment: Productive systems must inherently cover issues caused by unreliable networks.
see also: IoT-A Requirement UNI.308
see also: IoT-A Requirement UNI.318
supports: Reliability

User Interaction
creator: sebastian
has stakeholder: EndUser
type: NamedIndividual
type: Concern
comment: Interaction design, often abbreviated as IxD, is defined as "the practice of designing interactive digital products, environments, systems, and services." While the digital side of this statement is true, Interaction design is also valid when creating physical (non-digital) products, covering the ideology of how a user may interact with it. (source: wikipedia)
see also: IoT-A Requirement UNI.019
see also: IoT-A Requirement UNI.092
see also: IoT-A Requirement UNI.214
see also: IoT-A Requirement UNI.252
has d bpedia resource: Interaction design
supports: UserExperience

User Preferences
creator: sebastian
type: NamedIndividual
type: Concern
comment: Users can have the possibility to prefer one service over another for any reason.
see also: IoT-A Requirement UNI.253
supports: Service level agreement

Vendor Lockin
creator: Muhammad Usman
type: NamedIndividual
type: Concern
comment: There is a lot of competition among vendors to dominate the cloud market. According to Columbus’ report, a study conducted by IDG Cloud Computing Study realized that Cloud investment rose by 19% in larger scale enterprises consisting of more than a thousand employees who spend a mean of $3.3 million annually.
has wikipedia article: Vendor lock-in
supports: Business Context
supports: Cloud Computing Capability

Viewpoint
creator: sebastian
type: Class
comment: ISO 42010 definition of a Viewpoint
subclass of: Standard Classification
has d bpedia resource: IEC_42010
has official resource: http://www.iso-architecture.org/42010/
has wikipedia article: Conceptual Model - Architecture Viewpoint

VirtualEntities
see also: IoT-A Requirement UNI.409

Virtual Entity
creator: sebastian
type: NamedIndividual
type: Concern
comment: Entities are provided through a virtual form.
note: Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.1 THE CONTROL DOMAIN' 'Page 28'
has d bpedia resource: Digital twin
supports: Thing representation

X-Road Architecture Technical Specification Version: 1.0 18.09.2015 15 pages Doc. ID: ARC-G
type: NamedIndividual
type: oaSpecificResource

has Abbreviated Name
type: DatatypeProperty
comment: Abbreviated name of the thing.
domain: Thing
range: PlainLiteral

alignes With
type: ObjectProperty
type: SymmetricProperty
comment: indicates that some Standard Classification entity has a similar scope as another. This property most probably is symmetric but not transitive.
domain: Standard Classification
range: Standard Classification
sub property of: associatedWith

belongs To
creator: irlan
type: ObjectProperty
comment: A Standard Organization that belongs to the country
domain: StandardOrganization
range: Country

has Domain Name
type: DatatypeProperty
comment: Points the Standard with the name of the Industrial Domain
domain: Domain
range: PlainLiteral

has Formation Date
type: DatatypeProperty
type: FunctionalProperty
comment: Formation date of the Organization
domain: StandardOrganization
range: date

frames
type: ObjectProperty
comment: A relation specifying that a vewpoint regards a Concern.
domain: Viewpoint
range: Concern
sub property of: associatedWith
has official resource: http://www.iso-architecture.org/42010/

has Available Language
creator: irlan
type: ObjectProperty
comment: Languages in which the document of the Standard is available, e.g., English, French, Spanish
comment: Points to Languages in which the standard document is available, e.g., English, French, etc. Defined as subProperty of dcterms:language
domain: Document
label: hasAvailableLanguage
range: LinguisticSystem
sub property of: language

has Classification
creator: irlan
type: ObjectProperty
comment: An Standard is isCategorizedBy a given Categorization Area which is connected to a specific Standarization Initiative
domain: Standard
range: Standard Classification

has Developer
creator: irlan
type: ObjectProperty
comment: The organization that developed this Standard
domain: Publication
range: StandardOrganization
sub property of: maker

has Edition
type: DatatypeProperty
comment: Indicates the current Edition/Version number of the document.
domain: Document
range: float

has File Size
creator: irlan
type: ObjectProperty
comment: The size of document file in some unit, e.g., 104 Kilobyte.
domain: Document
range: Measure
note: 1. Reference for om2:Measure <http://www.ontology-of-units-of-measure.org/page/om-2/Measure> 2. om2:Measure om2:hasNumericalValue xsd:float; 3. om2:Measure om2:hasUnit om2:Unit; 4. om2:hasUnit om2:InformationCapacityUnit; is another possibility for range that could not be verified. 5. rdfs:seeAlso <http://www.ontology-of-units-of-measure.org/page/om-2/kilobyte> 6. Documentation on Measure <https://github.com/HajoRijgersberg/OM>

has Headquater In
creator: irlan
type: ObjectProperty
comment: Denotes the countries in which the Headquarter of the organization who publishes the Standart
domain: StandardOrganization
range: Place

has ICS
type: ObjectProperty
comment: Serves as a catalogue of International Classification For Standards
domain: Publication
range: InternationalClassificationForStandards

has Implementation Format
type: DatatypeProperty
comment: Describes the name of the implementation or serialization format of the Publication, e.g., XML, Document, binary, batch
domain: Publication
range: Literal

has Objective
type: DatatypeProperty
comment: Specifies the objectives for the different ISA 95 levels.
domain: ISA 95 Level
range: string

has Ontology
type: DatatypeProperty
comment: Point to the URL of a recognized Ontology representation of the Standard
domain: Publication
range: anyURI

has Pages
type: DatatypeProperty
comment: Indicates the number of pages in the document.
domain: Document
range: integer

has Previous Version
type: ObjectProperty
comment: Indicates the list of Standards that are previous versions of a Standard. For example,IEC 60038:2009 has IEC 60038:1983+AMD1:1994+AMD2:1997,IEC 60038:1983/AMD2:1997,IEC 60038:1983/AMD1:1994,IEC 60038:1983,IEC 60038:1975/AMD1:1977,IEC 60038:1975,IEC 60038:1967,IEC 60038:1954,IEC 60038:1938,IEC 60038:1927 as previous versions.
sub property of: related To

has Publication Date
type: DatatypeProperty
comment: Publication date of the Publication
domain: Publication
range: date

has Publisher
creator: irlan
type: ObjectProperty
comment: The organization that published this Standard
domain: Publication
range: StandardOrganization
sub property of: maker

has Stability Date
type: DatatypeProperty
comment: Stability date of a publication. Publications are valid for a certain period, i.e., the Stability Period. This property defines the end of the stability period.
domain: Publication
range: gYear
note: The data specified is not actually a Date but an Year

has Status
type: DatatypeProperty
comment: Publication status of the Standard, e.g., Valid, Revised, Published, under preparation, Released
domain: Publication
range: Literal

has Target Concern
type: ObjectProperty
comment: The relation declaring that a standard is relevant or targets a certain concern.
domain: Standard
range: Concern
sub property of: associatedWith

has Task
type: DatatypeProperty
comment: Specifies the tasks for the different ISA 95 levels.
domain: ISA 95 Level
range: string

has Technical Committee
type: ObjectProperty
comment: Specifies the Technical Committee or a Sub-Committee that is responsible for creation and maintenance of a standard
domain: Publication
range: TechnicalCommittee

iShare
associated with: HTTP
associated with: ISO/IEC 9594
associated with: REST
associated with: RFC 5246
associated with: JSON Web Token
associated with: XACML
type: NamedIndividual
type: Organization
comment: iSHARE is a uniform set of agreements or a scheme for identification, authentication and authorization. All companies that join the iSHARE Scheme comply with the set of agreements. They all use the same methods to both provide and gain access to data. (source: iShare: 'It is not a platform…')
has official resource: www.ishareworks.org
has Target Concern: Identification
has Target Concern: Interoperability

Introduction of X-tee
creator: EstonianInformationSystemAuthority
type: NamedIndividual
type: Document
type: Publication
type: Technical Report
comment: It is a guide intended for those who want to acquaint themselves more thoroughly with the X-tee (e.g. theose who are working for an organisation which will soon join the X-tee). It introduces the X-tee’s complex terminological system slowly and in a comprehensible way, so that the reader can painlessly achieve the preliminary familiarity with the X-tee necessary to engage with more explicitly technical and complex manuals. (source: https://www.ria.ee/en/state-information-system/x-tee/introduction-x-tee.html)
maker: EstonianInformationSystemAuthority
has Classification: x-road Deplyoment View
has Classification: x-road Protocols and Interfaces
has Classification: x-road System Components
has Classification: x-road Technology Matrix
has official resource: introduction-x-tee.html
has Publisher: EstonianInformationSystemAuthority

is Described in
type: ObjectProperty
comment: Links the Standarization Frameworks with the Classification of Standards
domain: Standard Classification
range: Standarization Framework

is Implementation Of
creator: irlan
type: ObjectProperty
comment: Represent the relation that connects two standards when standard A is the implementation of standard B, e.g., B2MML isImplementationOf ISA-95.
sub property of: related To

Org Name
type: DatatypeProperty
comment: Name of the Organization
domain: StandardOrganization
range: PlainLiteral

related To
creator: irlan
type: ObjectProperty
type: SymmetricProperty
type: TransitiveProperty
comment: Represent any type of relation that connects two standards.
domain: Standard
range: Standard
alternative label: has Associated Standard

std Part Name
type: DatatypeProperty
comment: Name of the standard part.
domain: StandardPart
range: string

use Structure Of
creator: irlan
type: ObjectProperty
comment: Standard A uses the structure of Standard B. For example, OPC UA uses Structure Of IEC_61804 (EDDL)
sub property of: related To

uses
creator: irlan
type: ObjectProperty
comment: Defines that Standard A uses Standard B. For example, IEC_62714(AML) uses MathML.
sub property of: related To

x-road
type: NamedIndividual
type: Data Sharing Initiative

x-road Deplyoment View
associated with: IDS RAM System Layer
associated with: IIRA Implementation Viewpoint
associated with: RAMI Integration Layer
type: NamedIndividual
type: Standard Classification
type: x-road Section
is Described in: x-Tee
alignes With: IDS RAM System Layer
alignes With: IIRA Implementation Viewpoint
alignes With: RAMI Integration Layer
frames: Communication
frames: Data Access
frames: Security
frames: Service Deployment
frames: Service life-cycle management
frames: Trustworthiness

xRoadDeploymentViewAnno
type: NamedIndividual
type: oaAnnotation
oahas body: x-road Deplyoment View
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 16
    oahas start selector: Page 15
  oahas source: X-Road Architecture Technical Specification Version: 1.0 18.09.2015 15 pages Doc. ID: ARC-G

x-road Protocols and Interfaces
associated with: IDS RAM Process Layer
associated with: IIRA Control Domain
associated with: RAMI Integration Layer
type: NamedIndividual
type: Standard Classification
type: x-road Section
is Described in: x-Tee
alignes With: IDS RAM Process Layer
alignes With: IIRA Control Domain
alignes With: RAMI Integration Layer
frames: Communication
frames: Interoperability
frames: Syntactic Interoperability

xRoadProtocolsInterfacesAnno
type: NamedIndividual
type: oaAnnotation
oahas body: x-road Protocols and Interfaces
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 14
    oahas start selector: Page 10
  oahas source: X-Road Architecture Technical Specification Version: 1.0 18.09.2015 15 pages Doc. ID: ARC-G

x-road Section
creator: sebastian
type: Class
subclass of: Standard Classification
subclass of: Restriction
  has value: x-Tee
  on property: is Described in

x-road System Components
associated with: IDS RAM Business Layer
associated with: IDS RAM Process Layer
associated with: IIC Security Framework
associated with: RAMI Functional Layer
type: NamedIndividual
type: Standard Classification
type: x-road Section
is Described in: x-Tee
alignes With: IDS RAM Business Layer
alignes With: IDS RAM Process Layer
alignes With: IIC Security Framework
alignes With: RAMI Functional Layer
frames: Authentication
frames: Communication
frames: Identity Management
frames: Secure Communication
frames: Security
frames: Security Configuration
frames: Trustworthiness

xRoadSystemComponentsAnno
type: NamedIndividual
type: oaAnnotation
oahas body: x-road System Components
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 10
    oahas start selector: Page 7
  oahas source: X-Road Architecture Technical Specification Version: 1.0 18.09.2015 15 pages Doc. ID: ARC-G

x-road Technology Matrix
type: NamedIndividual
type: Standard Classification
type: x-road Section
is Described in: x-Tee

xRoadTechnologyMatrixAnno
type: NamedIndividual
type: oaAnnotation
oahas body: x-road Technology Matrix
oahas target: oaSpecificResource
  oahas selector: oaRangeSelector
    oahas end selector: Page 15
    oahas start selector: Page 14
  oahas source: X-Road Architecture Technical Specification Version: 1.0 18.09.2015 15 pages Doc. ID: ARC-G

x-Tee
type: NamedIndividual
type: Architecture Description
type: Standarization Framework
has Publisher: x-road

alignes With
type: ObjectProperty
type: SymmetricProperty
comment: indicates that some Standard Classification entity has a similar scope as another. This property most probably is symmetric but not transitive.
domain: Standard Classification
range: Standard Classification
sub property of: associatedWith

frames
type: ObjectProperty
comment: A relation specifying that a vewpoint regards a Concern.
domain: Standard Classification
range: Concern
sub property of: associatedWith
has official resource: http://www.iso-architecture.org/42010/

has Target Concern
type: AnnotationProperty
type: ObjectProperty
comment: The relation declaring that a standard is relevant or targets a certain concern.
domain: Class
  union of: Standard
  union of: Standarization Framework
range: Concern
sub property of: associatedWith

supports
type: ObjectProperty
comment: A relation between two different concerns where dealing with the subject Concern supports in achieving the object concern
domain: Concern
range: Concern

Industrial IoT Architecture Ontology
created: 2017-01-25
created: 2019-06-09
creator: steffen-lohmann
creator: irlan-grangel-gonzalez
creator: Priyanka
creator: sebastian
creator: paul-baptista-601177b2
Date Modified: 2017-09-08
Date Modified: 2019-06-09
Date Modified: 2019-07-21
publisher: Fraunhofer-Gesellschaft
rights: This work is distributed under a Creative Commons Attribution License (http://creativecommons.org/licenses/by/3.0/).
title: Standards Ontology
preferred namespace prefix: sto
preferred namespace prefix: sto_iot
preferred namespace uri: https://w3id.org/i40/sto#
repository: StandardsOntology
type: Ontology
comment: An ontology to describe standards related to Industry 4.0 and Smart Manufacturing
comment: An ontology to describe the landscape of IIoT, Industry 4.0 and Smart Manufacturing
comment: The Internet of things (IoT) is the network of devices such as vehicles, and home appliances that contain electronics, software, sensors, actuators, and connectivity which allows these things to connect, interact and exchange data.
imports: concerns.ttl
imports: sto.ttl
version IRI: concerns
version info: 0.2
version info: 0.3
has d bpedia resource: Internet of things
has official resource: https://webstore.iec.ch/publication/153
has wikipedia article: Internet of things

Trusted Connector
creator: Industrial Data Space Reference Architecture Model
associated with: Administration Shell
associated with: Industrial Data Space Reference Architecture Model
type: NamedIndividual
type: Technology
comment: TODO: model IDS concepts correctly
maker: Industrial Data Space Reference Architecture Model
alignes With: Administration Shell

IDS RAM Layer
type: Class
subclass of: Standard Classification
equivalent class: Class
  one of: BusinessLayer
  one of: FunctionalLayer
  one of: InformationLayer
  one of: ProcessLayer
  one of: SystemLayer