Commit 3173ef00e91358e1c1516247ab4b7da1fa01cfe7

Authored by Joerg Swetina
1 parent 15cd2fdb

Replacing base_ontology.owl with version 3_0_0

Showing 1 changed file with 47 additions and 100 deletions
... ... @@ -19,6 +19,7 @@
19 19 xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
20 20 <Ontology rdf:about="http://www.onem2m.org/ontology/Base_Ontology/base_ontology">
21 21 <rdfs:comment>This file contains the Base Ontology of oneM2M as specified in TS-0012
  22 +This version 3_0_0 of the oneM2M Base Ontology is identical to version 2_1_0
22 23  
23 24 =========================================
24 25 Copyright Notification
... ... @@ -38,7 +39,7 @@ NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURA
38 39 NO oneM2M PARTNER TYPE 1 SHALL BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR ON SEQUENTIAL DAMAGES.
39 40 oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER.
40 41 =========================================</rdfs:comment>
41   - <versionIRI rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology-v2_2_0"/>
  42 + <versionIRI rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology-v3_0_0"/>
42 43 </Ontology>
43 44  
44 45  
... ... @@ -105,11 +106,11 @@ oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PR
105 106  
106 107  
107 108  
108   - <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#exposesFunction -->
  109 + <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#exposesFunctionality -->
109 110  
110   - <ObjectProperty rdf:about="&base_ontology;exposesFunction">
  111 + <ObjectProperty rdf:about="&base_ontology;exposesFunctionality">
111 112 <rdfs:comment>A Service exposes a Functionality to the network and makes it discoverable, registerable and remotely controllable in the network</rdfs:comment>
112   - <rdfs:range rdf:resource="&base_ontology;Function"/>
  113 + <rdfs:range rdf:resource="&base_ontology;Functionality"/>
113 114 <rdfs:domain rdf:resource="&base_ontology;Service"/>
114 115 </ObjectProperty>
115 116  
... ... @@ -120,17 +121,17 @@ oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PR
120 121 <ObjectProperty rdf:about="&base_ontology;hasCommand">
121 122 <rdfs:comment>A Functionality of a Device can be influenced / observed by a human user through the Commands that this Functionality has and that are offered to the user</rdfs:comment>
122 123 <rdfs:range rdf:resource="&base_ontology;Command"/>
123   - <rdfs:domain rdf:resource="&base_ontology;Function"/>
  124 + <rdfs:domain rdf:resource="&base_ontology;Functionality"/>
124 125 </ObjectProperty>
125 126  
126 127  
127 128  
128   - <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasFunction -->
  129 + <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasFunctionality -->
129 130  
130   - <ObjectProperty rdf:about="&base_ontology;hasFunction">
  131 + <ObjectProperty rdf:about="&base_ontology;hasFunctionality">
131 132 <rdfs:comment>In order to accomplish its task, a Device performs one or more Functionalities</rdfs:comment>
132 133 <rdfs:domain rdf:resource="&base_ontology;Device"/>
133   - <rdfs:range rdf:resource="&base_ontology;Function"/>
  134 + <rdfs:range rdf:resource="&base_ontology;Functionality"/>
