04:54:58 <RRSAgent> RRSAgent has joined #webi2c
04:54:58 <RRSAgent> logging to http://www.w3.org/2015/10/28-webi2c-irc
04:55:11 <stakagi> https://en.wikipedia.org/wiki/I%C2%B2C
04:56:01 <kaz> Meeting: GPID Breakout
04:56:01 <kaz> Chair: Koichi_Takagi
04:56:01 <kaz> anssi: concrete use cases?
04:56:01 <kaz> nori: would make a movement
04:56:01 <kaz> ... shows architecture
04:56:01 <kaz> ... people use several platforms but all of them different OSs
04:56:03 <kaz> ... on the other hand, if we use web apps, we can write the code just once
04:56:05 <kaz> anssi: that is the missing point usual OSs have
04:56:07 <kaz> tobie: what is the benefit of using Johnny 5?
04:56:09 <kaz> ... why using such a heavy runtime?
04:56:11 <kaz> ... just for showing the screen?
04:56:15 <kaz> nori: this architecture is proposed by IoT forum (picture)
04:56:17 <kaz> (Software Architecture (Draft))
04:56:19 <kaz> nori: sensors don't have strong computing power
04:56:21 <kaz> ... for embedded computing, you could use specific sensors
04:56:23 <kaz> ... but you can reuse CHIRIMEN for multiple purposes
04:56:46 <kaz> topic: WoT Device by CHIRIMEN (Naoki Sekiguchi)
04:56:47 <kaz> (explains the slides)
04:57:58 <kaz> naoki: low level API using Web I2C and Web GPIO
04:58:27 <kaz> anssi: does this mean that the developer need to know the sensor's characteristics?
04:58:46 <kaz> naoki: currently various devices with display
04:59:26 <kaz> ... CHIRIMEN board can work in a standalone manner
04:59:58 <kaz> ... in some case, I want to control the device directly
05:00:09 <kaz> ... not via Web or another device
05:00:30 <kaz> ... in that case, if we have a server like Node.js
05:00:38 <kaz> ... we can use server side scripts
05:00:55 <kaz> nori: can translate
05:01:26 <kaz> kaz: Anssi meant the lower part sensors. right?
05:01:28 <kaz> anssi: yes
05:01:54 <kaz> ... there is one implementation strategy like Generic Sensor API
05:02:31 <kaz> johannes: how to access the low-level sensor using generic api?
05:02:59 <kaz> anssi: so that's actually a JS library
05:03:59 <kaz> ... constraint with a set of sensors?
05:04:31 <kaz> tobbie: big device company might be interested to provide that
05:04:52 <kaz> nori: freedom of touching "everything" is the keyword here
05:04:55 <tobie> s/tobbie/tobie/
05:05:33 <kaz> anssi: portability?
05:05:46 <kaz> ... is that out of scope?
05:05:54 <kaz> nori: only the web is the current targt
05:05:57 <kaz> s/targt/target
05:06:35 <kaz> johannes: sandbox + a set of APIs for security purposes
05:06:45 <kaz> tobie: yes, the next question is how to handle security
05:07:11 <kaz> ... my understanding on what BT guys do is
05:07:20 <kaz> ... take control over sensors on the network
05:07:31 <kaz> ... no longer accessible from the origin
05:07:38 <kaz> ... do you have any strategy?
05:07:44 <kaz> nori: a lot of discussion
05:07:52 <kaz> ... running on FirefoxOS
05:08:07 <kaz> tobie: so reusing the security model of FirefoxOS
05:08:09 <kaz> nori: yes
05:08:25 <kaz> ... need to extend the security model for Web pages as well
05:08:32 <kaz> ... that's in our focus
05:08:55 <kaz> tobie: can talk with different sensors at once?
05:09:31 <kaz> ... multiple apps can talk with at the same timing?
05:09:38 <kaz> nori: let's talk about that later
05:09:54 <kaz> tobie: real use case?
05:10:05 <kaz> ... a bunch of use cases?
05:10:10 <kaz> nori: e.g., digital signage
05:10:23 <kaz> tobie: specific app domain for this?
05:10:35 <kaz> ... WoT machine?
05:10:46 <kaz> nori: please come to the demo booth
05:10:55 <kaz> ... within the main hall B
05:11:14 <kaz> johannes: so far FirefoxOS
05:11:38 <kaz> ... do you have another version of sandbox + JS?
05:11:47 <kaz> nori: some people don't require screens
05:11:59 <kaz> ... but HTML5 and browser is a nice UI
05:12:21 <kaz> ... on the other hand, Arduino kind of devices have poor UI capability
05:12:46 <kaz> ... currently we're focus on screen devices
05:13:08 <kaz> ken: screen+touch like smartphone?
05:13:10 <kaz> nori: yes
05:13:35 <kaz> ... the air conditioner I/F on the wall has poor interface capability
05:13:41 <kaz> anssi: right
05:13:55 <kaz> ... in the future, IoT devices will have some sort of screens
05:14:08 <kaz> nori: browsers have accessibility functions as well
05:14:18 <kaz> ... e.g., text reader
05:14:32 <kaz> anssi: much harder requirements for that
05:14:48 <kaz> ... it can run a default stack
05:15:21 <kaz> satoru: according to Moore's law we'll have strong capability with board computers
05:15:35 <kaz> darko: discovery?
05:15:41 <kaz> ... how to discover sensors?
05:16:16 <kaz> naoki: implemented by @@@
05:16:22 <stakagi> http://sensible.io/
05:16:47 <stakagi> http://mono.hm/
05:16:56 <kaz> s/@@@/Mono/
05:17:21 <kotakagi> s/Mono/Monohm/
05:17:23 <kaz> naoki: mDNS using socket API
05:17:57 <kaz> anssi: discover where and download library
05:18:16 <kaz> ken: what about things discovery?
05:18:47 <kaz> naoki: expose URI using mDNS
05:19:12 <kaz> ... sensors access the CHIRIMEN board via HTTP
05:20:12 <kaz> tobie: in order to talk with sensors you need to know what kind of the sensor it is
05:20:31 <kaz> ryoya: the application inside the CHIRIMEN knows about the sensors?
05:21:10 <kaz> nori: from this point, would mention how web developers access devices using this
05:21:27 <kaz> tobie: so the app developer has to know about devices?
05:22:09 <kaz> ... how device information is handled on the CHIRIMEN board
05:22:13 <kaz> s/d/d?/
05:23:46 <kaz> (some discussion)
05:24:13 <kaz> kaz: so currently the CHIRIMEN apps developer is exactly the same guy who develop the sensor itself
05:24:25 <kaz> ... so he knows the sensor's characteristics
05:24:34 <kaz> (got it)
05:24:40 <kaz> rrsagent, draft minutes
05:24:40 <RRSAgent> I have made the request to generate http://www.w3.org/2015/10/28-webi2c-minutes.html kaz
05:25:40 <kaz> topic: Wrap-up
05:26:10 <kaz> koichi: had discussions and got comments on security, etc.
05:26:38 <kaz> -> https://github.com/MozOpenHard/examples/tree/master/wotplugfest2015
05:26:55 <naokis_> https://github.com/MozOpenHard/examples/tree/master/wotplugfest2015
05:27:11 <kaz> [ adjourned ]
05:27:15 <stakagi> https://github.com/mozopenhard
05:27:26 <kaz> s/[ adjourned ]//
05:27:30 <kaz> [ adjourned ]
05:27:35 <kaz> rrsagent, draft minutes
05:27:35 <RRSAgent> I have made the request to generate http://www.w3.org/2015/10/28-webi2c-minutes.html kaz
05:28:25 <kaz> rrsagent, make log public
05:28:33 <kaz> rrsagent, draft minutes
05:28:33 <RRSAgent> I have made the request to generate http://www.w3.org/2015/10/28-webi2c-minutes.html kaz
05:34:44 <naokis_> naokis_ has joined #webi2c
05:41:42 <yukio> yukio has left #webi2c
05:52:36 <stakagi> stakagi has joined #webi2c
06:00:25 <oonishi> oonishi has joined #webi2c
06:02:38 <naokis_> naokis_ has left #webi2c
06:44:59 <stakagi> stakagi has joined #webi2c
06:59:10 <oonishi_> oonishi_ has joined #webi2c
07:00:28 <oonishi__> oonishi__ has joined #webi2c
07:01:06 <oonishi__> oonishi__ has left #webi2c
07:23:35 <Zakim> Zakim has left #webi2c
07:46:51 <stakagi> stakagi has joined #webi2c
08:11:16 <stakagi> stakagi has joined #webi2c
09:19:54 <stakagi> stakagi has joined #webi2c
09:20:38 <mantaroh> mantaroh has joined #webi2c
09:21:08 <mantaroh> mantaroh has joined #webi2c
10:36:50 <kotakagi_> kotakagi_ has joined #webi2c