Commit 45b20cb11c0c6c818b28fb6ec87074a2cac6b2b0

Authored by Joerg Swetina
1 parent 69d9b6b8

uploading version 3.1.0

Showing 1 changed file with 105 additions and 52 deletions
... ... @@ -19,7 +19,6 @@
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
23 22  
24 23 =========================================
25 24 Copyright Notification
... ... @@ -39,7 +38,7 @@ NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURA
39 38 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.
40 39 oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER.
41 40 =========================================</rdfs:comment>
42   - <versionIRI rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology-v3_0_0"/>
  41 + <versionIRI rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology-v3_1_0"/>
43 42 </Ontology>
44 43  
45 44  
... ... @@ -106,11 +105,11 @@ oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PR
106 105  
107 106  
108 107  
109   - <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#exposesFunctionality -->
  108 + <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#exposesFunction -->
110 109  
111   - <ObjectProperty rdf:about="&base_ontology;exposesFunctionality">
  110 + <ObjectProperty rdf:about="&base_ontology;exposesFunction">
112 111 <rdfs:comment>A Service exposes a Functionality to the network and makes it discoverable, registerable and remotely controllable in the network</rdfs:comment>
113   - <rdfs:range rdf:resource="&base_ontology;Functionality"/>
  112 + <rdfs:range rdf:resource="&base_ontology;Function"/>
114 113 <rdfs:domain rdf:resource="&base_ontology;Service"/>
115 114 </ObjectProperty>
116 115  
... ... @@ -121,17 +120,17 @@ oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PR
121 120 <ObjectProperty rdf:about="&base_ontology;hasCommand">
122 121 <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>
123 122 <rdfs:range rdf:resource="&base_ontology;Command"/>
124   - <rdfs:domain rdf:resource="&base_ontology;Functionality"/>
  123 + <rdfs:domain rdf:resource="&base_ontology;Function"/>
125 124 </ObjectProperty>
126 125  
127 126  
128 127  
129   - <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasFunctionality -->
  128 + <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasFunction -->
130 129  
131   - <ObjectProperty rdf:about="&base_ontology;hasFunctionality">
  130 + <ObjectProperty rdf:about="&base_ontology;hasFunction">
132 131 <rdfs:comment>In order to accomplish its task, a Device performs one or more Functionalities</rdfs:comment>
133 132 <rdfs:domain rdf:resource="&base_ontology;Device"/>
134   - <rdfs:range rdf:resource="&base_ontology;Functionality"/>
  133 + <rdfs:range rdf:resource="&base_ontology;Function"/>
135 134 </ObjectProperty>
136 135  
137 136  
... ... @@ -158,6 +157,9 @@ oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PR
158 157 <ObjectProperty rdf:about="&base_ontology;hasInputDataPoint">
159 158 <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.
160 159 - 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>
161 163 <rdfs:range rdf:resource="&base_ontology;InputDataPoint"/>
162 164 <rdfs:domain>
163 165 <Class>
... ... @@ -191,6 +193,9 @@ oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PR
191 193 <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasOperation -->
192 194  
193 195 <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>
194 199 <rdfs:comment>A Service communicates by means of Operations over the network to transmit data to/from other devices</rdfs:comment>
195 200 <rdfs:range rdf:resource="&base_ontology;Operation"/>
196 201 <rdfs:domain rdf:resource="&base_ontology;Service"/>
... ... @@ -228,6 +233,9 @@ oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PR
228 233 <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasOutputDataPoint -->
229 234  
230 235 <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>
231 239 <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.
232 240 - An OutputDataPoint is a persistent resource</rdfs:comment>
233 241 <rdfs:range rdf:resource="&base_ontology;OutputDataPoint"/>
... ... @@ -257,6 +265,9 @@ oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PR
257 265  
258 266 <ObjectProperty rdf:about="&base_ontology;hasSubService">
259 267 <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>
260 271 <rdfs:domain rdf:resource="&base_ontology;Service"/>
261 272 <rdfs:range rdf:resource="&base_ontology;Service"/>
262 273 </ObjectProperty>
... ... @@ -309,7 +320,7 @@ oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PR
309 320 <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.
310 321 e.g. a temperature sensor would refer to the Aspect &quot;Temperature&quot; that it measures</rdfs:isDefinedBy>
311 322 <rdfs:range rdf:resource="&base_ontology;Aspect"/>
312   - <rdfs:domain rdf:resource="&base_ontology;Functionality"/>
  323 + <rdfs:domain rdf:resource="&base_ontology;Function"/>
