Ontologies used for oneM2M

Ontologies and their OWL representations are used in oneM2M to provide syntactic and semantic interoperability of the oneM2M System with external systems. These external systems are expected to be described by ontologies.

The only ontology that is specified by oneM2M is the oneM2M Base Ontology, as described in TS-0012. The oneM2M Base Ontology is the minimal ontology (i.e. mandating the least number of conventions) that is required such that other ontologies can be mapped into oneM2M.

Syntactic interoperability allows for interworking with non-oneM2M devices, e.g. in Area Networks. In this case an ontology - represented as an OWL file - that contains the Area Network-specific types of communication parameters (names of operations, input/output parameters, their types and structures, etc.) is used to configure an Interworking Proxy Entity to a oneM2M solution.

External organizations and companies are expected to contribute their own ontologies that can be mapped (e.g. by sub-classing, equivalence..) to the oneM2M Base Ontology. They then supplement oneM2M data with information on the meaning/purpose of their data. 

Semantic interoperability can be achieved by mapping ontologies from external organizations – possibly with the help of intermediate ontologies – ultimately onto the oneM2M Base Ontology.

The following ontologies are currently available:

SpecificationOWL file (RDF/XML formatted)VersionRelease
TS-0012 oneM2M_Base_Ontology-V_3_3_0.owl 3.3.0 Release 3
TS-0012 oneM2M_Base_Ontology-V_3_2_0.owl 3.2.0 Release 3
TS-0012 oneM2M_Base_Ontology-V_3_1_0.owl 3.1.0 Release 3
TS-0012 oneM2M_Base_Ontology-V_3_0_0.owl 3.0.0 Release 3
TS-0012 oneM2M_Base_Ontology-V_2_2_0.owl 2.2.0 Release 2