02:01:36 <RRSAgent> RRSAgent has joined #wot-breakout
02:01:36 <RRSAgent> logging to http://www.w3.org/2017/05/17-wot-breakout-irc
02:01:43 <barryleiba> barryleiba has joined #wot-breakout
02:08:09 <kaz> present+ Matthias, Barry, Tokuyama, Nishida, Naomi, Nimura, Matsukura, Naka, Naoki, Radim, Kaz
02:08:18 <ryuichi_> ryuichi_ has joined #wot-breakout
02:08:54 <kaz> topic: HATEOAS - Matthias
02:09:16 <kaz> mk: HATEOAS: Hypermedia-driven Actions and error handling
02:09:50 <kaz> ... [Be aware: WoT is Two-fold]
02:10:34 <kaz> ... complementing existing standards
02:11:26 <kaz> ... for binding templates, scripting API
02:11:45 <kaz> ... [HATEOAS/Hpermedia Controls]
02:12:36 <kaz> ... Entry URI -> Resource Directory -(follow links)-> Thing A
02:13:06 <shigeya> shigeya has joined #wot-breakout
02:13:13 <kaz> ... how to handle multiple Things?
02:13:34 <kaz> ... [Prototype: ISO/IEC 15118-2 - Electric Vehicle Charging]
02:13:41 <kaz> ... a lot of steps here
02:13:58 <kaz> ... Siemens implements EV charging device
02:14:16 <kaz> ... setup phase and charging phase
02:14:32 <kaz> ... we can find use cases from this
02:14:48 <kaz> ... [Actions]
02:14:58 <kaz> ... short-lived actions and long-lived actions
02:15:11 <kaz> ... we might want to monitor them
02:16:00 <kaz> ... any implementations?
02:16:11 <kaz> ... ideas?
02:16:30 <kaz> ... in your prototype implementation, how to control the process?
02:16:45 <kaz> radim: so far just reading data
02:17:00 <kaz> mk: for air conditioners or robot cleaner?
02:17:07 <kaz> s/for/what about/
02:17:14 <kaz> ... would like to have some brainstorm
02:17:34 <kaz> nimura: related to management topic
02:18:03 <kaz> ... need some control mechanism inside things
02:18:09 <kaz> s/things/Things/
02:18:28 <kaz> ... HATEOAS might be applied
02:18:43 <kaz> ... some one need to provide management mechanism
02:19:00 <kaz> mk: definitely need new mechanism
02:19:09 <kaz> ... would like to start with this viewpoint
02:19:49 <kaz> ... related to Scripting API
02:20:13 <kaz> ... maybe we can connect this topic to the management topic, though
02:21:35 <kaz> ... you don't have to let the client know about concrete state transition model
02:22:00 <kaz> ... loose coupled interface
02:22:26 <kaz> ... (mentions a use case of online payment)
02:22:44 <kaz> ... having this mechanism for machines would be powerful
02:23:11 <kaz> nimura: we need to think about concrete situation for this
02:24:23 <kaz> mk: maybe machines should know about basic state transition by vising the "next" link
02:24:51 <kaz> radim: question about the "long-lived" action
02:25:33 <kaz> mk: there a lot of freedom here
02:26:00 <kaz> ... TD usually has some starting page and following consecutive links
02:26:36 <kaz> nimura: need mechanism for error handling as well
02:26:46 <kaz> mk: [Error Handling]
02:27:17 <kaz> ... shows example code of .onInvokeAction
02:27:43 <kaz> ... but how to recover?
02:27:53 <kaz> ... handling status code internally?
02:28:54 <kaz> ... [Error Messages]
02:29:04 <kaz> ... provide means for recovery
02:29:11 <kaz> ... 404: link to the start page
02:29:37 <kaz> ... 401: link to "log in with Facebook"
02:29:48 <kaz> ... provide means for machines
02:29:53 <kaz> ... TD-like interactions
02:30:03 <kaz> ... action(?) to the get access token
02:30:33 <kaz> ... would like to get opinions from people
02:31:56 <kaz> kaz: mentions SCXML as a detailed state transition mechanism for long-lived action transition
02:32:12 <kaz> ... but what kind mechanism would fit which level of action transition?
02:32:26 <naka> naka has joined #wot-breakout
02:32:27 <kaz> mk: small high-level state transition mechanism possibly?
02:33:58 <kaz> ... (mentions an example use case of converting temperature by C to F)
02:34:41 <kaz> topic: Browser-based Servient - Radim
02:35:10 <kaz> -> https://github.com/naokisekiguchi/W3C_WoT_F2F_meeting_May_2017_Osaka_Japan/blob/master/W3C_WoT_F2F_meeting_May_2017_Osaka_Japan.pdf slides
02:35:25 <kaz> ... [CHRIMEN]
02:35:31 <kaz> ... based on B2G
02:35:57 <kaz> ... reference open-source hardware board providing Web GPIO/I2C APIs
02:36:05 <kaz> ... [Exhibition/Event]
02:36:14 <kaz> ... try and touch event
02:36:20 <kaz> ... Interop Tokyo 2016
02:36:28 <kaz> ... Keio SFC 2016 event
02:37:02 <kaz> rrsagent, draft minutes
02:37:02 <RRSAgent> I have made the request to generate http://www.w3.org/2017/05/17-wot-breakout-minutes.html kaz
02:37:13 <kaz> ... [Maker Fair]
02:37:20 <kaz> ... [ Online Resources]
02:37:29 <kaz> s/[ /[/
02:37:40 <kaz> ... chirimen.org, etc.
02:37:54 <kaz> ... [Web x IoT Maker's Hackathon]
02:38:14 <kaz> ... [Web x IoT Maker's Hackathon (cont.)]
02:38:31 <kaz> ... [Vision: Pervasive browsers]
02:38:45 <kaz> ... IoT devices into which Web technology ahs been introduced
02:39:07 <kaz> mk: chicken and egg problem
02:39:17 <kaz> ... hard to give enough information
02:40:08 <kaz> rrsagent, make log public
02:40:14 <kaz> rrsagent, draft minutes
02:40:14 <RRSAgent> I have made the request to generate http://www.w3.org/2017/05/17-wot-breakout-minutes.html kaz
02:40:25 <kaz> ... [Web GPIO/I2C API]
02:40:35 <kaz> ... work by the Robotics CG
02:41:04 <kaz> ... robot controlled by a browser (with GPIO/I2C APIs)
02:41:20 <kaz> ... can handle temperature sensors, etc.
02:41:29 <kaz> ... and export the information as a servient
02:41:47 <kaz> present+ Uchida
02:42:02 <kaz> ... [Recent Activities]
02:42:12 <kaz> ... implementations by polyfills
02:42:22 <kaz> ... discussion on APIs
02:42:54 <kaz> ... should be more general APIs
02:43:03 <kaz> s/APIs/APIs?/
02:43:08 <kaz> ... security issues
02:43:17 <kaz> ... authentication and authorization
02:43:38 <kaz> ... some of the devices don't have displays
02:43:58 <kaz> mk: browsers always send requests?
02:44:10 <kaz> radim: [Browser has no server function]
02:44:31 <kaz> ... [WoT servient with browser]
02:45:02 <kaz> ... browser on th edevice communicates with WoT servient on cloud or gateway as a WoT client
02:45:07 <kaz> ... [Issues]
02:45:18 <kaz> ... authentication and authorization of brower/client
02:45:27 <kaz> s/brower/browser/
02:45:46 <kaz> ... setting properties should be allowed only to some specific client
02:45:56 <kaz> ... consistency between thing descriptions and devices
02:46:08 <kaz> ... distance sensor value should be set as a distance properties
02:47:23 <kaz> kaz: interested in the DAP WG's generic sensor API discussion?
02:47:41 <kaz> radim: possibly but so far interested in GPIO and I2C
02:47:49 <kaz> ... how to make the interface abstract
02:48:02 <kaz> mk: where to connect with the WoT discussion?
02:48:18 <kaz> ... Matsukura-san is working on abstraction
02:48:34 <kaz> ... this is related to hardware APIs
02:48:42 <kaz> ... how to talk with sensors
02:48:58 <kaz> ... are you aware of Johnny 5 project?
02:49:47 <kaz> ... similarity with TD as high-level interface
02:50:54 <kaz> ... can provide your ideas to the Scripting API discussion as well
02:51:14 <kaz> ... this board is usually connected with ubiquitous browsers
02:53:28 <kaz> ... possibly connection during the plugfest at the next f2f in Dusseldolf
02:53:58 <kaz> ... comments/questions?
02:54:16 <kaz> meeting: Day 1 - breakout
02:54:53 <kaz> mk: lunch and marketing strategy after that
02:54:58 <kaz> [ Lunch ]
02:55:05 <kaz> rrsagent, draft minutes
02:55:05 <RRSAgent> I have made the request to generate http://www.w3.org/2017/05/17-wot-breakout-minutes.html kaz
02:55:19 <kaz> chair: Matthias
02:55:25 <kaz> rrsagent, draft minutes
02:55:25 <RRSAgent> I have made the request to generate http://www.w3.org/2017/05/17-wot-breakout-minutes.html kaz
03:08:47 <naomi> naomi has joined #wot-breakout
03:44:59 <shigeya> shigeya has joined #wot-breakout
03:49:03 <naomi> naomi has joined #wot-breakout
04:04:50 <shigeya> shigeya has joined #wot-breakout
04:13:20 <kaz> kaz has joined #wot-breakout
04:25:42 <naomi> naomi has joined #wot-breakout
04:29:13 <barryleiba> barryleiba has joined #wot-breakout
04:48:09 <elena> elena has joined #wot-breakout
05:00:28 <elena> elena has left #wot-breakout
05:05:31 <barryleiba> barryleiba has joined #wot-breakout
05:08:26 <naka> naka has joined #wot-breakout
05:08:39 <naomi> naomi has joined #wot-breakout
05:09:37 <barryleiba> barryleiba has left #wot-breakout
05:09:52 <barryleiba> barryleiba has joined #wot-breakout
05:10:05 <McCool> McCool has joined #wot-breakout
05:10:06 <dsr> dsr has joined #wot-breakout
05:10:12 <McCool> p+ Michael_McCool
05:10:52 <McCool> Kaz, are you on, and if so, can you share the WebEx link please for the breakout?
05:11:12 <McCool> Elena, sorry we are late, we are almost ready
05:11:12 <barryleiba> p+ Barry_Leiba
05:12:17 <naka> present+ Katsuyoshi_Naka
05:15:06 <sano_> sano_ has joined #wot-breakout
06:06:14 <shigeya> shigeya has joined #wot-breakout
06:31:10 <naka> naka has joined #wot-breakout
06:42:55 <shigeya> shigeya has joined #wot-breakout
07:29:21 <naomi> naomi has joined #wot-breakout
07:31:00 <Zakim> Zakim has left #wot-breakout
07:55:45 <barryleiba> barryleiba has left #wot-breakout
08:39:14 <dsr> dsr has joined #wot-breakout
08:50:34 <naomi> naomi has left #wot-breakout
09:21:59 <kaz> kaz has joined #wot-breakout
09:33:10 <dsr> dsr has joined #wot-breakout