Version 3.2.0 of the base ontology
Compare changes
+ 334
− 316
@@ -38,7 +29,6 @@ NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURA
@@ -56,10 +46,10 @@ oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PR
<rdfs:comment>The resourceDescriptorLink annotation property is used to refer to a semanticDescriptor resource that contains more information about its subject. Its subject may be any individual and the range shall be the data literal or URI reference that represents the address of the semanticDescriptor</rdfs:comment>
@@ -77,250 +67,270 @@ oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PR
<rdfs:comment>The conversion rule (the VariableConversion in the domain of Object Property: hasConversion) converts the value range of a given Variable (see 6.2.22 Object Property: hasConversion) into the value range of another Variable (the Variable in the range of Object Property: convertsTo)</rdfs:comment>
@@ -338,219 +348,218 @@ e.g. a temperature sensor would refer to the Aspect "Temperature" that
@@ -615,110 +624,111 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
<rdfs:comment>This data property contains the value of the Variable if that value is part of the semantic description and is not contained in a different resource (identified by the oneM2MTargetURI data property). Storing the value of a Variable in a semantic description (i.e. as part of the RDF description in the semanticDescriptor resource) is useful for values that are relatively static (e.g. the name of the manufacturer).
This data property contains the URI of a oneM2M resource (<container> or <flexContainer>) through which the oneM2M instantiation of the value of the Variable can be manipulated by the communicating entity. It can contain an absolute address or an address relative to the <semanticDescriptor> resource that holds the RDF description of the Variable.
This data property contains the URI of a oneM2M resource (<container> or <flexContainer>) through which the oneM2M instantiation of the value of the Variable can be manipulated by the communicating entity. It can contain an absolute address or an address relative to the <semanticDescriptor> resource that holds the RDF description of the Variable.
@@ -736,7 +746,7 @@ That address could be e.g.
@@ -744,7 +754,7 @@ That address could be e.g.
@@ -753,29 +763,29 @@ The Aspect could be a (physical or non-physical) entity or it could be a quality
<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.
@@ -789,8 +799,8 @@ Note: In RESTful systems the names of Input- and OutputDataPoints are usually ch
@@ -799,25 +809,25 @@ E.g. a thermostat would have "temperature-adjustment" as a Controlling
<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.
@@ -832,7 +842,7 @@ In the context of oneM2M a Device is always assumed to be capable of communicati
@@ -845,8 +855,8 @@ A Functionality of a Device can be influenced / observed by a human user through
@@ -855,8 +865,8 @@ To enable a third party to instruct the device to retrieve (out of schedule) the
<rdfs:comment>An InterworkedDevice (Class: InterworkedDevice) is a Device – e.g. in an Area Network – 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</rdfs:comment>
@@ -864,8 +874,8 @@ To enable a third party to instruct the device to retrieve (out of schedule) the
@@ -874,7 +884,7 @@ E.g. a temperature sensor would have "temperature-sensing" as a Measur
@@ -883,29 +893,29 @@ E.g. the indoor temperature could have meta data: "Degrees Celsius"</r
@@ -923,8 +933,8 @@ An Operation correlates the output data of the Operation to the input data that
@@ -932,8 +942,8 @@ An Operation correlates the output data of the Operation to the input data that
@@ -942,44 +952,44 @@ An Operation correlates the output data of the Operation to the input data that
<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
@@ -988,8 +998,8 @@ An Operation correlates the output data of the Operation to the input data that
<rdfs:comment>OutputDataPoint (Class: OutputDataPoint) is a Variable of a Service that is set by a RESTful Device in its environment and that the Device updates autonomously (e.g. at periodic times). To enable a third party to instruct the device to update (out of schedule) the current value of a OutputputDataPoint devices often also offer a SET_OutputDataPoint Operation to trigger the device to update the data of the OutputDataPoint</rdfs:comment>
@@ -997,35 +1007,35 @@ An Operation correlates the output data of the Operation to the input data that
@@ -1039,26 +1049,26 @@ NOTE: While a Functionality describes the – human understandable – meaning
@@ -1070,17 +1080,17 @@ The simple datatypes and –restrictions contained in "OWL 2 Web Ontology L
@@ -1095,8 +1105,8 @@ E.g. A room that is modelled in oneM2M would be a Thing that could have a room-t
@@ -1107,19 +1117,27 @@ A Value of a Thing can have meta data</rdfs:comment>
<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.