04:33:06 <RRSAgent> RRSAgent has joined #iotpf
04:33:06 <RRSAgent> logging to http://www.w3.org/2015/10/28-iotpf-irc
04:33:45 <kaoru> scribenick: kaoru
04:33:46 <yosuke> yosuke has joined #iotpf
04:34:25 <daisuke> daisuke has joined #iotpf
04:34:46 <kaoru> oleg: By HTML5 application can easily change iot device configurations.
04:35:06 <chiba-shu> chiba-shu has joined #iotpf
04:35:18 <yosuke> [Oleg is explainig IQP, their Web-based IoT Platform, as a starting point of discussion.]
04:35:56 <gm_kou> gm_kou has joined #iotpf
04:36:04 <kaoru> Oleg: There are many protocls and need standardization to support all of the devices to be able to connect.
04:36:33 <kaoru> Oleg: Question is "what is the future W3C wants to have?"
04:37:42 <kaoru> Oleg: Think about Web of Things Framework
04:40:02 <kaoru> Oleg: Demonstration: Real-time dashboard to show the speed and the geographic location of a car.
04:40:05 <ymasao> ymasao has joined #iotpf
04:40:35 <kaoru> ... This application is build easily without any special things.
04:42:19 <kaoru> ...  Data is coming while the device is sending.  The app is build with a designer that can flexibly place components.
04:42:33 <tomoyuki_> tomoyuki_ has joined #iotpf
04:44:03 <kaoru> ... This is a use case that an application receives data from devices and render a page.
04:44:53 <kaoru> ... Live streaming of IoT sensor data, e.g. video stream, is also supported.
04:45:48 <kaoru> [Oleg demonstrates webrtc stream over the IQP platform]
04:46:57 <kaoru> q?
04:47:59 <tomoyuki> tomoyuki has joined #iotpf
04:48:04 <kaoru> @: There are so many solutions and that's why WoT interest group.  Have you looked at other systems and find gaps?
04:49:14 <kaoru> Oleg: What we discovered is do you supply GW to device manufacturers or do you create apps that connect to devices.  Device support after device support lacks standards.
04:49:40 <kaoru> ... We need to get device manufacturers involved in stardardization.
04:49:58 <jcdufourd> s/@:/Claes:/
04:50:09 <kaoru> ...  JSON@@ looks promising.
04:51:18 <yuwei> Did the documents need access right? http://www.w3.org/2015/10/28-iotpf-irc
04:52:31 <kaoru> Oleg: Device manufactures seems interested in connecting but standard formats from devices are not considered well yet.
04:53:17 <kaoru> Claes: You need data format from the devices?
04:54:00 <kawaguch> kawaguch has joined #iotpf
04:54:09 <tomoyuki> rrsagent, draft minutes
04:54:09 <RRSAgent> I have made the request to generate http://www.w3.org/2015/10/28-iotpf-minutes.html tomoyuki
04:54:21 <kaoru> Oleg: Cameras streams videos and can be controlled, but this kind of things are not available.
04:54:56 <kaoru> @: Did you face any concerns about generic communication protocols?  Any preference over protocols?
04:55:37 <kaoru> Oleg: MQTT is most flexible.  Easy to talk, more and more devices implement it.
04:56:15 <ryuichi> ryuichi has joined #iotpf
04:56:23 <kaoru> ... Swagger@.0 supports many devices and provide REST
04:57:05 <kaoru> ... Not all browsers support it because of security issue, though.
04:58:00 <ccho4> ccho4 has joined #iotpf
04:58:40 <kaoru> Oleg: Video streaming will impose traffic problems.  Configurable installation would be needed.
04:58:52 <jcdufourd> rrsagent, make logs public
04:59:26 <jcdufourd> Present+ Jean-Claude_Dufourd
05:00:02 <yosuke> rrsagent, draft minutes
05:00:02 <RRSAgent> I have made the request to generate http://www.w3.org/2015/10/28-iotpf-minutes.html yosuke
05:00:08 <kaoru> @2: Over the MQTT, did you build some kind of standard protocols or private?
05:00:34 <jcdufourd> Topic: Web-based IoT platforms federation
05:00:40 <jcdufourd> Chair: Oleg
05:00:54 <jcdufourd> rrsagent, draft minutes
05:00:54 <RRSAgent> I have made the request to generate http://www.w3.org/2015/10/28-iotpf-minutes.html jcdufourd
05:01:01 <kaoru> ...  Any state model, pub/sub topics in JSON/XML?
05:01:18 <kaoru> Oleg: JSON.
05:02:11 <kaoru> ... Custom JSON for devices.  This is another problem.  Customer requests vary and create more differences.
05:02:45 <kaoru> @2: In case of two companies want to communicate, any specific standard data model used?
05:03:17 <kaoru> Oleg: They provide integrations to adapt data formats.
05:03:49 <kaoru> ... As many data types and formats can be supported but you have to do yourself.
05:04:11 <kaoru> ... We would love to use any generic format available.
05:04:31 <kaoru> @2: May be worth staring a draft.
05:06:21 <kaoru> Claes: You said a device wakes up and send data over MQTT.  One issue is that you have to reach it while the device is sleeping.  Have you such use cases?
05:06:28 <tomoyuki> s/@:/Claes:/
05:07:46 <kaoru> @3: Bluetooth devices support low-energy communication.
05:08:17 <ddahl2> ddahl2 has joined #iotpf
05:08:18 <kaoru> Oleg: You cannot know how long the device can sleep until you know the use case.
05:08:54 <kaoru> Claes: Have you compared your platform to @@@-IoT, that also uses MQTT?
05:08:54 <ccho4> ccho4 has joined #iotpf
05:09:28 <kaoru> Oleg: I want to check Amazons.  Ours are more close to @@@'s
05:10:05 <tomoyuki> s/@@@'s/IBM's/
05:10:15 <kaoru> @2: I'm paying attention to CoAP.  It considers more about sleeping nodes via proxy mechanism.
05:10:53 <kaoru> ... It's request/response base but extensions on pub/sub models are also in progress.
05:11:13 <kaoru> ...  In the IETF context we work on this.  For transports, we have to do more things.
05:11:51 <kaoru> Claes: It sleeps and wakes up every second is not really sleeping.
05:12:14 <kaoru> @4: For IoT, there should some kind of metadata that describing this.
05:12:37 <kaoru> @2: WoT IG should describe @@@ higher levels to lower.
05:13:02 <kaoru> rrsagent, draft minutes
05:13:02 <RRSAgent> I have made the request to generate http://www.w3.org/2015/10/28-iotpf-minutes.html kaoru
05:13:54 <kaoru> @2: Sleeping node behind a NAT should be supported.  Not the firewall problem.
05:14:50 <kaoru> @4: Can you describe more about security and access control?
05:15:21 <tomoyuki> s/@4:/Dave_Raggett:/
05:16:01 <kaoru> Oleg: More or less, you receive the platform.  You get a credential to connect.  Device level, you start creating account that identify the system.
05:16:34 <kaoru> ... Users are who create applications or users runtime applications.
05:17:31 <kaoru> ... Querys work just as SQL over the data received from the devices.
05:17:42 <gm_kou_> gm_kou_ has joined #iotpf
05:18:40 <kaoru> ... System has configurations that what users can access what data types.
05:18:56 <kaoru> ... Role-based conditions are supported.
05:19:39 <kaoru> s/users runtime/use runtime/
05:22:29 <ddahl2> ddahl2 has left #iotpf
05:23:02 <ddahl2> ddahl2 has joined #iotpf
05:24:10 <kaoru> Oleg: Browser based IoT apps are supported.  Roadmap on guidlelines to support native apps is needed.
05:24:41 <ymasao> ymasao has joined #iotpf
05:24:46 <kaoru> Dave_Raggett: Contiributions to CG Bluetooth and NFC is welcome.
05:25:10 <ddahl2> Present+ Debbie_Dahl
05:25:25 <kaoru> @2: NFC API specifications exist.  Implementations to come.
05:27:13 <kaoru> Dave_Raggett: Many people work with WebSockets.
05:28:04 <kaoru> rrsagent, draft minutes
05:28:04 <RRSAgent> I have made the request to generate http://www.w3.org/2015/10/28-iotpf-minutes.html kaoru
05:32:37 <gm_kou> gm_kou has joined #iotpf
05:34:12 <jcdufourd> jcdufourd has joined #iotpf
05:34:28 <jcdufourd> jcdufourd has left #iotpf
05:35:34 <kawaguch> kawaguch has left #iotpf
05:45:49 <ymasao> ymasao has joined #iotpf
06:36:46 <gm_kou> gm_kou has joined #iotpf
07:09:34 <gm_kou> gm_kou has joined #iotpf
07:13:46 <ymasao> ymasao has joined #iotpf
07:13:55 <ymasao_> ymasao_ has joined #iotpf
07:15:09 <gm_kou> gm_kou has joined #iotpf
09:21:24 <knagano> knagano has joined #iotpf
10:59:44 <knagano> knagano has joined #iotpf