<kaz> scribenick: Joerg

Preliminaries

Johannes discussed agenda

Johannes: are there additions

Discussion on scope definition and outputs of the Task force

Johannes: discussion of the scope and output of the TF

In the wiki is a first draft of the scope

<kaz> draft scope on wiki

Johannes: determine a set of common primitives for interactions

how do those primitives map to protocols and API

the APIcan be used to expose and consume things

Presentation from Nimura-san on UC and Architecture

<kaz> Nimura-san's slides

Use Case: house calls by caregivers

[page 2: An architecture]

Joerg: how to bind the device driver with the IoT device

Nimura-san: is not described here, might be an issue for the discovery, might use MAC

Johannes: is the protocol between the WoT device and the WoT Server and the one to the device driver the same

Nimura-san: the interface between GW and WoT server might be inside a smart phone
... in focus is how to migrate IoT devices such as thse connected via bluetooth and provide a driver for this

<inserted> scribenick: kaz

kaz: would suggest we should be very careful to distinguish the hardware layer and the software layer
... the "gateway" here should be called "wot adapter" or something like that
... and could be installed on the smartphone or the IoT device or even on some cloud service

[page 3: Setup]

<scribe> scribenick: Joerg

the smartphone can request the apropriate driver for the IOT

distribute the driver to the gateway

and register the device with the WoT Server

<kaz> scribenick: kaz

kaz: we can reuse existing discovery mechanism like bonjour. right?

nimura: yes

jhund: good input for the discovery group

Contribution from Johannes Hund, Siemens - Sketch for a document extracting commonalities in the proposals, i.e. the interactions and mappings to APIs and protocols

[audio connection dropped, and everybody switches to webex]

<kaz> Initial sketch on abstract interactions for APIs and Protocol bindings

jhund: scripting API mappings
... anybody can give input to this document
... as the output of this task force

<kaz> http://www.w3.org/TR/mmi-arch/ MMI Architecture

kaz: there is an abstracted layer interface definition within W3C named MMI Architecture, which could be included in this initial sketch document

jhund: can you talk with the mmi wg and ask them to contribute to this protocol mapping document?

kaz: will do

Joerg: we have several different architecture designs

jhund: having concrete graphical representations would be useful

+1

jhund: any good tool for graphical representations?

kaz: myself simply use Inkscape :)

jhund: is the output file an svg?

kaz: yes, and we can get a png version as well

<kaz> scribenick: Joerg

Johannes: PlantUML can be edited textually

<kaz> PlantUML site

<kaz> scribenick: kaz

taki: is that freely available?

Johannes: yes

taki: we can try several possible tools, and then make decision which to use

aob

Joerg: would think about time slots for TF calls
... we have three TFs
... maybe it would be better for Kaz to manage the WebEx sessions. I'll send the call details to you.

kaz: ok. I'll talk with the systeam, and will do so if it's possible

<kaz> scribenick: jhund

Joerg: we will have three time slots each Wednesday on fixed recurring slots, with the TF's rotating.

[ adjourned ]