<scribe> scribenick: kaoru

oleg: By HTML5 application can easily change iot device configurations.

<yosuke> [Oleg is explainig IQP, their Web-based IoT Platform, as a starting point of discussion.]

Oleg: There are many protocls and need standardization to support all of the devices to be able to connect.
... Question is "what is the future W3C wants to have?"
... Think about Web of Things Framework
... Demonstration: Real-time dashboard to show the speed and the geographic location of a car.
... This application is build easily without any special things.
... Data is coming while the device is sending. The app is build with a designer that can flexibly place components.
... This is a use case that an application receives data from devices and render a page.
... Live streaming of IoT sensor data, e.g. video stream, is also supported.

[Oleg demonstrates webrtc stream over the IQP platform]

Claes: There are so many solutions and that's why WoT interest group. Have you looked at other systems and find gaps?

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.
... We need to get device manufacturers involved in stardardization.
... JSON@@ looks promising.

<yuwei> Did the documents need access right? http://www.w3.org/2015/10/28-iotpf-irc

Oleg: Device manufactures seems interested in connecting but standard formats from devices are not considered well yet.

Claes: You need data format from the devices?

Oleg: Cameras streams videos and can be controlled, but this kind of things are not available.

Claes: Did you face any concerns about generic communication protocols? Any preference over protocols?

Oleg: MQTT is most flexible. Easy to talk, more and more devices implement it.
... Swagger@.0 supports many devices and provide REST
... Not all browsers support it because of security issue, though.
... Video streaming will impose traffic problems. Configurable installation would be needed.

@2: Over the MQTT, did you build some kind of standard protocols or private?

Web-based IoT platforms federation

scribe: Any state model, pub/sub topics in JSON/XML?

Oleg: JSON.
... Custom JSON for devices. This is another problem. Customer requests vary and create more differences.

@2: In case of two companies want to communicate, any specific standard data model used?

Oleg: They provide integrations to adapt data formats.
... As many data types and formats can be supported but you have to do yourself.
... We would love to use any generic format available.

@2: May be worth staring a draft.

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?

@3: Bluetooth devices support low-energy communication.

Oleg: You cannot know how long the device can sleep until you know the use case.

Claes: Have you compared your platform to @@@-IoT, that also uses MQTT?

Oleg: I want to check Amazons. Ours are more close to IBM's

@2: I'm paying attention to CoAP. It considers more about sleeping nodes via proxy mechanism.

scribe: It's request/response base but extensions on pub/sub models are also in progress.
... In the IETF context we work on this. For transports, we have to do more things.

Claes: It sleeps and wakes up every second is not really sleeping.

@4: For IoT, there should some kind of metadata that describing this.

@2: WoT IG should describe @@@ higher levels to lower.

@2: Sleeping node behind a NAT should be supported. Not the firewall problem.

Dave_Raggett: Can you describe more about security and access control?

Oleg: More or less, you receive the platform. You get a credential to connect. Device level, you start creating account that identify the system.
... Users are who create applications or use runtime applications.
... Querys work just as SQL over the data received from the devices.
... System has configurations that what users can access what data types.
... Role-based conditions are supported.
... Browser based IoT apps are supported. Roadmap on guidlelines to support native apps is needed.

Dave_Raggett: Contiributions to CG Bluetooth and NFC is welcome.

@2: NFC API specifications exist. Implementations to come.

Dave_Raggett: Many people work with WebSockets.

This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/@:/Claes:/
Succeeded: s/@:/Claes:/
Succeeded: s/@@@'s/IBM's/
Succeeded: s/@4:/Dave_Raggett:/
Succeeded: s/users runtime/use runtime/
Found ScribeNick: kaoru
Inferring Scribes: kaoru
Present: Jean-Claude_Dufourd Debbie_Dahl

WARNING: Fewer than 3 people found for Present list!


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

Got date from IRC log name: 28 Oct 2015
Guessing minutes URL: http://www.w3.org/2015/10/28-iotpf-minutes.html
People with action items: