Ontology Architectural Support Options Group Name: MAS WGSource: Catalina Mladin, Lijun Dong, InterDigitalMeeting Date: 2015-05-16Agenda Item: TBD

2

Overview• TS-0012 oneM2M Base Ontology is under development to define a set of

concepts, relationships and properties that are mainly used for defining oneM2M resources

• There are other ontologies defined addressing individual namespaces rated to M2M and agreed requirements to support simultaneous usage of multiple ontologies for the same M2M resource

• There are proposals/discussions (MAS-2015-0551R01) under way on modelling approaches when dealing with concepts from different ontologies– RE-USE (concepts from existing ontologies) where possible and extend the oneM2M

Base ontology where needed– RE-DEFINITION ( of similar concepts)

oneM2M-MAS-2015-XXXX by Nicolas Seydoux, LAAS-CNRS, from NEC MAS-2015-0551

Re-use vs. Mapping

Re-use

Mapping

oneM2M-MAS-2015-XXXX 4

NextIndependent of the answer to the modeling approach to move forward on functionality addressing the existing requirements, we need to determine architectural support needed for Ontology storage and management.

Consider a e-Health Use Case to highlight the Open Issues to address next

oneM2M-MAS-2015-XXXX

eHealth Use Case

5

eHealth Monitoring

System

Service Provider(IN-CSE)

Smart Watch

Blood Pressure Meter

Smart Scale

Ontology Repository

SemanticRepository

(Triple Store)

Semantic Engine

ResourceRepository

3rd Party (e.g., insurance

company)

Home Gateway (MN-CSE)

Q1: How to input (E-health) Ontology for oneM2M system use.

Q 2. How to create semantic descriptions and annotate resources

Q 3: Enable Semantic Repository (TripleStore)to store RDF triples?

Q 4: How to enable use of the Semantic Repository (TripleStore) for queries

Illustrate questions/proposals via Blood Pressure reading use-case flows

oneM2M-MAS-2015-XXXX 6

QuestionsWe propose for discussion the four steps identified in this use-case in order to address the following questions

a) How to store multiple ontologies such that they can be discovered and re-used by the M2M system

b) What the ontology repository resources should look like to enable use for semantic annotation

c) How to enable semantic queries using the given annotation

oneM2M-MAS-2015-XXXX 7

Architectural support assumptions

• There are three architectural elements which have been discussed/proposed to support both the oneM2M Base Ontology and any extensions:– ontologyRef attribute ( Release 1 agreement)

• For AE, container, contentInstance resources• URI of the ontology used to represent the information that is managed and

understood for that resource– Semantic descriptor attribute ( several proposals)

• semantic descriptor with relationships and values for the parent resource• RDF annotation or similar

– Ontology repository (MAS-2015-0528 NEC proposal)• Supports Management of ontologies• Supports CRUD, SPARQL query on ontology (as special retrieve)

oneM2M-MAS-2015-XXXX 8

Ontology Repository AssumptionMAS-2015-0528 NEC proposal

• Ontologies– Create

• Provide ontology directly• Download ontology from URL

– Retrieve• List of supported ontologies

• <ontology>– Retrieve

• Read complete ontology• Retrieve parts based on (SPARQL) query (e.g. subclasses)

– Update• Complete ontology• Partial update???

– Delete

ontologies

oneM2M base ontology

SSN ontology

Smart home ontology

Proposal for discussion – neither final nor complete

oneM2M-MAS-2015-XXXX

rdfs:Class

ex:Person ex:Device

ex:Patient

rdf:type

rdfs:subClassOf

ex:MeasurementSample

ex:BPMeasurementSample

rdfs:subClassOf

rdf:type rdf:type

(subject property object)ex:Patient rdfs:subClassOf ex:Person

ex:BloodPressureMeter

rdfs:subClassOf

Q1: Example Definition: Class

9

rdfs:Class – declare a resource as a class for other resourcesrdf:type – specify that a resource is an instance of a specific RDFS classrdfs:subClassOf – declare hierarchies of classes

Define Concepts such as “Patient”, “Blood Pressure Meter”, etc.

<ontology>

format

<class>

<relationship>

