<kaz> scribenick: Istvan

<jhund> Agenda: https://lists.w3.org/Archives/Public/public-wot-ig/2015May/0046.html

Preliminals

<jhund> - Preliminals - Recap sketched structure: https://github.com/w3c/wot/blob/master/TF-AP/Example_sketch.md - Discussion with sensor API WG: https://github.com/w3c/sensors/issues/18 - Goal setting for TF work until F2F - AOB

Johannes asked for agenda bashing, no comments were made

<scribe> ongoing discussion about sensor API, Github repo

Johannes mentioned about the face to afce meeting agenda

Recam sketched structure

<jhund> https://github.com/w3c/wot/blob/master/TF-AP/Example_sketch.md

Johannes, mentioned about the Github document, details about how to structure the TF

anybody can submit pull request, Githib is the best tool

in terms of content we have the basic structure proposed

Johannes: basic model contains metadata, events and actions
... we could try to map these to HMTL, XMPP or COAP/MQTT at a later stage
... we can reference how this API can look like at a later stage
... focus on cross domain and cross device level structure of WoT
... main input should be focusing on structure, not content at the moment
... team is encouraged to provide feedback and comment on the document
... any questions on the document structure?

no feedback was received

Johannes: we should also look at viable alternatives to the current proposal, no comments was mentioned about the tooling

Generic Sensor API discussion

Johannes: next agenda point
... generic sensor API topic - define an API for a sensor on the device, for example a smartphone which is equipped with ambient light, geo sensors etc.
... sensor API group proposal - we can structure our API based on this API
... look at list of of known sensor types as a main difference, we can also focus on actuators (currently out of scope from sensor API)
... we should avoid parallel development, we need to leverage their baseline and look at our API definition
... Github API sketch shared on webex, comments are welcomed

<inserted> API sketch

Kazuyuki: proposed a new dedicated IRC channel for each TF meetings because minutes are mixed (confusing)

for the next call, action is taken by Johannes (wiki will be modified according to the proposal)

Johannes: point agreed about separate IRC channels for each TF
... sensor API group has been asked a questions for collaboration among groups.

Kazuyuki: we need to establish liaison with external bodies, but we don't have to do that for W3C groups. the WoT IG Chair simply can send a message to the Chairs of the other groups, e.g., Device API

Johannes: took an action to sync up with Joerg about cross links with other groups

Goal settings for the next f2f meeting

Johannes: next agenda item - goal settings for the next face to face meeting
... what will be the inputs for the next F2F meeting, 1. documentation about APIs and protocols 2. architecture
... start document on 2. architecture model work

Kaz: architecture has two components, we need to clairfy

we need to be clear on devices and server side

Kaz: we can start with a proposal for a basic architecture. each proposer could explain what their proposed components should do, e.g., WoT server, Wot device and WoT servient

Johannes: the doc proposal covers client side, server side and protocol on the high level
... we need to collect the ideas from slides and merge he different views to a single doc for a common understanding
... how could we start this piece of work

Kaz: proposed to start the draft, asking the presenters by adding it to wiki or creating a new doc

Johannes: best approach would be to open wiki and add all presentations to it, we have a wiki on W3C page already

Kaz: people can add their content / slides to the wiki as next step

Johannes: action to open a wiki page for this place-holder

+1

<kaz> +1

Dape: what is the plan to structure the wiki page?

Johannes: wikipage structure is TBD, it makes sense to propose a structure

Dape: took the action to make a proposal for creating a structure on the wikipage

Johannes: we have one doc for architecture, one for protocol binding, do we need anything else for the F2F mtg
... pointed out the draft charter, asked for comments from the team
... AOB

meeting is closed