Version 3.3.0 of the base ontology
Compare changes
+ 280
− 38
@@ -8,7 +8,7 @@
@@ -8,7 +8,7 @@
@@ -20,7 +20,7 @@ The oneM2M Partners assume no responsibility for errors or omissions in this doc
@@ -20,7 +20,7 @@ The oneM2M Partners assume no responsibility for errors or omissions in this doc
(c) 2016, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC). All rights reserved.
The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable regulations.
@@ -299,7 +299,7 @@ the cardinality of hasSubService must be - min 1.</rdfs:comment>
@@ -299,7 +299,7 @@ the cardinality of hasSubService must be - min 1.</rdfs:comment>
<ObjectProperty rdf:about="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasThingProperty">
<rdfs:range rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#ThingProperty"/>
@@ -309,7 +309,7 @@ the cardinality of hasSubService must be - min 1.</rdfs:comment>
@@ -309,7 +309,7 @@ the cardinality of hasSubService must be - min 1.</rdfs:comment>
<ObjectProperty rdf:about="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasThingRelation">
<rdfs:isDefinedBy>A Thing may have relations to itself or to other Things (e-g. a Thing "Room" could have a relation "has_Door" with a Thing "Door")</rdfs:isDefinedBy>
@@ -319,7 +319,7 @@ the cardinality of hasSubService must be - min 1.</rdfs:comment>
@@ -319,7 +319,7 @@ the cardinality of hasSubService must be - min 1.</rdfs:comment>
<rdfs:domain rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#InterworkedDevice"/>
@@ -329,8 +329,8 @@ the cardinality of hasSubService must be - min 1.</rdfs:comment>
@@ -329,8 +329,8 @@ the cardinality of hasSubService must be - min 1.</rdfs:comment>
<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.
e.g. a temperature sensor would refer to the Aspect "Temperature" that it measures</rdfs:isDefinedBy>
@@ -361,6 +361,10 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
@@ -361,6 +361,10 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
<DatatypeProperty rdf:about="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction_langRange">
<rdfs:subPropertyOf rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction"/>
E.g. the subset of the value space of rdf:PlainLiteral corresponding to the facet pair ( rdf:langRange "de-DE" ) contains the pairs < "abc" , "de-de" > and < "abc" , "de-de-1996" > (because these match the language range "de-DE" according to RFC 4647), but not the string "abc" (because it is not a pair with a language tag) or the pairs < "abc" , "de-deva" > and < "abc" , "de-latn-de" > (because these do not match the language range "de-DE" according to RFC 4647)</rdfs:comment>
@@ -369,6 +373,21 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
@@ -369,6 +373,21 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
<DatatypeProperty rdf:about="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction_length">
<rdfs:subPropertyOf rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction"/>
@@ -377,6 +396,49 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
@@ -377,6 +396,49 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
<DatatypeProperty rdf:about="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction_maxExclusive">
<rdfs:subPropertyOf rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction"/>
@@ -385,6 +447,49 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
@@ -385,6 +447,49 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
<DatatypeProperty rdf:about="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction_maxInclusive">
<rdfs:subPropertyOf rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction"/>
@@ -393,6 +498,21 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
@@ -393,6 +498,21 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
<DatatypeProperty rdf:about="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction_maxLength">
<rdfs:subPropertyOf rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction"/>
@@ -401,6 +521,49 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
@@ -401,6 +521,49 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
<DatatypeProperty rdf:about="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction_minExclusive">
<rdfs:subPropertyOf rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction"/>
@@ -409,6 +572,49 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
@@ -409,6 +572,49 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
<DatatypeProperty rdf:about="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction_minInclusive">
<rdfs:subPropertyOf rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction"/>
@@ -417,6 +623,21 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
@@ -417,6 +623,21 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
<DatatypeProperty rdf:about="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction_minLength">
<rdfs:subPropertyOf rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction"/>
@@ -425,6 +646,19 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
@@ -425,6 +646,19 @@ The Data Property "hasDataRestriction" shall always be sub-classed</rd
<DatatypeProperty rdf:about="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction_pattern">
<rdfs:subPropertyOf rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasDataRestriction"/>
@@ -813,12 +1047,6 @@ E.g. a thermostat would have "temperature-adjustment" as a Controlling
@@ -813,12 +1047,6 @@ E.g. a thermostat would have "temperature-adjustment" as a Controlling
@@ -843,12 +1071,22 @@ In the context of oneM2M a Device is always assumed to be capable of communicati
@@ -843,12 +1071,22 @@ In the context of oneM2M a Device is always assumed to be capable of communicati
<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.
A Functionality refers to (e.g. observes or influences) some real-world aspect(s), that can be modelled as a Class: Aspect.
E.g. considering a "light switch" then a related Functionality could be "Controlling_ON_OFF" or "Controlling Brightness". These functionalities would refer to an Aspect "light-control".
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</priorVersion>
@@ -908,6 +1146,12 @@ E.g. the indoor temperature could have meta data: "Degrees Celsius"</r
@@ -908,6 +1146,12 @@ E.g. the indoor temperature could have meta data: "Degrees Celsius"</r
<onProperty rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasOperationState"/>
<allValuesFrom rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#OperationState"/>
@@ -918,6 +1162,12 @@ E.g. the indoor temperature could have meta data: "Degrees Celsius"</r
@@ -918,6 +1162,12 @@ E.g. the indoor temperature could have meta data: "Degrees Celsius"</r
<allValuesFrom rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#OperationOutput"/>
<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.
An Operation is transient. I.e. an Operation can be invoked, possibly produces output and is finished.
- A non-oneM2M Device or a oneM2M entity (e.g. an AE) can invoke an Operation of the Device (oneM2M Device or InterworkedDevice) and that invocation can trigger some action in the Device. If an Operation has input data it may receive input data from
@@ -1005,6 +1255,16 @@ An Operation correlates the output data of the Operation to the input data that
@@ -1005,6 +1255,16 @@ An Operation correlates the output data of the Operation to the input data that
@@ -1032,16 +1292,10 @@ An Operation correlates the output data of the Operation to the input data that
@@ -1032,16 +1292,10 @@ An Operation correlates the output data of the Operation to the input data that
<allValuesFrom rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#OutputDataPoint"/>
<onProperty rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasSubService"/>
<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.
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.
A Service can expose one or more Functionalities and a Functionality can be exposed by one or more Services.
The Input- and Output DataPoints and Operations of a Service may have the same names as for a different Service, however the Service to which they belong differentiates how they are addressed in the Device (e.g. via a port specific to the Service).
NOTE: While a Functionality describes the – human understandable – meaning of a Service of the device the Service is used to describe how such functionality is represented in a communication network and can be accessed by electronic means. The Service and its Operations is therefore dependent on the technology of the network, hard- and software of the device.</rdfs:comment>
NOTE: While a Functionality describes the – human understandable – meaning of a Service of the device the Service is used to describe how such functionality is represented in a communication network and can be accessed by electronic means. The Service and its Operations is therefore dependent on the technology of the network, hard- and software of the device.</rdfs:comment>
@@ -1087,12 +1341,6 @@ The simple datatypes and –restrictions contained in "OWL 2 Web Ontology L
@@ -1087,12 +1341,6 @@ The simple datatypes and –restrictions contained in "OWL 2 Web Ontology L
<allValuesFrom rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#ThingProperty"/>
<onProperty rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasThingRelation"/>
<rdfs:comment>A Thing in oneM2M (Class: Thing) is an entity that can be identified in the oneM2M System.
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 "Device".
A Thing may have ThingProperties (Object Property: hasThingProperty). A Thing can have relations to other things (Object Property: hasThingRelation).
@@ -1107,10 +1355,10 @@ E.g. A room that is modelled in oneM2M would be a Thing that could have a room-t
@@ -1107,10 +1355,10 @@ E.g. A room that is modelled in oneM2M would be a Thing that could have a room-t
<rdfs:subClassOf rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#Variable"/>
<rdfs:comment>A Value (Class: Value) denotes a property of a Thing. A Value can e.g. be observed or influenced by devices, or it constitutes static data about a Thing.
A Value of a thing can concern a certain Aspect, e.g. the indoor temperature concerns the Aspect "Temperature" that could be measured by a temperature sensor.
@@ -1118,12 +1366,6 @@ A Value of a Thing can have meta data</rdfs:comment>
@@ -1118,12 +1366,6 @@ A Value of a Thing can have meta data</rdfs:comment>
<onProperty rdf:resource="http://www.onem2m.org/ontology/Base_Ontology/base_ontology#hasSubStructure"/>
<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.
<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.
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>