HATEOAS - Matthias

mk: HATEOAS: Hypermedia-driven Actions and error handling
... [Be aware: WoT is Two-fold]
... complementing existing standards
... for binding templates, scripting API
... [HATEOAS/Hpermedia Controls]
... Entry URI -> Resource Directory -(follow links)-> Thing A
... how to handle multiple Things?
... [Prototype: ISO/IEC 15118-2 - Electric Vehicle Charging]
... a lot of steps here
... Siemens implements EV charging device
... setup phase and charging phase
... we can find use cases from this
... [Actions]
... short-lived actions and long-lived actions
... we might want to monitor them
... any implementations?
... ideas?
... in your prototype implementation, how to control the process?

radim: so far just reading data

mk: what about air conditioners or robot cleaner?
... would like to have some brainstorm

nimura: related to management topic
... need some control mechanism inside Things
... HATEOAS might be applied
... some one need to provide management mechanism

mk: definitely need new mechanism
... would like to start with this viewpoint
... related to Scripting API
... maybe we can connect this topic to the management topic, though
... you don't have to let the client know about concrete state transition model
... loose coupled interface
... (mentions a use case of online payment)
... having this mechanism for machines would be powerful

nimura: we need to think about concrete situation for this

mk: maybe machines should know about basic state transition by vising the "next" link

radim: question about the "long-lived" action

mk: there a lot of freedom here
... TD usually has some starting page and following consecutive links

nimura: need mechanism for error handling as well

mk: [Error Handling]
... shows example code of .onInvokeAction
... but how to recover?
... handling status code internally?
... [Error Messages]
... provide means for recovery
... 404: link to the start page
... 401: link to "log in with Facebook"
... provide means for machines
... TD-like interactions
... action(?) to the get access token
... would like to get opinions from people

kaz: mentions SCXML as a detailed state transition mechanism for long-lived action transition
... but what kind mechanism would fit which level of action transition?

mk: small high-level state transition mechanism possibly?
... (mentions an example use case of converting temperature by C to F)

Browser-based Servient - Radim

slides

scribe: [CHRIMEN]
... based on B2G
... reference open-source hardware board providing Web GPIO/I2C APIs
... [Exhibition/Event]
... try and touch event
... Interop Tokyo 2016
... Keio SFC 2016 event
... [Maker Fair]
... [Online Resources]
... chirimen.org, etc.
... [Web x IoT Maker's Hackathon]
... [Web x IoT Maker's Hackathon (cont.)]
... [Vision: Pervasive browsers]
... IoT devices into which Web technology ahs been introduced

mk: chicken and egg problem
... hard to give enough information
... [Web GPIO/I2C API]
... work by the Robotics CG
... robot controlled by a browser (with GPIO/I2C APIs)
... can handle temperature sensors, etc.
... and export the information as a servient
... [Recent Activities]
... implementations by polyfills
... discussion on APIs
... should be more general APIs?
... security issues
... authentication and authorization
... some of the devices don't have displays
... browsers always send requests?

radim: [Browser has no server function]
... [WoT servient with browser]
... browser on th edevice communicates with WoT servient on cloud or gateway as a WoT client
... [Issues]
... authentication and authorization of browser/client
... setting properties should be allowed only to some specific client
... consistency between thing descriptions and devices
... distance sensor value should be set as a distance properties

kaz: interested in the DAP WG's generic sensor API discussion?

radim: possibly but so far interested in GPIO and I2C
... how to make the interface abstract

mk: where to connect with the WoT discussion?
... Matsukura-san is working on abstraction
... this is related to hardware APIs
... how to talk with sensors
... are you aware of Johnny 5 project?
... similarity with TD as high-level interface
... can provide your ideas to the Scripting API discussion as well
... this board is usually connected with ubiquitous browsers
... possibly connection during the plugfest at the next f2f in Dusseldolf
... comments/questions?
... lunch and marketing strategy after that

[ Lunch ]

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/for/what about/
Succeeded: s/things/Things/
Succeeded: s/[ /[/
Succeeded: s/APIs/APIs?/
Succeeded: s/brower/browser/
Present: Matthias Barry Tokuyama Nishida Naomi Nimura Matsukura Naka Naoki Radim Kaz Uchida
No ScribeNick specified.  Guessing ScribeNick: kaz
Inferring Scribes: kaz
Got date from IRC log name: 17 May 2017
Guessing minutes URL: http://www.w3.org/2017/05/17-wot-breakout-minutes.html
People with action items: