W3C

- DRAFT -

Web of Things Interest Group Teleconference

08 Jul 2015

See also: IRC log

Attendees

Present
tobie, dape, ddahl, jhund, soumya, tidoust, joerg, kaz, Dave, kathy
Regrets
Chair
jhund
Scribe
soumya, dsr

Contents


<trackbot> Date: 08 July 2015

<Soumya> scribenick: soumya

MMI Architecture

ddahl: begins presentation
... multimodal interaction WG - focused on user interfaces, combining different things like speech, handwriting
... modality inputs are applicable to input sensors and output to other things
... synergy between modality and WoT
... multimodal architecture - protocol for connecting things like camera to make an integrated system
... other on semantics
... semantics of user input, gives an example
... shows a slide on "putting things together" - multimodal spec
... interaction manager of the architecture orchestrates everything
... also need to interpret modality components
... generic modality component is similar to a servient

joerg: question on MMI being implemented in browser

ddahl: could be that
... amazon echo

daniel: can the orchestration be handed to the things at the bottom of the architecture?

ddahl: idea of nested component, withing one component there could be one interaction manager which is local to the things
... might be architecturally complecated
... showing an actual life cyle of an event
... will email later

jhund: asking for comments

none heard

ddahl: sending a paper

<dsr> scribenick: dsr

<scribe> chair: Johannes

<scribe> scribenick: dsr

OMA LwM2M

Soumya presents an overview via screen sharing

LwM2M defines an app layer protocol with a client embedded in the M2M device

The approach uses CoAP and TLS over datagrams

Information is referred to as a resource, and a client may have may such resources that are logically organised as objects

LwM2M can also use SMS as a transport mechanism

A bootstrap process is used to provision information to the LwM2M client. This enables the client to register itself with one or more LwM2M servers.

Clients can register, update and unregister themselves.

A keep alive mechanism is used to enable servers to drop clients that appear to be dead

The protocol supports create, read, write, delete, execute, write attributes and discovery operations.

The discover operation provides all resources of an object. This is based on the CoRE link format.

Servers can register to observe an object or resource. The client then sends update notifications as needed.

This is presumably based on the CoAP observe mechanism

Soumya lists some further reading materials

He has sent the slides to the mailing list

Dave: is M2M looking at the experimental broker mechanism for CoAP pub-sub?

Soumya: not as far as I know

Dave: this could be interesting for future work

CoRE

CoRE = constrained restful environment.

CoRE Linking defines a way to express Web Linking (inspired by HTTP Link, and before that by HTML Link element)

CoRE can be used with well known locations. CoAP defines GET operations on /.well-known/core as a way to discover all resources known to a given server.

The CoRE link format could in principle be used as part of registration process.

The format includes some parameters, e.g. the resource type. This is either a URI or a registered name.

There are conventions for using paths, e.g. to access the device, endpoint or configuration.

An end point could be a sensor or actuator.

The if parameter indicates what CoAP methods are supported on a given path, GET, PUT, etc.

Soumya has done some experiments with JSON.

The abbreviations for paths and parameter values enables compact device descriptions.

Johannes: so the rt parameter tells you what media types you can get, whilst the if parameter tells you what methods are supported.

Johannes thanks Soumya and Debbie for their presentations.

Any other business?

[no]

Next meeting at the 1am - 2am European time

… end of call

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2015/07/08 16:07:10 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/Topic CoRE/topic: CoRE/
Succeeded: i/ddahl: begins presentation/topic: MMI Architecture
Found ScribeNick: soumya
Found ScribeNick: dsr
Found ScribeNick: dsr
Inferring Scribes: soumya, dsr
Scribes: soumya, dsr
ScribeNicks: soumya, dsr
Present: tobie dape ddahl jhund soumya tidoust joerg kaz Dave kathy
Found Date: 08 Jul 2015
Guessing minutes URL: http://www.w3.org/2015/07/08-wot-ap-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]