Architectural Considerations for Semantic Support Group Name: WG5 Source: Martin Bauer (NEC), Joerg Swetina (NEC) Meeting Date: Agenda Item: WI-0005

MAS Architectural_Considerations_for_Semantic_Support Purpose of the contribution A variety of contributions to TR-0007 on semantics have been made, with different focus: – General state of the art in semantics – How can M2M use cases be realized with semantics (in general) – How can semantic technologies be used to solve problems within the oneM2M platform – How can the oneM2M platform be enhanced to support the semantic use cases In most cases, the architectural assumptions have not been made explicit and they may be different  This contribution explicitly discusses three possible architectural assumptions for semantic support in oneM2M – the intention is to show the possible spectrum  The goal is to agree on what the target / intended scope for oneM2M should be 2

MAS Architectural_Considerations_for_Semantic_Support Use of Semantics in oneM2M There are different options to what degree and for what purpose semantics can be supported in oneM2M: Provide semantic annotations, so applications can make use of semantics (current status in Rel. 1) Use semantic technologies for specific functionalities of the oneM2M platform and expose them as part of oneM2M interface (e.g. device template for creating resource structure, for discovery) Provide an interface with a full semantic view of the oneM2M platform (e.g. make oneM2M part of Semantic Web) 3

MAS Architectural_Considerations_for_Semantic_Support Semantic Annotations Resources, containers, values can be (optionally) annotated with URI (ontologyRef) Applications reading the information can use the URI(s) to – Identify the semantic meaning – Use it (e.g. URI as URL or for look-up in semantic DB) to retrieve additional information, e.g. semantic type, structure of data, etc. – Implement semantic functionalities on top (index, reasoning,...)  platform enables some semantic functionalities on top, not necessarily very efficiently, no semantic functionalities within the platform 4

MAS Architectural_Considerations_for_Semantic_Support Semantic Annotations 5 oneM2M Platform Semantics Infrastructure Application 1) Read ontology reference 2) Use ontology reference Ontology reference

MAS Architectural_Considerations_for_Semantic_Support Use of Semantic Technologies for Platform Functionalities Semantic technologies are part of the platform and the respective aspects are exposed through the interface The semantic modelling is typically targeted to explicitly support the specific functionality  typically existing ontologies cannot be used out of the box as the oneM2M platform specifics have to be taken into account Examples: – Discovery functionality – query has to be specified in suitable form. This could be an existing query language like SPARQL or something oneM2M-specific. Query results point to oneM2M resources. – Device template – defines the resource structure of the resources representing a specific device instance. May have generic parts from existing ontologies, but core aspects have to fit oneM2M resource structure. 6

MAS Architectural_Considerations_for_Semantic_Support Use of Semantic Technologies for (specific) Platform Functionalities 7 oneM2M Platform Application Discovery Registration (Resource Creation) Semantic Query, e.g. in SPARQL Semantic Device Template Application, e.g. interworking func.

MAS Architectural_Considerations_for_Semantic_Support Full Semantic Interface Platform exposes all aspects in semantic form All information is ontology-based and where possible existing ontologies are used Common semantic interfaces and tools are used for interacting with the platform Platform can easily be integrated with existing semantic platforms like the Semantic Web 8

MAS Architectural_Considerations_for_Semantic_Support Full Semantic Interface 9 oneM2M Platform Application Semantic Web Semantic Repository Reasoning Engine all information Semantic Interface Semantic Query