1. TS-0034 scope against TS-0001, and managing stage 2 Semantics
Group Name: ARC#29.3, joint with MAS
Source: Catalina Mladin, Convida Wireless
Meeting Date: June 28, 2017

2. TS-0034 Scope and Structure (highlights)
Already proposed new resources: 4 for mashup, 2 for ontology, 1 for validation
5 Architectural Model and Concepts
6 Resource Types
Note: This section specifies new resource types for specific support of semantic functionality only (and the related CRUD procedures). General purpose resources will be referenced from TS-0001.
7 Functional Descriptions
Note: This section will contain high level feature description, related flows as well as detailed functional descriptions. The associated resources and their respective CRUD procedures will be referenced from clause 7.
Overview
Access Control
Semantic Annotation
Semantic Filtering and Discovery
Semantic Queries and Query Scope
Semantics Reasoning
Semantic Mash-up
Semantics-based Data analytics
Semantic Validation
Difficult to describe fully all this functionality in TS-0001

3. Alternative 1
Make TS a dedicated TS for semantics, explaining the entire functionality
TS-0001 will contain “hooks” and references pointing the reader to the document covering this specialized functionality.
Potentially include stage 3 aspects as well

4. TS-0001 highlights of changes moving semantic aspects TO TS-0034)
6 oneM2M Architecture Aspects
…2… Common Services Functions: … Data Management and Repository, Discovery CSF mention semantic processing, no changes needed
…8 Description and Flows of Reference Points
Request:semanticsFilter –referencing <SD> - needs TS reference
Upcoming query parameter – will probably need TS reference
…9.6 Resource Types
9.6.14a. semanticFanOutPoint, semantic Descriptor
…10.2. Functional Procedure
… Semantics Management
1 Intro, 2-5 CRUD <SD>
6 Semantic Discovery, 7. Annotation-based semantic discovery method, 8. Resource link-based method
No updates in black
Small updates in green
Moves to TS-0034 in blue
… blue detailed on next slides

5. Example Resource type move
Resource Type semanticDescriptor
The <semanticDescriptor> resource is used to store a semantic description pertaining to a resource and potentially sub-resources. Such a description may be provided according to ontologies. The semantic information is used by the semantic functionalities of the oneM2M system and is also available to applications or CSEs. [i.28] provides an informative example of a descriptor attribute.
See [Reference TS-0034] for a full description of the <semanticDescriptor> resource type, including child resources and attributes.

6. Example Functional Procedure move
Semantics management
Semantics management is performed for the purpose of…
The following are specialized resource types defined for the purpose of providing semantic enablement.
[table with resource type, notes/description,
reference in TS-0034 section 6]
The following are semantic procedures defined for the purpose of providing semantic enablement.
[table with procedure, notes/description,
reference in TS-0034 section 7]

7. Alternative 2 Make TS-00034 a dedicated TS for semantics.
TS-0001 will contain all resources and CRUD operations
TS-0034 will contain some more advanced explanations
Stage 3 aspects potentially covered by TS-0004

8. …. To be added in TS-0001 already! (1 of 2)
No updates in black
Small updates in green
Additions in TS-0034 in red… blue detailed on next slides
…8 Description and Flows of Reference Points
Request:semanticsFilter –referencing <SD> - needs TS reference
Upcoming query parameter – will probably need TS reference
…9.6 Resource Types
9.6.x1. semanticMashupJobProfile,
9.6.x1. semanticMashupInstance,
9.6.x1. mashup,
9.6.x1. semanticMashupResult,

9. …. To be added in TS-0001 already! (2 of 2)
…10.2. Functional Procedure
… X1 Semantic Mashup
… X2 Create <semanticMashupJobProfile>
… X3 Retrieve <semanticMashupJobProfile >
… X4 Update <semanticMashupJobProfile >
… X5 Delete semanticMashupJobProfile >
… X6 Create <semanticMashupInstance>
… X7 Retrieve <semanticMashupInstance >
… X8 Update <semanticMashupInstance >
… X9 Delete <semanticMashupInstance>
… X10 Retrieve <mashupInstance >
… X11 Retrieve <semanticMashupResult >
… X12 Delete <semanticMashupResult>
This is just for mashup. We need addition for Validation, analytics, reasoning, etc.
Resources will be “intertwined” with the general purpose ones. If we create “semantics” setion we basically include TS-0034 in TS-0001

10. Proposal: use Alternative 1
Pros of Alternative 1
Creates a clear “go to” spec for semantic functionality, with little back-and-forth reference to TS-0001 (and possibly TS-0004)
TS-0001 already huge
TS-0034 may include stage 3 aspects.
TS-0001 readers don’t need o worry about SPRQL, mashup, etc. unless they want to. Sematic functionality users tend to be knowledgeable and/or functionally focused
Keeps TS-0001 “clean” while still providing good information about resources and functionality, just FULL description referenced to TS-0034
This includes the sematic resources not being “intermingled” with the general purpose ones

11. Proposal: use Alternative 1
Cons of Alternative 1
Decentralized system
More than one spec to open
More than one spec to manage in stage 2
Improving the process of managing stage 2 between ARC and MAS is key, no matter how many documents are to be used