134 135 </ObjectProperty>
135 136  
136 137  
... ... @@ -157,9 +158,6 @@ oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PR
157 158 <ObjectProperty rdf:about="&base_ontology;hasInputDataPoint">
158 159 <rdfs:comment>A Service or an Operation of a Service of the Device can have InputDataPoints. Communicating entities write data into InputDataPoints and the Device retrieves the data at times according to an internal schedule.
159 160 - An InputDataPoint is a persistent resource</rdfs:comment>
160   - <rdfs:comment>Note:
161   -If an InputDataPoint is mandatory for a Service or Operation then
162   -the cardinality of hasInputDataPoint must be - min 1.</rdfs:comment>
163 161 <rdfs:range rdf:resource="&base_ontology;InputDataPoint"/>
164 162 <rdfs:domain>
165 163 <Class>
... ... @@ -193,9 +191,6 @@ the cardinality of hasInputDataPoint must be - min 1.&lt;/rdfs:comment&gt;
193 191 <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasOperation -->
194 192  
195 193 <ObjectProperty rdf:about="&base_ontology;hasOperation">
196   - <rdfs:comment>Note:
197   -If an Operation is mandatory for a Service then
198   -the cardinality of hasOperation must be - min 1.</rdfs:comment>
199 194 <rdfs:comment>A Service communicates by means of Operations over the network to transmit data to/from other devices</rdfs:comment>
200 195 <rdfs:range rdf:resource="&base_ontology;Operation"/>
201 196 <rdfs:domain rdf:resource="&base_ontology;Service"/>
... ... @@ -233,9 +228,6 @@ the cardinality of hasOperation must be - min 1.&lt;/rdfs:comment&gt;
233 228 <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasOutputDataPoint -->
234 229  
235 230 <ObjectProperty rdf:about="&base_ontology;hasOutputDataPoint">
236   - <rdfs:comment>Note:
237   -If an OutputDataPoint is mandatory for a Service or Operation then
238   -the cardinality of hasOutputDataPoint must be - min 1.</rdfs:comment>
239 231 <rdfs:comment>A Service or an Operation of a Service of the Device can have OutputDataPoints. The Device writes data into OutputDataPoints at times according to an internal schedule and the communicating entitis retrieves the data.
240 232 - An OutputDataPoint is a persistent resource</rdfs:comment>
241 233 <rdfs:range rdf:resource="&base_ontology;OutputDataPoint"/>
... ... @@ -265,9 +257,6 @@ the cardinality of hasOutputDataPoint must be - min 1.&lt;/rdfs:comment&gt;
265 257  
266 258 <ObjectProperty rdf:about="&base_ontology;hasSubService">
267 259 <rdfs:comment>A Service may be composed of smaller, independent (sub)Services, e.g. re-usable servicemodules</rdfs:comment>
268   - <rdfs:comment>Note:
269   -If an Service constist of at least one sub-Service then
270   -the cardinality of hasSubService must be - min 1.</rdfs:comment>
271 260 <rdfs:domain rdf:resource="&base_ontology;Service"/>
272 261 <rdfs:range rdf:resource="&base_ontology;Service"/>
273 262 </ObjectProperty>
... ... @@ -320,7 +309,7 @@ the cardinality of hasSubService must be - min 1.&lt;/rdfs:comment&gt;
320 309 <rdfs:isDefinedBy>A Functionality of a Device can refer to a certain Aspect (a quality or kind) that is measured or controlled by that Functionality.
321 310 e.g. a temperature sensor would refer to the Aspect &quot;Temperature&quot; that it measures</rdfs:isDefinedBy>
322 311 <rdfs:range rdf:resource="&base_ontology;Aspect"/>
323   - <rdfs:domain rdf:resource="&base_ontology;Function"/>
  312 + <rdfs:domain rdf:resource="&base_ontology;Functionality"/>
324 313 </ObjectProperty>
325 314  
326 315  
... ... @@ -619,18 +608,6 @@ The Data Property &amp;quot;hasDataRestriction&amp;quot; shall always be sub-classed&lt;/rd
619 608  
620 609  
621 610  
622   - <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasThingAnnotation -->
623   -
624   - <DatatypeProperty rdf:about="&base_ontology;hasThingAnnotation">
625   - <rdfs:comment>This data property contains a description of a Thing.
626   -Note: Data Property: hasThingAnnotation should be used in cases where the annotation data do not change very often and/or where they are usually not the subject of semantic operations (e.g. semantic discovery). Otherwise Object Propety: hasThingPropery should be used
627   -E.g. a certain type of Device could have the model (as a numeric description) or the name of the manufacturer (as a textual annotation)</rdfs:comment>
628   - <rdfs:domain rdf:resource="&base_ontology;Thing"/>
629   - <rdfs:range rdf:resource="&rdfs;Literal"/>
630   - </DatatypeProperty>
631   -
632   -
633   -
634 611 <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasValue -->
635 612  
636 613 <DatatypeProperty rdf:about="&base_ontology;hasValue">
... ... @@ -762,8 +739,8 @@ The Aspect could be a (physical or non-physical) entity or it could be a quality
762 739 </rdfs:subClassOf>
763 740 <rdfs:subClassOf>
764 741 <Restriction>
765   - <onProperty rdf:resource="&base_ontology;hasInput"/>
766   - <allValuesFrom rdf:resource="&base_ontology;OperationInput"/>
  742 + <onProperty rdf:resource="&base_ontology;hasInputDataPoint"/>
  743 + <allValuesFrom rdf:resource="&base_ontology;InputDataPoint"/>
