Version 3.6.0 of the base ontology
Compare changes
+ 256
− 256
@@ -6,9 +6,9 @@
@@ -44,9 +44,9 @@ 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>
@@ -65,116 +65,116 @@ 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>
@@ -184,28 +184,28 @@ the cardinality of hasInputDataPoint must be - min 1.</rdfs:comment>
@@ -214,28 +214,28 @@ the cardinality of hasOperation must be - min 1.</rdfs:comment>
@@ -245,21 +245,21 @@ the cardinality of hasOutputDataPoint must be - min 1.</rdfs:comment>
@@ -268,51 +268,51 @@ the cardinality of hasSubService must be - min 1.</rdfs:comment>
@@ -330,10 +330,10 @@ e.g. a temperature sensor would refer to the Aspect "Temperature" that
@@ -341,11 +341,11 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
@@ -354,11 +354,11 @@ it applies to:
@@ -375,11 +375,11 @@ It applies to:
@@ -396,11 +396,11 @@ It applies to:
@@ -409,11 +409,11 @@ it applies to:
@@ -430,11 +430,11 @@ It applies to:
@@ -451,11 +451,11 @@ It applies to:
@@ -464,11 +464,11 @@ it applies to:
@@ -477,10 +477,10 @@ it applies to:
@@ -623,10 +623,10 @@ it applies to:
@@ -635,10 +635,10 @@ E.g. a certain type of Device could have the model (as a numeric description) or
<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).
@@ -646,49 +646,49 @@ E.g. a certain type of Device could have the model (as a numeric description) or
@@ -696,14 +696,14 @@ E.g. a certain type of Device could have the model (as a numeric description) or
@@ -716,14 +716,14 @@ E.g. a certain type of Device could have the model (as a numeric description) or
@@ -747,48 +747,48 @@ That address could be e.g.
<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.
@@ -800,31 +800,31 @@ Note: In RESTful systems the names of Input- and OutputDataPoints are usually ch
<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.
@@ -837,9 +837,9 @@ In the context of oneM2M a Device is always assumed to be capable of communicati
@@ -850,73 +850,73 @@ A Functionality of a Device can be influenced / observed by a human user through
<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>
@@ -932,69 +932,69 @@ 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>
@@ -1006,24 +1006,24 @@ NOTE: While a Functionality describes the – human understandable – meaning
@@ -1031,15 +1031,15 @@ The simple datatypes and –restrictions contained in 'https://www.w3.org/T
@@ -1047,13 +1047,13 @@ The simple datatypes and –restrictions contained in 'https://www.w3.org/T
@@ -1066,10 +1066,10 @@ E.g. A room that is modelled in oneM2M would be a Thing that could have a room-t
@@ -1078,12 +1078,12 @@ A ThingProperty 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.
@@ -1091,9 +1091,9 @@ These data of the Variable usually describe some real-world Aspects (e.g. a temp