[TF-AP] MOM for last call, Draft agenda for next call on 10th of June, 9am CEST

Dear WoT IG task force,

* Please find the minutes of our last TF call here: http://www.w3.org/2015/06/02-wot-ap-minutes.html


Key outcomes:
- We discussed how legacy resp. foreign devices/protocols are represented resp. integrated into the WoT Architecture
- Four basic ways are identified:
 - "Mapping": The Resource model and interactions are directly mappable onto the protocol, the application layer remains semantically the same. 
 - "Tunneling": An IP(-like) transport is established over the foreign protocol, tunneling a native WoT protocol (e.g. HTTP or CoAP).
 - "Device driver": API-level adaption is taking place on the client device. A driver is transparently providing the regular WoT API to a script that is agnostic to the fact. 
 - "Adapter": A dedicated WoT server acts as a proxy exposing the legacy device as a WoT thing.
- There will be the two mentioned scripting APIs for WoT: client-side and server-side. A driver should transparently emulate these.
- We should try to establish guidelines on when th use what approach (i.e. mention key requirements for a protocol to enable mapping of the WoT Framework)

* Next call:

Our next call will be on June 10th @ 7:00 - 8:00 UTC / 9:00 - 10:00 CEST / 0:00 - 1:00 PDT / 16:00 - 17:00 JST
http://bit.ly/1G6lBeO

(see also attached ics file)

We will use this webex for audio:
https://mit.webex.com/mit/j.php?MTID=m6e93006969eb2607399a42a19bee6b36


minutes will be scribed in #wot-ap on irc.w3.org
http://irc.w3.org/?channels=wot-ap


* Agenda:

The draft agenda is set as follows:

- Preliminaries/Logistics

- recap of Architecture model: https://github.com/w3c/wot/wiki/Architecture-Model


- Discussion: Interaction patterns for the WoT Framework: how do clients interact with Actions, Properties and Event sources.

- AOB

As always, additions, comments and contributions are very welcome

Best Regards,
Johannes