08:02:57 RRSAgent has joined #wot 08:02:57 logging to http://www.w3.org/2016/05/20-wot-irc 08:03:19 meeting: Call with Markus Jung re WoT & IoTivity 08:03:29 present: Dave, Markus, Soumya, Kaz 08:03:49 markus: focus on the service layer 08:04:07 dsr: can you explain IoTivity? 08:04:22 markus: C++ and C-based IoT approach 08:04:50 ... 2 parts: discovery using CoAP, data transmission 08:05:09 ... useful for demonstration to show interoperability 08:05:21 ... 1.1 version released last month 08:05:25 ... any questions? 08:05:58 dsr: July may be difficult for demo, so might aim September in Lisbon 08:06:02 markus: could work 08:06:07 q+ 08:06:16 ... my question 08:06:21 ... on the IG's work 08:06:29 ... what kind of practical implementations? 08:06:34 ... just curious 08:06:49 dsr: open source development and lab-based ones 08:07:01 markus: you're planning plugfest in Beijing as well 08:07:03 dsr: yes 08:07:13 ... trying to invite other organizations 08:07:21 ack k 08:08:12 kaz: do you know Sanjeev BA? 08:08:16 markus: yes 08:08:22 ... IoTivity has 6 domains 08:08:30 ... smart home, automotive, etc. 08:08:43 ... IoTivity is a generic framework to be extended 08:09:02 ... resource model of WoT would be useful to IoTivity 08:09:29 present+ Matthias, Carsten, Kevin 08:09:46 kevin: from JLR 08:09:59 ... interested in IoTivity 08:10:12 dsr: some more questions on IoTivity 08:10:23 ... what is exposed to apps 08:10:30 ... low-level? high-level? 08:10:33 ... data type? 08:10:45 markus: multiple options 08:11:02 ... C language SDK 08:11:17 ... in this case, basically CoAP implementation 08:11:23 ... low-level server connection 08:11:37 ... similar to several APIs like entity handler 08:11:57 ... low level like CoAP request header 08:12:07 ... key-value map 08:12:08 Present: Markus, Carsten, Kaz, Kevin, Matthias, Dave 08:12:14 ... that is the basics 08:12:37 ... this is low-level API 08:12:45 ... and we also have high level API 08:12:57 ... data state driven APIs 08:13:33 ... there is still a potential W3C WoT IG's work would be helpful 08:13:36 dsr: tx 08:14:01 markus: simple key-value data type 08:14:20 -> http://www.slideshare.net/SamsungOSG/iotivity-connects-the-genivi-demo-platform-to-tizen fyi, Sanjeev's slides 08:14:57 markus: if you want something complicated, can use collected types 08:14:59 dsr: including nested model? 08:15:01 markus: yes 08:15:43 dsr: questions from others? 08:15:54 carsten: familiar with OCF's work :) 08:16:04 ... could improve descriptive capability 08:16:14 ... that's interesting work 08:17:15 cabo has joined #wot 08:17:43 Soumya has joined #wot 08:17:43 mkovatsc has joined #wot 08:17:46 KevG has joined #wot 08:17:57 markus: question about interoperability 08:18:04 ... data model of OCF and WoT 08:18:21 ... what do you want to show for the interoperability demo? 08:18:28 dsr: that's good topic to discuss 08:18:41 ... demonstrate high-level APIs 08:18:57 ... what kind of architecture should be use? 08:19:03 ... C++, etc. 08:19:21 q? 08:19:39 kevin: what is the underlying communication protocol? 08:19:42 ... part of the spec? 08:20:37 markus: basically build on the constrained application protocol 08:20:55 ... optimized version of HTTP 08:21:07 ... additional interaction patter could be added 08:21:17 ... RESTful communication over CoAP 08:21:40 ... binary representation of JSON 08:22:03 kevin: binary representation of JSON over WebSocket? 08:22:19 markus: IoTivity follows RESTful approach 08:22:36 matthias: what we want to achieve? 08:22:41 dsr: next phase? 08:22:51 matthias: what OCF would offer? 08:22:58 ... in Thing Description 08:23:07 ... what the interaction pattern should be? 08:23:21 ... pretty close resource model 08:23:34 ... Thing Description should have better design 08:24:05 markus: Thing Description for OCF devices? 08:24:21 matthias: TD is meta data model based on RDF 08:24:36 ... can handle constraints, etc., automatically 08:24:45 ... could be applied to the model of OCF 08:25:22 ... W3C can publish TD as REC track document, and OCF can refer to that 08:25:51 markus: most of the information by RAML and JSON Schema 08:26:07 ... TD could be useful 08:26:43 dsr: what kind of use cases do we want to show at the demo? 08:26:59 cabo: safe description for resource 08:27:08 ... making IoTivity devices available for TD 08:27:17 ... and inverse would be also useful 08:27:26 s/carsten/cabo/ 08:28:07 kaz: maybe we might have some concrete timeline for the September meeting in Lisbon 08:28:11 q? 08:28:36 kevin: mechanism and description language for automotive purposes 08:28:56 ... we (=automotive wg) are thinking about websocket-based service layer 08:29:31 ... complex entity may have complex structure 08:29:41 ... in side vehicle, need to identify things 08:30:09 ... different mechanism to describe signals for complex objects 08:30:33 q+ 08:30:59 dsr: maybe need to handle it separately since automotive area is a big use case 08:31:40 ... do you think automotive would be an interesting use case for TPAC demo? 08:31:57 kevin: have to be careful about what we could commit to 08:32:15 ... our deliverables are specs 08:32:24 s/our/our (=automotive wg's)/ 08:32:32 ... should focus on our specs 08:32:57 ... but think we need to work for OCF-based demo as well 08:33:08 ... can't commit at the moment, though 08:33:21 dsr: participating in BG or WG? 08:33:25 kevin: WG 08:33:50 dsr: if you have separate resources outside of the WG, maybe you can do something 08:34:43 kaz: would suggest we once bring back this idea to the automotive side and have some discussion there 08:34:51 kevin,dsr: ok 08:35:01 markus: basic question 08:35:15 ... looked at the WoT Architecture 08:35:20 ... what is the goal? 08:35:25 ... protocol as well? 08:35:30 ... only Thing Description? 08:35:40 dsr: IG is on the process of rechartering 08:35:52 ... WG is generating a draft charter 08:36:06 ... need to reach out external SDOs 08:36:18 ... build common understandings 08:36:28 ... looking into APIs, semantics, etc. 08:36:45 ... joint study with external SDOs 08:37:00 ... TD as metadata vocabulary 08:37:18 ... there are already similar approaches by other SDOs 08:37:36 ... WG will be launched maybe in October 08:38:04 -> http://w3c.github.io/wot/current-practices/wot-practices.html current practice 08:38:14 dsr: there is a document on Current Practice 08:38:53 markus: we can allow different device architecture 08:38:59 dsr: what platform? 08:39:18 markus: plug-in of Eclipse 08:39:21 ... on Linux 08:39:41 ... IoTivity is currently developed for Linux and Android 08:39:46 ... main platform is Linux 08:40:02 dsr: can use on an emulator? 08:40:09 markus: can check 08:40:19 ... for mobile demonstration setup, etc. 08:40:49 dsr: what's the requirements for boards? 08:41:11 markus: basically embedded pc like Rasberry pi(?) 08:41:18 dsr: networking, etc.? 08:41:34 markus: a few KB is ok 08:41:41 ... if Linux can works 08:41:54 s/is ok/is not ok/ 08:42:14 dsr: so relatively powerful device is expected 08:42:29 markus: for running emulator, you need a PC 08:42:42 dsr: nice to have a real board, but could do by an emulator 08:42:52 ... resources from your end? 08:42:57 markus: have to check 08:43:08 ... think can make contribution 08:43:21 dsr: would have brainstorming about the scenario 08:43:46 markus: Matthias's suggestion was OCF device 08:44:04 ... this kind of requirements? 08:44:06 dsr: yes 08:44:15 ... one OCF device talks with other devices 08:44:57 matthias: would be better to have IoTivity on the one side and WoT TD on another side 08:44:59 ... to see the interoperability 08:45:09 dsr: multiple platforms together is good 08:45:16 ... how to handle discovery? 08:45:19 ... multicast? 08:45:32 markus: currently using CoAP multicasting 08:45:44 dsr: do you have existing protocol's registering? 08:45:47 markus: yes 08:45:55 ... some discovery API provided 08:46:03 dsr: we used some repository for our PlugFest demos 08:46:14 ... something else to integrate 08:46:29 cabo: the repository was a shortcut 08:46:43 ... in the long run approach, we need some mechanism for discovery 08:47:20 dsr: abstraction of discovery is needed 08:47:38 cabo: interoperating with resources 08:47:43 ... population of information 08:48:20 dsr: would see interoperability with the IoTivity approach 08:48:32 ... what we need to do then? 08:48:44 ... write up a plan 08:49:04 markus: should be feasible 08:49:14 ... would see the demonstration scenario first 08:49:32 ... and would like to know about the IG's work including the TD 08:49:44 ... who is sketching the plan? 08:50:01 matthias: can set up how things should work together 08:50:17 dsr: when do we need the first description 08:50:20 ... e.g., end of June? 08:50:24 q+ 08:50:31 markus: fine 08:50:57 matthias: would see how much text is needed 08:51:07 dsr: Markus could make contribution 08:51:45 kaz: maybe we might want to have a regular call for this work? 08:51:57 dsr: we can have another call at the end of June 08:52:14 kaz: yeah, monthly call like that 08:52:41 dsr: try to write up the plan and have a call at the end of June 08:52:56 ... and another one after the Beijing meeting 08:53:09 ... initial description on the demo is needed for the first call 08:53:15 ... any other comments? 08:53:17 (none) 08:53:42 dsr: we need a use case for the demo 08:54:44 kaz: maybe we can start some initial discussion using a keyword "[iotivity]" on the public list 08:55:17 dsr: action on kaz/dave to talk with the automotive group 08:55:34 ... use cases and requirements for the possible automotive demo 08:55:42 kaz: will do 08:55:48 dsr: tx 08:56:05 ... and tx a lot for your participation, all 08:56:33 action: kaz to talk with the Automotive WG about the possible automotive demo with WoT during TPAC 2016 in Lisbon 08:56:33 Created ACTION-58 - Talk with the automotive wg about the possible automotive demo with wot during tpac 2016 in lisbon [on Kazuyuki Ashimura - due 2016-05-27]. 08:56:41 [ adjourned ] 08:56:46 rrsagent, draft minutes 08:56:46 I have made the request to generate http://www.w3.org/2016/05/20-wot-minutes.html kaz 08:57:04 rrsagent, make log public 08:57:06 rrsagent, draft minutes 08:57:06 I have made the request to generate http://www.w3.org/2016/05/20-wot-minutes.html kaz 08:57:45 Chair: Dave 08:57:56 present+ Soumya 08:57:59 rrsagent, draft minutes 08:57:59 I have made the request to generate http://www.w3.org/2016/05/20-wot-minutes.html kaz 08:59:19 rrsagent, stop