313 324 </ObjectProperty>
314 325  
315 326  
... ... @@ -608,6 +619,18 @@ The Data Property &amp;quot;hasDataRestriction&amp;quot; shall always be sub-classed&lt;/rd
608 619  
609 620  
610 621  
  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 +
611 634 <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasValue -->
612 635  
613 636 <DatatypeProperty rdf:about="&base_ontology;hasValue">
... ... @@ -733,26 +756,26 @@ The Aspect could be a (physical or non-physical) entity or it could be a quality
733 756 <Class rdf:about="&base_ontology;Command">
734 757 <rdfs:subClassOf>
735 758 <Restriction>
736   - <onProperty rdf:resource="&base_ontology;hasOutput"/>
737   - <allValuesFrom rdf:resource="&base_ontology;OperationOutput"/>
  759 + <onProperty rdf:resource="&base_ontology;hasOutputDataPoint"/>
  760 + <allValuesFrom rdf:resource="&base_ontology;OutputDataPoint"/>
738 761 </Restriction>
739 762 </rdfs:subClassOf>
740 763 <rdfs:subClassOf>
741 764 <Restriction>
742   - <onProperty rdf:resource="&base_ontology;hasInputDataPoint"/>
743   - <allValuesFrom rdf:resource="&base_ontology;InputDataPoint"/>
  765 + <onProperty rdf:resource="&base_ontology;hasOutput"/>
  766 + <allValuesFrom rdf:resource="&base_ontology;OperationOutput"/>
744 767 </Restriction>
745 768 </rdfs:subClassOf>
746 769 <rdfs:subClassOf>
747 770 <Restriction>
748   - <onProperty rdf:resource="&base_ontology;hasOutputDataPoint"/>
749   - <allValuesFrom rdf:resource="&base_ontology;OutputDataPoint"/>
  771 + <onProperty rdf:resource="&base_ontology;hasInput"/>
  772 + <allValuesFrom rdf:resource="&base_ontology;OperationInput"/>
750 773 </Restriction>
751 774 </rdfs:subClassOf>
752 775 <rdfs:subClassOf>
753 776 <Restriction>
754   - <onProperty rdf:resource="&base_ontology;hasInput"/>
755   - <allValuesFrom rdf:resource="&base_ontology;OperationInput"/>
  777 + <onProperty rdf:resource="&base_ontology;hasInputDataPoint"/>
  778 + <allValuesFrom rdf:resource="&base_ontology;InputDataPoint"/>
756 779 </Restriction>
757 780 </rdfs:subClassOf>
758 781 <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.
... ... @@ -764,10 +787,10 @@ Note: In RESTful systems the names of Input- and OutputDataPoints are usually ch
764 787  
765 788  
766 789  
767   - <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#ControllingFunctionality -->
  790 + <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#ControllingFunction -->
768 791  
769   - <Class rdf:about="&base_ontology;ControllingFunctionality">
770   - <rdfs:subClassOf rdf:resource="&base_ontology;Functionality"/>
  792 + <Class rdf:about="&base_ontology;ControllingFunction">
  793 + <rdfs:subClassOf rdf:resource="&base_ontology;Function"/>
771 794 <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
772 795 E.g. a thermostat would have &quot;temperature-adjustment&quot; as a ControllingFunctionality</rdfs:comment>
773 796 </Class>
... ... @@ -780,22 +803,21 @@ E.g. a thermostat would have &amp;quot;temperature-adjustment&amp;quot; as a Controlling
780 803 <rdfs:subClassOf rdf:resource="&base_ontology;Thing"/>
781 804 <rdfs:subClassOf>
782 805 <Restriction>
783   - <onProperty rdf:resource="&base_ontology;consistsOf"/>
784   - <allValuesFrom rdf:resource="&base_ontology;Device"/>
  806 + <onProperty rdf:resource="&base_ontology;hasService"/>
  807 + <allValuesFrom rdf:resource="&base_ontology;Service"/>
785 808 </Restriction>
786 809 </rdfs:subClassOf>
787 810 <rdfs:subClassOf>
788 811 <Restriction>
789   - <onProperty rdf:resource="&base_ontology;hasService"/>
790   - <onClass rdf:resource="&base_ontology;Service"/>
  812 + <onProperty rdf:resource="&base_ontology;hasFunction"/>
  813 + <onClass rdf:resource="&base_ontology;Function"/>
791 814 <minQualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">1</minQualifiedCardinality>
792 815 </Restriction>
793 816 </rdfs:subClassOf>
794 817 <rdfs:subClassOf>
795 818 <Restriction>
796   - <onProperty rdf:resource="&base_ontology;hasFunctionality"/>
797   - <onClass rdf:resource="&base_ontology;Functionality"/>
798   - <minQualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">1</minQualifiedCardinality>
  819 + <onProperty rdf:resource="&base_ontology;consistsOf"/>
  820 + <allValuesFrom rdf:resource="&base_ontology;Device"/>