767 744 </Restriction>
768 745 </rdfs:subClassOf>
769 746 <rdfs:subClassOf>
... ... @@ -774,8 +751,8 @@ The Aspect could be a (physical or non-physical) entity or it could be a quality
774 751 </rdfs:subClassOf>
775 752 <rdfs:subClassOf>
776 753 <Restriction>
777   - <onProperty rdf:resource="&base_ontology;hasInputDataPoint"/>
778   - <allValuesFrom rdf:resource="&base_ontology;InputDataPoint"/>
  754 + <onProperty rdf:resource="&base_ontology;hasInput"/>
  755 + <allValuesFrom rdf:resource="&base_ontology;OperationInput"/>
779 756 </Restriction>
780 757 </rdfs:subClassOf>
781 758 <rdfs:comment>A Command (Class: Command) represents an action that can be performed to support the Functionality. A Command is the human understandable name of that action that is invoked in a device or is reported by the device. An Operation exposes a Command to the network. OperationInput and OperationOutput of the related Operation can parameterize the command.
... ... @@ -787,10 +764,10 @@ Note: In RESTful systems the names of Input- and OutputDataPoints are usually ch
787 764  
788 765  
789 766  
790   - <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#ControllingFunction -->
  767 + <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#ControllingFunctionality -->
791 768  
792   - <Class rdf:about="&base_ontology;ControllingFunction">
793   - <rdfs:subClassOf rdf:resource="&base_ontology;Function"/>
  769 + <Class rdf:about="&base_ontology;ControllingFunctionality">
  770 + <rdfs:subClassOf rdf:resource="&base_ontology;Functionality"/>
794 771 <rdfs:comment>A ControllingFunctionality (Class: ControllingFunctionality) represents a functionality that has impacts on the real world, but does not gather data. In general a ControllingFunctionality has Commands (and/or Operations of its related Services) that receives Input data
795 772 E.g. a thermostat would have &quot;temperature-adjustment&quot; as a ControllingFunctionality</rdfs:comment>
796 773 </Class>
... ... @@ -803,21 +780,22 @@ E.g. a thermostat would have &amp;quot;temperature-adjustment&amp;quot; as a Controlling
803 780 <rdfs:subClassOf rdf:resource="&base_ontology;Thing"/>
804 781 <rdfs:subClassOf>
805 782 <Restriction>
806   - <onProperty rdf:resource="&base_ontology;hasService"/>
807   - <allValuesFrom rdf:resource="&base_ontology;Service"/>
  783 + <onProperty rdf:resource="&base_ontology;consistsOf"/>
  784 + <allValuesFrom rdf:resource="&base_ontology;Device"/>
808 785 </Restriction>
809 786 </rdfs:subClassOf>
810 787 <rdfs:subClassOf>
811 788 <Restriction>
812   - <onProperty rdf:resource="&base_ontology;hasFunction"/>
813   - <onClass rdf:resource="&base_ontology;Function"/>
  789 + <onProperty rdf:resource="&base_ontology;hasService"/>
  790 + <onClass rdf:resource="&base_ontology;Service"/>
814 791 <minQualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">1</minQualifiedCardinality>
815 792 </Restriction>
816 793 </rdfs:subClassOf>
817 794 <rdfs:subClassOf>
818 795 <Restriction>
819   - <onProperty rdf:resource="&base_ontology;consistsOf"/>
820   - <allValuesFrom rdf:resource="&base_ontology;Device"/>
  796 + <onProperty rdf:resource="&base_ontology;hasFunctionality"/>
  797 + <onClass rdf:resource="&base_ontology;Functionality"/>
  798 + <minQualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">1</minQualifiedCardinality>
