Transcript oneM2M Architecture Adaptations for Semantics

Semantic Annotation
Options for Release2
Group Name: MAS WG
Source: Catalina Mladin, Lijun Dong, InterDigital
Meeting Date: 2015-03-16
Agenda Item: TBD
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).
oneM2M-MAS-2015-XXXX
2
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)
oneM2M-MAS-2015-XXXX
3
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)
oneM2M-MAS-2015-XXXX
4
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).
oneM2M-MAS-2015-XXXX
5
Example TR-0007 A.3 Use Case
Use case assumptions:
• User enters gym
• Smart watch registration performed
<watchAE>
oneM2M-MAS-2015-XXXX
6
Assumptions
• 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
7
Opt A: Attribute-based Annotation
<watchAE>
“attribute”
semanticDescription
oneM2M-MAS-2015-XXXX
rdf:type ns: DeviceApp
ns: identifier “JohnDoeWatch”
ns: producedData “bloodPressure”
8
Opt B. Resource-based Annotation
<watchAE>
Two alternative options are
proposed on the next slides
“attribute”
<semantics>
oneM2M-MAS-2015-XXXX
9
Opt B1. “Basic”
Resource-based Annotation
Description attribute:
List of Relationship-Value tuples
that describes the parent
resource’s semantics.
<semantics>
description
rdf:type ns: DeviceApp
ns: identifier “JohnDoeWatch”
ns: producedData “bloodPressure”
<subscription>
oneM2M-MAS-2015-XXXX
10
Opt B2. “relationTuple”
Sub-resource
<relationTuple>
<semantics >
description
relationTuple
<subscription >
<subscription >
Example on the next slide
oneM2M-MAS-2015-XXXX
11
Example Opt. B2
<watchAE>
<semantics>
<relationTuple1>
description
rdf:type ns: DeviceApp
<relationTuple2>
description
ns: identifier “JohnDoeWatch”
description
ns: producedData “bloodPressure”
<relationTuple3>
oneM2M-MAS-2015-XXXX
12