799 821 </Restriction>
800 822 </rdfs:subClassOf>
801 823 <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.
... ... @@ -808,9 +830,9 @@ In the context of oneM2M a Device is always assumed to be capable of communicati
808 830  
809 831  
810 832  
811   - <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#Functionality -->
  833 + <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#Function -->
812 834  
813   - <Class rdf:about="&base_ontology;Functionality">
  835 + <Class rdf:about="&base_ontology;Function">
814 836 <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.
815 837 The functionality exhibits the – human understandable – meaning what the device &quot;does&quot;.
816 838 A Functionality refers to (e.g. observes or influences) some real-world aspect(s), that can be modelled as a Class: Aspect.
... ... @@ -840,10 +862,10 @@ To enable a third party to instruct the device to retrieve (out of schedule) the
840 862  
841 863  
842 864  
843   - <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#MeasuringFunctionality -->
  865 + <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#MeasuringFunction -->
844 866  
845   - <Class rdf:about="&base_ontology;MeasuringFunctionality">
846   - <rdfs:subClassOf rdf:resource="&base_ontology;Functionality"/>
  867 + <Class rdf:about="&base_ontology;MeasuringFunction">
  868 + <rdfs:subClassOf rdf:resource="&base_ontology;Function"/>
847 869 <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
848 870 E.g. a temperature sensor would have &quot;temperature-sensing&quot; as a MeasuringFunctionality</rdfs:comment>
849 871 </Class>
... ... @@ -864,8 +886,8 @@ E.g. the indoor temperature could have meta data: &amp;quot;Degrees Celsius&amp;quot;&lt;/r
864 886 <Class rdf:about="&base_ontology;Operation">
865 887 <rdfs:subClassOf>
866 888 <Restriction>
867   - <onProperty rdf:resource="&base_ontology;exposesCommand"/>
868   - <someValuesFrom rdf:resource="&base_ontology;Command"/>
  889 + <onProperty rdf:resource="&base_ontology;hasInput"/>
  890 + <allValuesFrom rdf:resource="&base_ontology;OperationInput"/>
869 891 </Restriction>
870 892 </rdfs:subClassOf>
871 893 <rdfs:subClassOf>
... ... @@ -876,14 +898,14 @@ E.g. the indoor temperature could have meta data: &amp;quot;Degrees Celsius&amp;quot;&lt;/r
876 898 </rdfs:subClassOf>
877 899 <rdfs:subClassOf>
878 900 <Restriction>
879   - <onProperty rdf:resource="&base_ontology;hasOutput"/>
880   - <allValuesFrom rdf:resource="&base_ontology;OperationOutput"/>
  901 + <onProperty rdf:resource="&base_ontology;exposesCommand"/>
  902 + <allValuesFrom rdf:resource="&base_ontology;Command"/>
881 903 </Restriction>
882 904 </rdfs:subClassOf>
883 905 <rdfs:subClassOf>
884 906 <Restriction>
885   - <onProperty rdf:resource="&base_ontology;hasInput"/>
886   - <allValuesFrom rdf:resource="&base_ontology;OperationInput"/>
  907 + <onProperty rdf:resource="&base_ontology;hasOutput"/>
  908 + <allValuesFrom rdf:resource="&base_ontology;OperationOutput"/>
887 909 </Restriction>
888 910 </rdfs:subClassOf>
889 911 <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.
... ... @@ -924,6 +946,13 @@ An Operation correlates the output data of the Operation to the input data that
924 946 <rdfs:subClassOf rdf:resource="&base_ontology;SimpleTypeVariable"/>
925 947 <rdfs:subClassOf>
926 948 <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>
927 956 <onProperty rdf:resource="&base_ontology;hasDataType"/>
928 957 <qualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">1</qualifiedCardinality>
929 958 <onDataRange rdf:resource="&xsd;string"/>
... ... @@ -951,13 +980,6 @@ An Operation correlates the output data of the Operation to the input data that
951 980 </unionOf>
952 981 </Class>
953 982 </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>
961 983 <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
962 984 &quot;data_received_by_application&quot;, &quot;operation_ended&quot;, &quot;operation_failed&quot;, &quot;data_transmitted_to_interworked_device&quot;.</rdfs:comment>
963 985 </Class>
... ... @@ -978,14 +1000,20 @@ An Operation correlates the output data of the Operation to the input data that
978 1000 <Class rdf:about="&base_ontology;Service">
979 1001 <rdfs:subClassOf>
980 1002 <Restriction>
981   - <onProperty rdf:resource="&base_ontology;hasOperation"/>
982   - <allValuesFrom rdf:resource="&base_ontology;Operation"/>
  1003 + <onProperty rdf:resource="&base_ontology;hasOutputDataPoint"/>
  1004 + <allValuesFrom rdf:resource="&base_ontology;OutputDataPoint"/>
