Conformance results between oneM2M requirements and the SSN ontology.
The following table lists the oneM2M ontology requirements and whether the SSN ontology satisfies them.
There are four possible results for each requirement:
| Identifier | Category | Competency Question | Result |
|---|---|---|---|
| oneM2M-1 | Thing | A thing is an entity that can be identified in the oneM2M System. | Undefined |
| oneM2M-2 | Thing | A thing may have properties | Undefined |
| oneM2M-3 | Thing | A thing can have relations to other things | Undefined |
| oneM2M-4 | Aspect | An aspect could be a (physical or non-physical) entity or it could be a quality | Undefined |
| oneM2M-5 | Aspect | An aspect can have metadata | Undefined |
| oneM2M-6 | Metadata | Metadata contain data (like units, precision-ranges) about a variable or about an aspect | Undefined |
| oneM2M-7 | Device Network | A device is a thing that is able to interact electronically with its environment via a network | Undefined |
| oneM2M-8 | Device | A device may be a physical or non-physical entity | Undefined |
| oneM2M-9 | Device Task | A device performs one or more functionalities in order to accomplish a particular task | Undefined |
| oneM2M-10 | Device Service | A device has one or more services that expose in the network its functionalities | Undefined |
| oneM2M-11 | Device | A device can be composed of several (sub-)devices | Undefined |
| oneM2M-12 | Accessibility | An interworked device is a device that does not support oneM2M interfaces and can only be accessed from the oneM2M System by communicating with a proxied (virtual) device that has been created by an interworking proxy entity | Undefined |
| oneM2M-13 | Accessibility Communication Protocol | An interworked device is part of an area network | Undefined |
| oneM2M-14 | Accessibility | An area network is a network that provides data transport services between an interworked device and the oneM2M System | Undefined |
| oneM2M-15 | Accessibility | An area network follows an standard that defines its physical properties | Undefined |
| oneM2M-16 | Accessibility Communication Protocol | An area network follows a communication protocol | Undefined |
| oneM2M-17 | Profile Accessibility | An area network follows a profile | Undefined |
| oneM2M-18 | Service Function | A service is an electronic representation of a functionality in a network | Undefined |
| oneM2M-19 | Service Function | A service can expose one or more functionalities | Undefined |
| oneM2M-20 | Service | A service can be composed of independent (sub-)services | Undefined |
| oneM2M-21 | Service | A service has an operation | Undefined |
| oneM2M-22 | Service | A service has an input data point | Undefined |
| oneM2M-23 | Service | A service has an output data point | Undefined |
| oneM2M-24 | Function Task | A functionality represents the functionality necessary to accomplish the task for which a device is designed | Undefined |
| oneM2M-25 | Function User | A functionality has commands that allow human users to influence/observe such functionality | Undefined |
| oneM2M-26 | Function | A controlling functionality represents a functionality that has impacts on the real world, but does not gather data | Undefined |
| oneM2M-27 | Function | A measuring functionality represents a functionality that has no impacts on the real world, but only gathers data | Undefined |
| oneM2M-28 | Operation | An operation is the means of a service to communicate in a procedure-type manner over the network (i.e. transmit data to/from other devices) | Undefined |
| oneM2M-29 | Operation | An operation is the -machine interpretable- exposure of a -human understandable- command to a network | Undefined |
| oneM2M-30 | Operation | An operation may receive input data from input data points (persistent entities) | Undefined |
| oneM2M-31 | Operation | An operation may receive data from operation inputs (transient entities that are deleted when the operation finishes) | Undefined |
| oneM2M-32 | Operation | An operation may produce output data into output data points (persistent entities) | Undefined |
| oneM2M-33 | Operation | An operation may produce data into operation outputs (transient entities that are deleted when the operation finishes) | Undefined |
The following table lists the terms that are defined in the oneM2M and in the SSN ontology.
| Term in oneM2M | Term in SSN |
|---|
The following table summarises the metrics related to the conformance between the oneM2M requirements and the SSN ontology
| Metric | Result |
|---|---|
| Percentage of covered requirement | 0% |
| Percentage of requirements with terms that are undefined in the oneM2M ontology | 100% |
| Percantge of requirements that lead to conflict between the SSN and the oneM2M ontology | 0% |