821 799 </Restriction>
822 800 </rdfs:subClassOf>
823 801 <rdfs:comment>A Device (Class: Device) is a object designed to accomplish a particular task. A Device contains some logic and is producer and/or consumer of data that are exchanged via its Services with other oneM2M entities (Devices, Things) in the network. A Device may be a physical or non-physical entity.
... ... @@ -830,9 +808,9 @@ In the context of oneM2M a Device is always assumed to be capable of communicati
830 808  
831 809  
832 810  
833   - <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#Function -->
  811 + <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#Functionality -->
834 812  
835   - <Class rdf:about="&base_ontology;Function">
  813 + <Class rdf:about="&base_ontology;Functionality">
836 814 <priorVersion>A Functionality (Class: Functionality) represents the functionality necessary to accomplish the task for which a Device is designed. A device can be designed to perform more than one functionality.
837 815 The functionality exhibits the – human understandable – meaning what the device &quot;does&quot;.
838 816 A Functionality refers to (e.g. observes or influences) some real-world aspect(s), that can be modelled as a Class: Aspect.
... ... @@ -862,10 +840,10 @@ To enable a third party to instruct the device to retrieve (out of schedule) the
862 840  
863 841  
864 842  
865   - <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#MeasuringFunction -->
  843 + <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#MeasuringFunctionality -->
866 844  
867   - <Class rdf:about="&base_ontology;MeasuringFunction">
868   - <rdfs:subClassOf rdf:resource="&base_ontology;Function"/>
  845 + <Class rdf:about="&base_ontology;MeasuringFunctionality">
  846 + <rdfs:subClassOf rdf:resource="&base_ontology;Functionality"/>
869 847 <rdfs:comment>A MeasuringFunctionality (Class: MeasuringFunctionality) represents a functionality that has no impacts on the real world, but only gathers data. In general a MeasuringFunctionality has Commands (and/or Operations of its related Services) that generate Output data
870 848 E.g. a temperature sensor would have &quot;temperature-sensing&quot; as a MeasuringFunctionality</rdfs:comment>
871 849 </Class>
... ... @@ -887,13 +865,13 @@ E.g. the indoor temperature could have meta data: &amp;quot;Degrees Celsius&amp;quot;&lt;/r
887 865 <rdfs:subClassOf>
888 866 <Restriction>
889 867 <onProperty rdf:resource="&base_ontology;exposesCommand"/>
890   - <allValuesFrom rdf:resource="&base_ontology;Command"/>
  868 + <someValuesFrom rdf:resource="&base_ontology;Command"/>
891 869 </Restriction>
892 870 </rdfs:subClassOf>
893 871 <rdfs:subClassOf>
894 872 <Restriction>
895   - <onProperty rdf:resource="&base_ontology;hasInput"/>
896   - <allValuesFrom rdf:resource="&base_ontology;OperationInput"/>
  873 + <onProperty rdf:resource="&base_ontology;hasOperationState"/>
  874 + <allValuesFrom rdf:resource="&base_ontology;OperationState"/>
897 875 </Restriction>
898 876 </rdfs:subClassOf>
899 877 <rdfs:subClassOf>
... ... @@ -904,8 +882,8 @@ E.g. the indoor temperature could have meta data: &amp;quot;Degrees Celsius&amp;quot;&lt;/r
904 882 </rdfs:subClassOf>
905 883 <rdfs:subClassOf>
906 884 <Restriction>
907   - <onProperty rdf:resource="&base_ontology;hasOperationState"/>
908   - <allValuesFrom rdf:resource="&base_ontology;OperationState"/>
  885 + <onProperty rdf:resource="&base_ontology;hasInput"/>
  886 + <allValuesFrom rdf:resource="&base_ontology;OperationInput"/>