983 1005 </Restriction>
984 1006 </rdfs:subClassOf>
985 1007 <rdfs:subClassOf>
986 1008 <Restriction>
987   - <onProperty rdf:resource="&base_ontology;exposesFunctionality"/>
988   - <someValuesFrom rdf:resource="&base_ontology;Functionality"/>
  1009 + <onProperty rdf:resource="&base_ontology;hasSubService"/>
  1010 + <allValuesFrom rdf:resource="&base_ontology;Service"/>
  1011 + </Restriction>
  1012 + </rdfs:subClassOf>
  1013 + <rdfs:subClassOf>
  1014 + <Restriction>
  1015 + <onProperty rdf:resource="&base_ontology;hasOperation"/>
  1016 + <allValuesFrom rdf:resource="&base_ontology;Operation"/>
989 1017 </Restriction>
990 1018 </rdfs:subClassOf>
991 1019 <rdfs:subClassOf>
... ... @@ -996,8 +1024,8 @@ An Operation correlates the output data of the Operation to the input data that
996 1024 </rdfs:subClassOf>
997 1025 <rdfs:subClassOf>
998 1026 <Restriction>
999   - <onProperty rdf:resource="&base_ontology;hasOutputDataPoint"/>
1000   - <allValuesFrom rdf:resource="&base_ontology;OutputDataPoint"/>
  1027 + <onProperty rdf:resource="&base_ontology;exposesFunction"/>
  1028 + <someValuesFrom rdf:resource="&base_ontology;Function"/>
1001 1029 </Restriction>
1002 1030 </rdfs:subClassOf>
1003 1031 <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.
... ... @@ -1020,6 +1048,19 @@ NOTE: While a Functionality describes the – human understandable – meaning
1020 1048 <onDataRange rdf:resource="&rdf;PlainLiteral"/>
1021 1049 </Restriction>
1022 1050 </rdfs:subClassOf>
  1051 + <rdfs:subClassOf>
  1052 + <Restriction>
  1053 + <onProperty rdf:resource="&base_ontology;hasSubStructure"/>
  1054 + <onClass rdf:resource="&base_ontology;Variable"/>
  1055 + <qualifiedCardinality rdf:datatype="&xsd;nonNegativeInteger">0</qualifiedCardinality>
  1056 + </Restriction>
  1057 + </rdfs:subClassOf>
  1058 + <rdfs:subClassOf>
  1059 + <Restriction>
  1060 + <onProperty rdf:resource="&base_ontology;hasDataRestriction"/>
  1061 + <allValuesFrom rdf:resource="&rdf;PlainLiteral"/>
  1062 + </Restriction>
  1063 + </rdfs:subClassOf>
1023 1064 <rdfs:comment>SimpleTypeVariable (Class: SimpleTypeVariable) is a sub-class of class:Variable that only consists of Variables of simple xml types like xsd:integer, xsd:string…, potentially including restrictions
1024 1065  
1025 1066 The simple datatypes and –restrictions contained in &quot;OWL 2 Web Ontology Language Structural Specification and Functional-Style Syntax (Second Edition)&quot; are supported. (see http://www.w3.org/TR/owl2-syntax/)</rdfs:comment>
... ... @@ -1036,6 +1077,12 @@ The simple datatypes and –restrictions contained in &amp;quot;OWL 2 Web Ontology L
1036 1077 <allValuesFrom rdf:resource="&base_ontology;Thing"/>
1037 1078 </Restriction>
1038 1079 </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>
1039 1086 <rdfs:comment>A Thing in oneM2M (Class: Thing) is an entity that can be identified in the oneM2M System.
1040 1087 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;.
1041 1088 A Thing may have ThingProperties (Object Property: hasThingProperty). A Thing can have relations to other things (Object Property: hasThingRelation).
... ... @@ -1061,6 +1108,12 @@ A Value of a Thing can have meta data&lt;/rdfs:comment&gt;
1061 1108 <!-- http://www.onem2m.org/ontology/Base_Ontology/base_ontology#Variable -->
1062 1109  
1063 1110 <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>
1064 1117 <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.
1065 1118 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>
1066 1119 </Class>
... ...