Semantic Annotation Options for Release2 Group Name: MAS WG Source: Catalina Mladin, Lijun Dong, InterDigital Meeting Date: Agenda Item: TBD

oneM2M-MAS-2015-XXXX Semantic annotation in TR-0007 Semantic annotation of M2M resources is a method for adding semantic information to M2M resources so that it provides consistent data translation and data interoperability to heterogeneous M2M applications. Semantically annotated M2M resources can be contacted by an M2M application that understands what data are provided by the resources and what these data means. These annotations provide more meaningful descriptions and expose M2M data than traditional M2M system alone. Semantic information is annotated using Resource Description Framework (RDF) or Web Ontology Language (OWL). 2

oneM2M-MAS-2015-XXXX Annotation Requirements (1 of 2) The M2M System shall provide capabilities to manage semantic information about the oneM2M resources, e.g., create, retrieve, update, delete, associate/link (1) The M2M System shall support a common language for semantic description, e.g. RDF (3). The M2M System shall support semantic annotation of oneM2M resources for example application related data contained in containers (14) The M2M System shall support semantic annotation based on related ontologies (15). The M2M System shall be able to support simultaneous usage of multiple ontologies for the same M2M resource (20) 3

oneM2M-MAS-2015-XXXX Annotation Requirements (2 of 2) The M2M System shall provide the capability for making semantic descriptions available in the M2M System, e.g. announcement (30) The M2M system shall enable applications to retrieve an ontology representation related to semantic information used in the M2M system (31) 4

oneM2M-MAS-2015-XXXX Architectural issues/choices What needs to be annotated? – All Resources (req. 1) includes containers, AEs, etc. What should the annotation provide? – Links to multiple related ontologies (req. 20) – Announceable (req. 30) How can the annotation be done? – Attributes – Linked/child resources Both provide CRUD capabilities, associate/link (req 1) RDF calls for resource-relationship-value triples. Missing: relationship-value doubles (tuples). 5

oneM2M-MAS-2015-XXXX Example TR-0007 A.3 Use Case 6 Use case assumptions: User enters gym Smart watch registration performed

oneM2M-MAS-2015-XXXX Assumptions 7 Classes and properties are defined in an ontology or ontologies that can be used for annotation (ns denotes a name space in which the ontology locates). – ns: DeviceApp – ns: identifier – ns: producedData Multiple ontologies may be used by and identified by the respective namespaces – Assume that we can mix in the same annotation: – ns1: DeviceApp – ns1: identifier – ns1: producedData – ns2: fitnessApp – ns2: user

oneM2M-MAS-2015-XXXX Opt A: Attribute-based Annotation 8 rdf:type ns: DeviceApp ns: identifier “JohnDoeWatch” ns: producedData “bloodPressure”

oneM2M-MAS-2015-XXXX Opt B. Resource-based Annotation 9 Two alternative options are proposed on the next slides

oneM2M-MAS-2015-XXXX Opt B1. “Basic” Resource-based Annotation 10 Description attribute: List of Relationship-Value tuples that describes the parent resource’s semantics. rdf:type ns: DeviceApp ns: identifier “JohnDoeWatch” ns: producedData “bloodPressure”

oneM2M-MAS-2015-XXXX Opt B2. “relationTuple” Sub-resource 11 Example on the next slide description <relationTuple> <subscription> relationTuple <semantics> <subscription>

oneM2M-MAS-2015-XXXX Example Opt. B2 12 rdf:type ns: DeviceApp ns: identifier “JohnDoeWatch” ns: producedData “bloodPressure”