diff --git a/concerns.ttl b/concerns.ttl index c4a36cb..df27f08 100644 --- a/concerns.ttl +++ b/concerns.ttl @@ -227,7 +227,7 @@ Spurce: OpenFog Consortum Architecture Whitepaper"""@en ; sto:Anonymity rdf:type owl:NamedIndividual , sto:Concern ; sto_iot:supports sto:Privacy ; - ; + sto:hasStakeholder ; rdfs:comment "Anonymity is the guarantee for a user to interact with a system without being tracked or connected to its real-world identity."@en ; rdfs:label "Anonymity"@en ; rdfs:seeAlso "IoT-A Requirement UNI.001" , @@ -291,7 +291,7 @@ sto:AutonomousCommunication rdf:type owl:NamedIndividual , sto:Concern ; sto_iot:supports sto:Communication , sto:ServiceChoreography ; - ; + sto:hasStakeholder ; rdfs: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."@en ; rdfs:label "Autonomous Communication"@en ; rdfs:seeAlso "IoT-A Requirement UNI.005" , @@ -303,7 +303,7 @@ sto:AutonomousCommunication rdf:type owl:NamedIndividual , sto:AutonomousConfiguration rdf:type owl:NamedIndividual , sto:Concern ; sto_iot:supports sto:ServiceChoreography ; - ; + sto:hasStakeholder ; rdfs:comment "A system built using the Reference Architecture shall be able to remotely control and configure devices."@en ; rdfs:label "Autonomous Configuration"@en ; rdfs:seeAlso "IoT-A Requirement UNI.015" , @@ -547,7 +547,7 @@ sto:ConstrainedDevices rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:IoT ; - "System Architect TODO"@en ; + sto:hasStakeholder "System Architect TODO"@en ; rdfs: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."@en , "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)"@en ; rdfs:label "Constrained Devices"@en ; @@ -560,7 +560,7 @@ sto:ConstrainedDevices rdf:type owl:NamedIndividual , sto:ContextAwareness rdf:type owl:NamedIndividual , sto:Concern ; sto_iot:supports sto:AutonomousCommunication ; - "Developer"@en ; + sto:hasStakeholder "Developer"@en ; rdfs: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."@en ; rdfs:label "Context Awareness"@en ; rdfs:seeAlso "IoT-A Requirement UNI.407" , @@ -587,7 +587,7 @@ sto:CrossDomainIdentityManagement rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:IdentityManagement ; - "System Architect"@en ; + sto:hasStakeholder "System Architect"@en ; rdfs:comment "A system built using the ARM shall support identity-locator split, i.e. making the device's identity independent from its locator."@en ; rdfs:label "Cross-domain Identity Management"@en ; rdfs:seeAlso "IoT-A Requirement UNI.314" ; @@ -609,7 +609,7 @@ sto:DataAccessControl rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:Authorization ; - , + sto:hasStakeholder , ; rdfs:comment "Automated access control based on formalized descriptions."@en , "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)"@en ; @@ -660,7 +660,7 @@ sto:DataDescription rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:SemanticInteroperability ; - ; + sto:hasStakeholder ; rdfs:comment , "Methods to unambiguously describe data resources."@en ; rdfs:label "Data Description"@en ; @@ -769,7 +769,7 @@ sto:DataMarkets rdf:type owl:NamedIndividual , sto:DataProcessing rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; - ; + sto:hasStakeholder ; rdfs:comment "Data processing and analytic components from the App Store create flexible data processing pipelines."@en ; rdfs:label "Data Processing"@en ; rdfs:seeAlso "IoT-A Requirement UNI.018" , @@ -973,7 +973,7 @@ sto:EnergyEfficiency rdf:type owl:NamedIndividual , sto:EventDrivenMessaging rdf:type owl:NamedIndividual , sto:Concern ; sto_iot:supports sto:DataInMotion ; - ; + sto:hasStakeholder ; rdfs:label "Event-Driven Messaging"@en ; rdfs:seeAlso "IoT-A Requirement UNI.005" , "IoT-A Requirement UNI.233" ; @@ -1041,7 +1041,7 @@ sto:FaultTolerance rdf:type owl:NamedIndividual , sto:GeoTracking rdf:type owl:NamedIndividual , sto:Concern ; sto_iot:supports sto:ContextAwareness ; - ; + sto:hasStakeholder ; rdfs:comment "A system built using the ARM shall support physical entity location tracking (geo spatial and/or logical location)"@en ; rdfs:label "Geo tracking"@en ; rdfs:seeAlso "IoT-A Requirement UNI.016" ; @@ -1092,7 +1092,7 @@ sto:IPv4Support rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:SyntacticInteroperability ; - "System Architect"@en ; + sto:hasStakeholder "System Architect"@en ; rdfs:comment "Communication with non-IPv6 networks must be possible (IPv4, others)."@en ; rdfs:label "IPv4 Support"@en ; rdfs:seeAlso "IoT-A Requirement UNI.313" ; @@ -1164,7 +1164,7 @@ sto:IntegrityProtection rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:DeviceSecurity ; - "Device/Service Owner" ; + sto:hasStakeholder "Device/Service Owner" ; rdfs: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)"@en , "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."@en ; rdfs:label "Integrity Protection and Verification"@en ; @@ -1178,7 +1178,7 @@ sto:IntegrityProtection rdf:type owl:NamedIndividual , ### https://w3id.org/i40/sto#Interoperability sto:Interoperability rdf:type owl:NamedIndividual , sto:Concern ; - , + sto:hasStakeholder , ; rdfs:comment "A systems ability to connect with other systems."@en , "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]."@en ; @@ -1275,7 +1275,7 @@ sto:MaintenanceCost rdf:type owl:NamedIndividual , sto:MessagePriority rdf:type owl:NamedIndividual , sto:Concern ; sto_iot:supports sto:Communication ; - , + sto:hasStakeholder , ; rdfs:comment "Message precedence is an indicator attached to a message indicating its level of urgency. (source: wikipedia)"@en ; rdfs:label "Message precedence"@en ; @@ -1377,7 +1377,7 @@ sto:Performance rdf:type owl:NamedIndividual , sto:PeriodicCommunication rdf:type owl:NamedIndividual , sto:Concern ; sto_iot:supports sto:EventDrivenMessaging ; - ; + sto:hasStakeholder ; rdfs:label "Periodic Communication"@en ; rdfs:seeAlso "IoT-A Requirement UNI.005" . @@ -1425,7 +1425,7 @@ sto:ProvenanceTracking rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:Security ; - ; + sto:hasStakeholder ; rdfs:comment "Data provenance includes the data's origins, what happens to it and where it moves/moved over time."@en ; rdfs:label "Provenance Tracking"@en ; rdfs:seeAlso "IoT-A Requirement UNI.041" , @@ -1463,7 +1463,7 @@ sto:QualityOfService rdf:type owl:NamedIndividual , sto:RadioActivityControl rdf:type owl:NamedIndividual , sto:Concern ; sto_iot:supports sto:EnergyControl ; - ; + sto:hasStakeholder ; rdfs:comment "The user shall be able to control the radio activity of the system."@en ; rdfs:label "Radio activity control"@en ; rdfs:seeAlso "IoT-A Requirement UNI.021" . @@ -1473,7 +1473,7 @@ sto:RadioActivityControl rdf:type owl:NamedIndividual , sto:RealTimeAnalytics rdf:type owl:NamedIndividual , sto:Concern ; sto_iot:supports sto:DataAnalytics ; - ; + sto:hasStakeholder ; rdfs: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."@en ; rdfs:label "Real Time Analytics"@en ; rdfs:seeAlso "IoT-A Requirement UNI.020" ; @@ -1512,7 +1512,7 @@ sto:Resilience rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:Trustworthiness ; - , + sto:hasStakeholder , ; rdfs: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)"@en ; rdfs:label "Resilience"@en ; @@ -1588,7 +1588,7 @@ sto:SecureCommunication rdf:type owl:NamedIndividual , dcterms:creator sto:sebastian ; sto_iot:supports sto:Communication , sto:IntegrityProtection ; - , + sto:hasStakeholder , , ; rdfs:comment , @@ -1608,7 +1608,7 @@ sto:Security rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:Privacy ; - , + sto:hasStakeholder , ; rdfs: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)"@en ; rdfs:label "Security"@en ; @@ -1649,7 +1649,7 @@ sto:SemanticInteroperability rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:Interoperability ; - ; + sto:hasStakeholder ; rdfs: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: """@en ; rdfs:label "Semantic Interoperability"@en ; @@ -1704,7 +1704,7 @@ sto:ServiceComposition rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:interoperability ; - ; + sto:hasStakeholder ; rdfs:comment "2 to n Data Apps/Devices/Services are connected"@en , "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)"@en ; rdfs:label "Service Composition"@en ; @@ -1737,7 +1737,7 @@ sto:ServiceDescription rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:SemanticInteroperability ; - ; + sto:hasStakeholder ; rdfs: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)"@en ; rdfs:label "Service Description"@en ; rdfs:seeAlso "IoT-A Requirement UNI.004" , @@ -1788,7 +1788,7 @@ sto:ServiceLevelAgreements rdf:type owl:NamedIndividual , ### https://w3id.org/i40/sto#ServiceLifecycleManagement sto:ServiceLifecycleManagement rdf:type owl:NamedIndividual , sto:Concern ; - ; + sto:hasStakeholder ; rdfs: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)"@en ; rdfs:label "Service life-cycle management"@en ; rdfs:seeAlso "IoT-A Requirement UNI.087" ; @@ -1800,7 +1800,7 @@ sto:ServiceOrchestration rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:ServiceComposition ; - ; + sto:hasStakeholder ; rdfs: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."@en ; rdfs:label "Service Orchestration"@en ; rdfs:seeAlso "IoT-A Requirement UNI.010" , @@ -1910,7 +1910,7 @@ sto:ThingDescription rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:SemanticInteroperability ; - , + sto:hasStakeholder , ; rdfs:comment "'Things' in terms of physical objects in the IoT need to be described in order to identify them and to provide further information."@en ; rdfs:label "Thing description"@en ; @@ -1952,7 +1952,7 @@ sto:TimeSynchronization rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:ServiceComposition ; - ; + sto:hasStakeholder ; rdfs:label "Time Synchronization"@en ; rdfs:seeAlso "IoT-A Requirement UNI.089" ; sto:hasDBpediaResource , @@ -1989,7 +1989,7 @@ sto:UnreliableNetwork rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:Reliability ; - "Developer"@en , + sto:hasStakeholder "Developer"@en , "System Architect"@en ; rdfs:comment "Productive systems must inherently cover issues caused by unreliable networks."@en ; rdfs:label "Unreliable Network"@en ; @@ -2006,7 +2006,7 @@ sto:UserInteraction rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:UserExperience ; - ; + sto:hasStakeholder ; rdfs: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)"@en ; rdfs:label "User Interaction"@en ; rdfs:seeAlso "IoT-A Requirement UNI.019" , @@ -2084,7 +2084,7 @@ sto:IPv6Support rdf:type owl:NamedIndividual , sto:Concern ; dcterms:creator sto:sebastian ; sto_iot:supports sto:SyntacticInteroperability ; - "System Architect"@en ; + sto:hasStakeholder "System Architect"@en ; rdfs:comment "A system built using the ARM shall use/support common-addressing-schemes such as IPv6."@en ; rdfs:label "IPv6 Support"@en ; rdfs:seeAlso "IoT-A Requirement UNI.312" ; diff --git a/sto.ttl b/sto.ttl index 49b3ce4..ccd9016 100644 --- a/sto.ttl +++ b/sto.ttl @@ -168,7 +168,10 @@ dcterms:title rdf:type owl:AnnotationProperty ; ### http://voag.linkedmodel.org/voag#hasStakeholder - rdf:type owl:AnnotationProperty . +sto:hasStakeholder rdf:type owl:AnnotationProperty; + rdfs:comment "realtes sto:concerns to the sto:StakeholderGroup that are associated with the concerns. "; + rdfs:label "hasStakeholder"@en. + ### http://www.w3.org/1999/02/22-rdf-syntax-ns#value @@ -5307,7 +5310,7 @@ sto:IEC_60870_P6_S802_E3 rdf:type owl:NamedIndividual , sto:hasStabilityDate "2019"^^xsd:gYear ; sto:hasTag "IEC 60870-6-802:2014"@en ; dcterms:title "Telecontrol equipment and systems - Part 6-802: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - TASE.2 Object models"@en ; - rdfs:comment "IEC 60870-6-802:2014 specifies a method of exchanging time-critical control centre data through wide-area and local-area networks using a full ISO compliant protocol stack. It contains provisions for supporting both centralized and distributed architectures. The standard includes the exchange of real-time data indications, control operations, time series data, scheduling and accounting information, remote program control and event notification. This new edition includes the following significant technical changes with respect to the previous edition: -certain objects have been changed from informative to normative; - certain TASE.2 conformance blocks have been made out of scope."@en , + rdfs:comment "IEC 60870-6-802:2014 specifies a method of exchanging time-critical control centre data through wide-area and local-area networks using a full ISO compliant protocol stack. It contains provisions for supporting both centralized and distributed architectures. The standard includes the exchange of real-time data indications, control operations, time series data, scheduling and accounting information, remote program control and event notification. This new edition includes the following significant technical changes with respect to the previous edition: -certain objects have been changed from informative to normative; - certain TASE.2 conformance blocks have been made out of scope."@en ; rdfs:label "IEC 60870-6-802:2014"@en ; sto:hasDBpediaResource ; sto:hasOfficialResource ; @@ -9791,7 +9794,6 @@ sto:NIST_500-291 rdf:type owl:NamedIndividual , dcterms:creator sto:irlan ; sto:hasClassification sto:IIRASecurity ; sto:hasPublisher sto:NIST ; - sto:hasDomain sto:hasPublicationDate "2011-08-10"^^xsd:date ; dcterms:title "NIST Cloud Computing Standards Roadmap"@en ; rdfs:comment "The NIST Cloud Computing Standards Roadmap Working Group has surveyed the existing standards landscape for security, portability, and interoperability standards/models/studies/use cases, etc., relevant to cloud computing. Using this available information, current standards, standards gaps, and standardization priorities are identified in this document. The NIST Definition of Cloud Computing identified cloud computing as a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction."@en ; @@ -11244,10 +11246,18 @@ sto:uIP rdf:type owl:NamedIndividual , ### https://www.wikidata.org/wiki/Q1548249 rdf:type owl:NamedIndividual , - ; + sto:StakeholderGroup ; rdfs:label "System Architect"@en . + + +sto:StakeholderGroup a owl:Class ; + rdfs:label "StakeholderGroup"@en ; + rdfs:comment "Stakeholder (Stakeholder Group) is an individual, organisation, or classses thereof, having an interest in a system."@en; + rdfs:isDefinedBy sto:IEC_42010; + sto:hasWikipediaArticle . + ################################################################# # Annotations #################################################################