909 887 </Restriction>
910 888 </rdfs:subClassOf>
911 889 <rdfs:comment>An Operation (Class: 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). It is the –machine interpretable- exposure of a –human understandable- Command to a network.
... ... @@ -946,13 +924,6 @@ An Operation correlates the output data of the Operation to the input data that
946 924 <rdfs:subClassOf rdf:resource="&base_ontology;SimpleTypeVariable"/>
947 925 <rdfs:subClassOf>
948 926 <Restriction>
949   - <onProperty rdf:resource="&base_ontology;hasDataRestriction_pattern"/>
950   - <qualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">1</qualifiedCardinality>
951   - <onDataRange rdf:resource="&xsd;string"/>
952   - </Restriction>
953   - </rdfs:subClassOf>
954   - <rdfs:subClassOf>
955   - <Restriction>
956 927 <onProperty rdf:resource="&base_ontology;hasDataType"/>
957 928 <qualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">1</qualifiedCardinality>
958 929 <onDataRange rdf:resource="&xsd;string"/>
... ... @@ -980,6 +951,13 @@ An Operation correlates the output data of the Operation to the input data that
980 951 </unionOf>
981 952 </Class>
982 953 </rdfs:subClassOf>
  954 + <rdfs:subClassOf>
  955 + <Restriction>
  956 + <onProperty rdf:resource="&base_ontology;hasDataRestriction_pattern"/>
  957 + <qualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">1</qualifiedCardinality>
  958 + <onDataRange rdf:resource="&xsd;string"/>
  959 + </Restriction>
  960 + </rdfs:subClassOf>
983 961 <rdfs:comment>describes the current state during the lifetime of an Operation. The OperationState class represents all possible values for that state (enumerated individuals). The OperationState is set during the progress of the operation by the entity invoking the operation, the entity that is the target of the operation, e.g. a device (or for interworked devices by the IPE) and the CSE. It takes values like
984 962 &quot;data_received_by_application&quot;, &quot;operation_ended&quot;, &quot;operation_failed&quot;, &quot;data_transmitted_to_interworked_device&quot;.</rdfs:comment>
985 963 </Class>
... ... @@ -1000,20 +978,20 @@ An Operation correlates the output data of the Operation to the input data that
1000 978 <Class rdf:about="&base_ontology;Service">
1001 979 <rdfs:subClassOf>
1002 980 <Restriction>
1003   - <onProperty rdf:resource="&base_ontology;hasInputDataPoint"/>
1004   - <allValuesFrom rdf:resource="&base_ontology;InputDataPoint"/>
  981 + <onProperty rdf:resource="&base_ontology;hasOperation"/>
  982 + <allValuesFrom rdf:resource="&base_ontology;Operation"/>
1005 983 </Restriction>
1006 984 </rdfs:subClassOf>
1007 985 <rdfs:subClassOf>
1008 986 <Restriction>
1009   - <onProperty rdf:resource="&base_ontology;hasSubService"/>
1010   - <allValuesFrom rdf:resource="&base_ontology;Service"/>
  987 + <onProperty rdf:resource="&base_ontology;exposesFunctionality"/>
  988 + <someValuesFrom rdf:resource="&base_ontology;Functionality"/>
1011 989 </Restriction>
1012 990 </rdfs:subClassOf>
1013 991 <rdfs:subClassOf>
1014 992 <Restriction>
1015   - <onProperty rdf:resource="&base_ontology;exposesFunction"/>
1016   - <someValuesFrom rdf:resource="&base_ontology;Function"/>
  993 + <onProperty rdf:resource="&base_ontology;hasInputDataPoint"/>
  994 + <allValuesFrom rdf:resource="&base_ontology;InputDataPoint"/>
