13:06:50 RRSAgent has joined #wot-pf 13:06:50 logging to http://www.w3.org/2017/10/18-wot-pf-irc 13:06:56 Meeting: WoT PlugFest 13:06:59 sano has joined #wot-pf 13:07:13 kawaguch has joined #wot-pf 13:07:30 present+ Kaz_Ashimura, Matthias_Kovatsch, Taki_Kamiya, Toru_Kawaguchi, Uday_Davuluru, Kunihiko_Toumura, Michael_McCool 13:08:00 dape has joined #wot-pf 13:08:32 Agenda: https://lists.w3.org/Archives/Member/member-wot-ig/2017Oct/0017.html 13:08:44 present+ Michael_Koster 13:08:59 present+ Ryuichi_Matsukura, Takeshi_Yamada 13:09:19 kaz-win has joined #wot-pf 13:09:59 Mizushima has joined #wot-pf 13:10:02 present+ Takeshi_Sano, Tomoaki_Mizushima, Toru_Kawaguchi 13:11:00 sebastian has joined #wot-pf 13:11:16 present+ Sebastian_Kaebisch 13:11:22 zakim, pick a scribe 13:11:22 Not knowing who is chairing or who scribed recently, I propose Taki_Kamiya 13:11:44 zakim, pick a scribe 13:11:44 Not knowing who is chairing or who scribed recently, I propose Kaz_Ashimura 13:11:53 scrbenick: kaz 13:12:21 Agenda: https://lists.w3.org/Archives/Member/member-wot-ig/2017Oct/0017.html 13:13:01 topic: Matsukura-san's consolidated document 13:13:09 https://github.com/w3c/wot/blob/master/plugfest/2017-burlingame/preparation.md 13:13:50 mk: updated the figures right now 13:13:55 ... should be reloaded 13:14:04 matsu: created the MD above 13:14:09 ohura has joined #wot-pf 13:14:13 ... including the materials from my slides 13:14:27 ... section 1 introduction 13:14:55 ... including background and use case description 13:14:59 ... section 2 Servients 13:15:15 ... 3 kinds of servients for 4-layered model 13:15:32 ... application servient, device servient and proxy servient (remote/local) 13:15:49 ... the idea came from Koster at Binding call 13:16:01 ... 2.2 Servients from plugfest participants 13:16:23 ... application servient - remote proxy servient - local proxy servient - device servient 13:16:31 ... still mission pieces there 13:16:46 ... section 2.3 is missing 13:17:03 ... 2.4 is table o Servients and protocols 13:17:08 ... very important information 13:17:28 ... what kind of protocols are supported between which servient and which 13:17:44 ... e.g., app servient - remote proxy servient 13:18:14 ... Fujitsu app servient - (HTTP(S)) - Fujitsu remote proxy 13:18:37 q+ 13:18:44 ... Panasonic app servient - (HTTPS+WSS) - Panasonic device servient 13:18:51 ... please add information on your servients 13:19:03 ... 3. Application scenarios 13:19:10 ... what kind of scenarios for PlugFest? 13:19:24 ... 4. High level description of issues 13:19:42 ... issues to be solved from people's viewpoints 13:19:50 ... for the upcoming PlugFest 13:20:03 ... please put your issues here 13:20:25 ... next (section 4 again) Deadline and Schedule 13:20:31 ... expected schedule 13:20:42 ... who provides which servient(s)? 13:20:59 ... next week (Oct. 25) specify inter-servient interface 13:21:11 ... and then PlugFest itself on Nov 4-5 13:21:20 ... that's my points 13:21:31 s/points/document/ 13:21:55 mk: if you refresh the page, you can get the updated figures 13:22:17 -> https://github.com/w3c/wot/blob/master/plugfest/2017-burlingame/images/Servients_TPAC2017.png updated figure 13:22:48 mk: possible WebUI app on the local side 13:23:13 matsu: which one? 13:23:35 mk: "WebUI WoT Client (Siemens)" on my pc 13:24:06 ... and Local Proxy and Device Servients in Munich 13:24:18 ... difficult to explain in this 4-layer model 13:24:31 mm: diagrams in my document as well 13:24:59 mk: we have different dimension actually 13:25:10 q+ 13:25:10 q? 13:25:15 ack mk 13:25:28 mm: issue on Thing Directory 13:25:33 ... and local device 13:25:42 s/device/devices/ 13:25:54 ... factory service to create them 13:26:05 mk: already assumes remote proxy 13:26:53 q? 13:26:55 q+ 13:27:42 kaz: maybe we can use another kind of diagram as well 13:27:57 ... e.g., which shows the actual location-based topology 13:28:11 mm: categories of servients 13:28:58 ... 4-layered servients can be explained by the table 13:29:02 k_nimura has joined #wot-pf 13:29:35 ... we don't have all the parts in this diagram here 13:29:43 ... should make the diagram simpler 13:29:56 q+ 13:30:00 mk: there're kind of stacks 13:30:01 ack k 13:30:18 ... did some update again 13:31:17 mm: link to the implemented codes? 13:31:41 ... we should discuss management api as well 13:32:44 kaz: we don't have to stick with the "layer" here 13:32:52 ... we can express the role using the color 13:33:06 ... e.g., "WebUI WoT Client (Siemens)" as Matthias did 13:33:09 mm: yeah 13:33:13 tokuyama has joined #wot-pf 13:33:59 matsu: provide the detailed information on your part 13:34:17 ... and then would like to clarify which servient by whom to be connected which 13:34:44 ... for example, McCool, could you please add your stuff to this? 13:34:49 mm: yes, I can 13:34:56 ... after Matthias's update 13:35:03 mk: ok 13:35:10 ... going back to the table 13:35:17 ... the basic version on PPT was ok 13:35:35 ... but multi-column table here is difficult to edit 13:36:03 ... maybe easier to use PPT table and put the image of that? 13:36:15 matsu: ok to edit the ppt and put the table image here 13:37:04 ... Koster, can you add your information? 13:37:08 koster: ok 13:37:12 matsu: and Uday? 13:37:16 uday: will do 13:37:53 matsu: if your name is missing, please add a row 13:38:19 ... can put the updated table on this document 13:38:49 ... there are many developers for application servients this time 13:39:18 ... would like to know who will really provide applications 13:39:29 mm: application servient? 13:39:33 matsu: yes 13:39:41 mm: Intel as well 13:39:58 matsu: ok 13:40:44 kaz: maybe everybody can send the information by text to Matsukura-san 13:40:53 ... and he can integrate all the information 13:40:58 koster: makes sense 13:41:21 matsu: next, I'd like to clarify the application scenarios 13:41:41 ... please put your ideas to this section "3. Application scenarios" 13:41:41 q? 13:41:43 ack k 13:41:45 ack m 13:41:55 koster: question on the diagram 13:42:09 ... how the protocol binding might work 13:42:19 ... let's show global scope and local scope 13:42:42 ... local scope is accessible in the local network 13:42:49 ... mapping of devices and applications 13:43:00 ... possibly located on the remote side 13:43:16 matsu: device servient on the cloud side? 13:43:23 koster: yes, on the cloud side 13:43:27 ... shadow devices 13:43:36 ... HTTPS-based SmartThings API 13:43:47 matsu: ok 13:44:02 ... there are many variations for the upcoming PlugFest 13:44:12 koster: yes, I'll add my pieces 13:44:41 kawa: should we prepare Thing Description for devices we bring? 13:44:56 ... if we share TDs in advance, we can know what to do beforehand 13:45:08 ... useful to application scenario discussion as well 13:45:27 matsu: TD of each device servient should be uploaded on GitHub 13:46:08 kaz: we add TD and actual codes to the table 13:46:22 ... as McCool suggested before 13:46:28 nimura: about TD 13:46:41 ... which is the actual version for the Burlingame PlugFest? 13:47:01 mk: the target should be the FPWD of TD 13:47:19 ... experimentally could include observable events 13:47:42 ... what parts are mandatory and what are not 13:48:10 matsu: everyone wants to know about the differences between different versions 13:48:26 seb: good idea 13:48:51 mk: will add a link to the TD spec and explain the difference 13:48:54 matsu: appreciated 13:49:00 q? 13:49:10 ... any other comments? 13:49:17 mk: working on the ppt 13:49:30 ... please use the latest version from GH 13:49:34 yamada: will do 13:49:41 s/working/was working/ 13:50:07 kawa: question about the procedure 13:50:13 ... pullrequest for ppt? 13:50:25 ... don't have write permission maybe 13:50:36 mk: in that case, you can use pullrequest 13:50:49 matsu: you should use a different file name 13:50:53 ... that would be easier 13:51:06 ... any other comments? 13:51:22 (none) 13:51:41 topic: next week 13:51:46 matsu: we should talk about app scenarios next week 13:51:59 ... also posters and facilities 13:52:23 kaz: and inter-servient interface as recorded on the MD? 13:52:25 matsu: yes 13:52:45 ... will share a diagram on possible interface sequence 13:52:54 ... please share your input as well 13:53:10 ... by the next call on Wednesday, 25 Oct. 13:53:15 mm: regarding poster 13:53:22 ... make it professional 13:53:30 Template: https://github.com/w3c/wot/tree/master/plugfest/2016-lisbon 13:53:30 ... common template would be better 13:53:44 ... print it by Monday 13:54:02 ... we should have basic content by the PlugFest (on Nov. 4-5) 13:54:28 ... can finalize right after PlugFest (on Nov. 4-5) 13:54:44 mm: last year's template is a reasonable starting point 13:54:57 mk: Daniel Peintner took care of the one last year 13:55:02 ... template above 13:55:19 mm: can somebody take an action for this year? 13:55:41 mk: can do that right after getting the size available 13:55:49 taki: several sizes available 13:55:56 ... will send the information to the list 13:56:16 mk: please include me directly (in addition to the list) 13:56:28 matsu: how many posters? 13:56:42 seb: last time we had one for each building block 13:57:07 mk: can think about updating building block but quite some work 13:57:16 mm: architecture, td, etc. 13:57:19 ... and each demo 13:57:27 ... e.g., Amazon integration by Intel 13:57:34 ... 5 or more 13:57:43 s/5/So 5/ 13:57:52 koster: might have one for SmartThings 13:58:08 matsu: we have to assign people to each poster 13:58:10 mk: yes 13:58:25 matsu: aob? 13:58:29 (none) 13:58:45 [adjourned] 13:58:49 rrsagent, make log public 13:58:56 rrsagent, draft minutes 13:58:56 I have made the request to generate http://www.w3.org/2017/10/18-wot-pf-minutes.html kaz 14:17:42 Chair: Matsukura 14:17:42 rrsagent, draft minutes 14:17:42 I have made the request to generate http://www.w3.org/2017/10/18-wot-pf-minutes.html kaz 14:18:06 rrsagent, bye 14:18:06 I see no action items