<subscription>

creator

name

oneM2M-MAS-2015-XXXX

Q1: Example Definition: Property

10

rdfs:Property – declare the class of propertiesrdfs:domain – mean that when the specified property is used in a triple, the subject of the triple will always be an instance of the class specified by the rdfs:domain property in the ontology.rdfs:range -- mean that when the specified property is used in a triple, the object of the triple will always be an instance of the class specified by the rdfs:range property in the ontology.

sValue: systolic valuedValue: diastolic value

rdfs:Class

ex:MeasurementSample

rdf:type rdf:Property

ex:dValue

rdf:typerdf:rangerdf:domain

ex:sValue

rdf:range rdf:type

xsd:integer

rdf:domain

rdf:type<ontology>

format

<class>

<rproperty>

<subscription>

creator

name

oneM2M-MAS-2015-XXXX

Blood PressureMeter

Resource Repository

Semantic Repository

(TripleStore)

Create resources

Semantics Engine

1.1 CREATE Request: <AE>/<container>/<contentInstance>(create <container> and <contentInstance> to store samples)

1.2 CREATE ResponseLocation: <AE>/<container>/<contentInstance>

Measure data

Create resources

1.3 CREATE Request: <AE>/<container>/<contentInstance>/<semantics>(create <semantics> to store metadata)

1.4 CREATE ResponseLocation: <AE>/<container>/<contentInstance>/<semantics>

2.1 Semantics annotation Request: Location: <AE>/<container>/<contentInstance>/<semantics>

2.2 Semantics annotation Response

Retrieve corresponding <semantics> resource

Create triples

3.1 Request to add new triples(newly generated triples)

Add and store triples

3.2 Response

Semantics Annotation

Q2: Creating Semantic Annotations & Triples

11

Create the real measurement data

Create the semantic descriptions about the measurement data

Create RDF triples and submit/store them in Semantic Repository

oneM2M-MAS-2015-XXXX

Q2: Resource Representation examples

12

<healthcare AE>: BPDev01

<container>: samples

<semantics>

Tuple: /measuredFor, URI of patient 1 <contentInstance>; /measuredOn, “2014-8-21”

<contentInstance>: s01

<semantics>

RDF Triple: <URI of s01 , /measuredOn , “2014-8-21” >

Subject of Tuples under s01 <contentInstance>

content

(70, 150)

tuple: /type, “Blood Pressure Sample”

<contentInstance>: s02

<semantics>

Tuple: /measuredFor, URI of patient N <contentInstance>; /measuredOn, “2011-4-10”^^/xsd:date

ResourceRepository

SemanticRepository

(Triple Store)

Corresponding RDF triples stored

in…

semantic descriptor

Example: Resource Representation for Blood Pressure Measurements and its Semantic Descriptor

oneM2M-MAS-2015-XXXX

Q3: Example Query on TripleStore

13

Blood PressureMeter

Semantics Engine

Semantic Repository

(TripleStore)

Ontology Repository

5. Semantics query request

Construct semantics query

4. Construct query message following semantic compatible format

6. Perform semantics query on the targeted

data set

7. Semantics query response with query results

8. Convert query results into format that

originator expects

1 Retrieve Request(ontology discovery)

2 Retrieve Response(ontology definition)

3. Retrieve Request(semantics query request)

9. Retrieve Response

Q3: SPARQL Query example

14

Select ?sample ?sValue_var ?dValue_var Where{ ?sample ex:sValue ?sValue_var. ?sample ex:dValue ?dValue_var. FILTER ( (?sValue_var >= 120) || (?sValue_var < 90)

|| (?dValue_var >= 80) || (?dValue_var < 60) ) }

Find blood pressure samples that are

abnormal

oneM2M-MAS-2015-XXXX 15

Annex:Assumed Functional architecture

Semantic Analysis and Query

Semantic Mash-Up

Ontology Modeling and Processing

Reasoning

Semantic Annotation

Device Abstraction

M2M Data Collection

Semantics Repository

Ontology Repository

M2M Applications

Data Repository

Abstraction &

Semantics

Data Access

Service Access

Non-oneM

2M D

omains

Data Analytics