1017 995 </Restriction>
1018 996 </rdfs:subClassOf>
1019 997 <rdfs:subClassOf>
... ... @@ -1022,12 +1000,6 @@ An Operation correlates the output data of the Operation to the input data that
1022 1000 <allValuesFrom rdf:resource="&base_ontology;OutputDataPoint"/>
1023 1001 </Restriction>
1024 1002 </rdfs:subClassOf>
1025   - <rdfs:subClassOf>
1026   - <Restriction>
1027   - <onProperty rdf:resource="&base_ontology;hasOperation"/>
1028   - <allValuesFrom rdf:resource="&base_ontology;Operation"/>
1029   - </Restriction>
1030   - </rdfs:subClassOf>
1031 1003 <rdfs:comment>A Service (Class: Service) is a electronic representation of a Functionality in a network. The Service exposes the Functionality to the network and makes it discoverable, registerable and remotely controllable in the network.
1032 1004 A Service is offered by a device that wants (a certain set of) its Functionalities to be discoverable, registerable, remotely controllable by other devices in the network.
1033 1005 A Service can expose one or more Functionalities and a Functionality can be exposed by one or more Services.
... ... @@ -1043,19 +1015,6 @@ NOTE: While a Functionality describes the – human understandable – meaning
1043 1015 <rdfs:subClassOf rdf:resource="&base_ontology;Variable"/>
1044 1016 <rdfs:subClassOf>
1045 1017 <Restriction>
1046   - <onProperty rdf:resource="&base_ontology;hasDataRestriction"/>
1047   - <allValuesFrom rdf:resource="&rdf;PlainLiteral"/>
1048   - </Restriction>
1049   - </rdfs:subClassOf>
1050   - <rdfs:subClassOf>
1051   - <Restriction>
1052   - <onProperty rdf:resource="&base_ontology;hasSubStructure"/>
1053   - <onClass rdf:resource="&base_ontology;Variable"/>
1054   - <qualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">0</qualifiedCardinality>
1055   - </Restriction>
1056   - </rdfs:subClassOf>
1057   - <rdfs:subClassOf>
1058   - <Restriction>
1059 1018 <onProperty rdf:resource="&base_ontology;hasDataType"/>
1060 1019 <qualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">1</qualifiedCardinality>
1061 1020 <onDataRange rdf:resource="&rdf;PlainLiteral"/>
... ... @@ -1077,12 +1036,6 @@ The simple datatypes and –restrictions contained in &amp;quot;OWL 2 Web Ontology L
1077 1036 <allValuesFrom rdf:resource="&base_ontology;Thing"/>
1078 1037 </Restriction>
1079 1038 </rdfs:subClassOf>
1080   - <rdfs:subClassOf>
1081   - <Restriction>
1082   - <onProperty rdf:resource="&base_ontology;hasThingProperty"/>
1083   - <allValuesFrom rdf:resource="&base_ontology;ThingProperty"/>
1084   - </Restriction>
1085   - </rdfs:subClassOf>
1086 1039 <rdfs:comment>A Thing in oneM2M (Class: Thing) is an entity that can be identified in the oneM2M System.
1087 1040 A Thing that is not a Device is not able to conmmunicate electronically with its environment. However, the sub-class of Thing that is able to interact electronically is called a &quot;Device&quot;.
1088 1041 A Thing may have ThingProperties (Object Property: hasThingProperty). A Thing can have relations to other things (Object Property: hasThingRelation).
... ... @@ -1108,12 +1061,6 @@ A Value of a Thing can have meta data&lt;/rdfs:comment&gt;
1108 1061 <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#Variable -->
1109 1062  
1110 1063 <Class rdf:about="&base_ontology;Variable">
1111   - <rdfs:subClassOf>
1112   - <Restriction>
1113   - <onProperty rdf:resource="&base_ontology;hasSubStructure"/>
1114   - <allValuesFrom rdf:resource="&base_ontology;Variable"/>
1115   - </Restriction>
1116   - </rdfs:subClassOf>
1117 1064 <rdfs:comment>A Variable (Class: Variable) constitutes a super class to the following classes: ThingProperty, OperationInput, OperationOutput, OperationState, InputDataPoint, OutputDataPoint, SimpleTypeVariable. Its members are entities that store some data (e.g. integers, text, or structured data) that can change over time.
1118 1065 These data of the Variable usually describe some real-world Aspects (e.g. a temperature) and can have MetaData (e.g. units, precision..)</rdfs:comment>
1119 1066 </Class>
... ...