07:02:16 RRSAgent has joined #wot-pf 07:02:16 logging to https://www.w3.org/2019/09/10-wot-pf-irc 07:02:32 Meeting: WoT PlugFest - Online PlugFest 07:03:46 present+ Kaz_Ashimura, Michael_Lagally, Hiroki_Endo, Masaya_Ikeo, Kunihiko_Toumura, Takahisa_Suzuki 07:08:41 scribenick: kaz 07:08:56 endo_ has joined #wot-pf 07:09:29 Agenda: https://www.w3.org/WoT/IG/wiki/PlugFest_WebConf#Agenda_10.09.2019 07:09:36 topic: Agenda 07:09:51 ml: (goes through the agenda at: https://www.w3.org/WoT/IG/wiki/PlugFest_WebConf#Agenda_10.09.2019 ) 07:10:20 ... which devices, test cases to prioritize? 07:10:25 ... simple communication test 07:10:33 present+ Michael_McCool 07:11:21 mm: (points out some problem with the online-plugfest.md file) 07:11:27 -> https://github.com/w3c/wot/blob/master/plugfest/2019-tpac-fukuoka/online-plugfest.md online-plugfest.md 07:12:37 topic: Round table: which devices, test cases to prioritized? 07:12:57 s/topic: Round table: which devices, test cases to prioritized?// 07:13:12 ml: and then we should discuss F2F/PlugFest logistics 07:13:24 ... including demo/breakout setting 07:13:35 ... anything else for today? 07:13:57 mm: need to leave around 5:30pm 07:14:38 topic: Round table: which devices, test cases to prioritized? 07:14:45 ml: let's see the TDs 07:14:50 present+ Ege_Korkan 07:15:39 (Ege joins) 07:15:56 ek: would invite one of the students to this call 07:16:00 ml: ok 07:16:33 -> https://github.com/w3c/wot/tree/master/plugfest/2019-tpac-fukuoka/TDs/Fujitsu Fujitsu's TDs 07:16:44 ts: remote devices and local devices 07:16:48 ege has joined #wot-pf 07:17:08 present+ Christian_Glomb 07:17:50 -> https://github.com/w3c/wot/tree/master/plugfest/2019-tpac-fukuoka/TDs/Fujitsu/cloud Fujitsu's remote devices 07:18:41 Fujitsu: Fujitsu-WiFiSensor-3C71BF4253EC.jsonld, Fujitsu-Buzzerjsonld, Mozilla-LED.jsonld 07:19:11 q+ 07:19:42 ml: how to check if the device works? 07:19:47 ... are you on hangout? 07:19:57 ts: I'm on Panasonic hangout 07:20:32 Verena has joined #wot-pf 07:20:34 kaz: is the information available to everybody? 07:20:37 ml: yes 07:21:04 ts: (shows Fujitsu's devices on hangout) 07:22:16 kaz: just to make sure 07:23:03 ... does the cloud.md table include the information of devices on the local.md? 07:23:26 ts: Fujitsu's devices are connected to both the local proxy and the remote proxy 07:23:42 ... that's why there is the same information on the local devices on both the pages 07:23:44 kaz: got it 07:24:19 -> https://github.com/w3c/wot/tree/master/plugfest/2019-tpac-fukuoka/TDs/Intel Intel's TDs 07:24:49 mm: web cam and speech interface 07:24:54 ack k 07:25:15 q+ to ask about the relationship between intel-speak.json and intel-speak.jsonld 07:26:04 mm: longpoll grabs the image every 10 sec 07:26:15 ml: which of the entries works? 07:26:24 mm: all of them work 07:26:51 ml: do people have credentials for this? 07:26:56 mm: on the README.md 07:27:48 ... links to the Member archived credentials 07:28:03 ... also links to concrete TDs 07:28:43 ryuichi has joined #wot-pf 07:28:55 mm: you have to post for speech 07:29:14 ml: we should use the basic credential 07:29:22 ek: where is the information? 07:29:40 mm: there is links on README.md 07:29:53 ... will add clarification on the basic authentication 07:30:45 kaz: JPEG image is broken 07:30:57 mm: will fix 07:31:21 kaz: and relationship between JSON and JSON-LD for speech? 07:31:31 mm: just update the device IP address 07:31:37 ... please use the JSON version 07:32:00 -> https://github.com/w3c/wot/tree/master/plugfest/2019-tpac-fukuoka/TDs/Oracle Oracle's TDs 07:32:13 ml: (show the animation of the virtual devices) 07:32:43 s/virtual devices/Oracle IoT digital twin simulator/ 07:32:56 ... very simple model of the pump 07:33:22 ... please let me know if you need another one 07:35:33 ... (goes through the list of TDs) 07:35:56 ... you can log in and use the devices 07:36:09 q? 07:36:12 ack k 07:36:12 kaz, you wanted to ask about the relationship between intel-speak.json and intel-speak.jsonld 07:36:15 q+ 07:36:27 ts: tried to use the TD this morning 07:37:04 ... problem with href URL 07:37:28 ml: sorry 07:37:32 ... need to update the TD 07:38:23 kaz: what is the difference among all the Blue_Pump_*? 07:38:35 ml: specific instance for each vendor 07:39:06 present+ Verena_Schlott, Ryuichi_Matsukura 07:39:29 -> https://github.com/w3c/wot/tree/master/plugfest/2019-tpac-fukuoka/TDs/Panasonic Panasonic's TDs 07:40:09 ml: Toru-san is not available yet 07:40:23 kaz: what about NHK, Siemens and TUM? 07:40:35 cg: not prepared yet 07:40:49 ... planning to provide electric charger simulator 07:41:11 kaz: hardware-based or software-based? 07:41:17 cg: software-based one 07:41:27 kaz: tx 07:41:44 cg: today, I'm mainly observing 07:41:54 ... already got interesting information 07:42:29 kaz: do you think you can join the demo prep on Sunday? 07:44:06 cg: not available but will be there on Tuesday 07:44:32 mm: Intel and Siemens want to work on Tuesday at the W3C Team room 07:44:40 kaz: will double check with Naomi about that 07:44:51 ml: what about TUM? 07:45:05 ... Ege or Verena? 07:45:37 ... what kind of TDs are you planning to provide? 07:45:51 vs: we'll provide just clients 07:46:23 ek: can't access the devices at TUM from Fukuoka this time... 07:46:33 ml: what about NHK? 07:46:56 he: we don't provide TDs 07:46:58 Just for correction, I will be bringing the physically with me to Fukuoka 07:47:08 ... only application client on TV 07:47:19 q? 07:47:28 ack k 07:47:34 q+ to ask Ege for clarification 07:48:08 ml: which devices/TDs are you planning to use? 07:48:40 kaz: are you planning to get connected with Fujitsu and Panasonic? 07:49:00 he: Panasonic gateway and Fujitsu proxy 07:49:08 kaz: and what is your target devices? 07:49:35 McCool has joined #wot-pf 07:49:41 he: Panasonic's robot cleaner 07:49:56 ml: ok 07:50:10 ... regarding clients, how many applications do we have? 07:50:20 ... TUM, Hitachi, NHK, ... 07:50:25 ... three client applications? 07:51:16 i/regarding/topic: Client applications/ 07:51:45 ml: application developers can check the connectivity of their using devices/TDs 07:52:28 ml: Endo-san, can you check Fujitsu's device? or Panasonic one? 07:52:36 he: Panasonic robot cleaner 07:53:07 ... can show the video using hangout 07:53:32 ... our application runs/synchronizes with TV 07:55:03 (Endo-san prepares for his demo) 07:55:09 kaz: question for Ege 07:55:22 ... will you provide your TDs later? 07:55:26 ek: will do 07:56:44 topic: Connection test 07:57:08 ml: need to fix Oracle's TDs 07:58:53 https://hangouts.google.com/call/zMIBFnSSTxd4KpiLcP5DAAEI 08:00:06 ml: it seems there are two kinds of hangouts... 08:00:31 ... one on the README and another by Panasonic 08:00:51 ... we should use Panasonic's one given they're not here and can't change the setting 08:02:47 (15-min break) 08:03:12 s|https://hangouts.google.com/call/zMIBFnSSTxd4KpiLcP5DAAEI|| 08:03:18 rrsagent, make log public 08:03:23 rrsagent, draft minutes 08:03:23 I have made the request to generate https://www.w3.org/2019/09/10-wot-pf-minutes.html kaz 08:08:45 @toumura-san: Please try wot/plugfest/2019-tpac-fukuoka/TDs/Oracle/Blue_Pump_Hitachi.jsonld 08:12:28 tou: tried the updated TD 08:12:36 ... but there is some authentication problem 08:12:49 ... the error code is returned to the server 08:13:01 ... could you please check what's happening? 08:13:10 ml: ok, thanks for your feedback 08:21:05 (2nd session starts) 08:21:16 topic: Connection test 08:21:38 ml: who here can show your applications today? 08:21:47 ek: trying security devices 08:22:05 ... need some debugging for now 08:22:11 ml: ok 08:22:47 kaz: do you want to try today, Sunday or Tuesday? 08:22:54 ek: good question 08:23:05 ... can show node-wot testing today 08:23:33 ml: note tat we're test interoperability 08:23:40 ... what about Toumura-san? 08:23:47 tou: can show simple demo 08:24:02 ... can I share my screen? 08:24:05 ml: yes, please 08:24:12 topic: Hitachi 08:24:20 s/Hitachi/Hitach application/ 08:24:36 tou: simple test connection for each device 08:24:45 ... Fujitsu, Panasonic, Oracle, ... 08:25:28 ... can get connected with devices in Kanazawa 08:25:53 ... also USB buzzer light, rotary beacon, etc. 08:26:07 ... but can't get connect with Mozilla yet due to a bug 08:26:09 ... will fix it 08:26:47 ... would create an application to show camera's video 08:26:57 ... also the speech device works 08:27:25 ... can get connected with Panasonic devices as well 08:27:35 ... also some dashboard display 08:28:02 ... and then working on Suzuki-san's industry scenario 08:28:27 ... including Panasonic's bulletin board 08:29:03 ... but some problem 08:29:36 ... if Suzuki-san can generate a balloon, could be fixed 08:30:25 ... currently there is no value change 08:31:05 kaz: what do you mean "balloon"? 08:31:16 ... the plastic bag Matsukura-san brought? 08:31:21 tou: yes, that's the one 08:32:00 kaz: Matsukura-san and Suzuki-san, do you think you can bring a plastic bag again? 08:32:09 tou: or another kick 08:32:31 ts: not sure about the plastic bag but can we use another trigger? 08:32:47 ml: maybe we can use Siemens simulator? 08:33:01 tou: I can use that as well 08:33:16 s/Siemens/Oracle Siemens Festo/ 08:33:28 ... just wondering which one to be used 08:33:56 ml: but basically you can access those devices except Mozilla gateway 08:34:03 ... that is very good 08:35:08 topic: NHK 08:35:20 ml: Endo-san, what about you? 08:35:38 he: I'll show a demonstration within a local network 08:35:42 ... with Google hangout 08:35:57 ... local network first 08:36:07 ... and then run devices in Osaka 08:37:14 ... (shows the demo on hangout) 08:37:26 ... broadcast video on the TV 08:38:21 kaz: would be better to watch the hangout video directly (rather than via webex :) 08:38:25 ml: let's do so 08:39:04 kaz: is there any sound on the program? 08:39:32 he: no sound 08:39:35 kaz: ok 08:40:52 (mccool rejoins) 08:42:16 dape has joined #wot-pf 08:43:48 present+ Daniel_Peintner 08:44:32 topic: Fujitsu 08:44:40 ts: can I show my application? 08:46:52 ... (shares his screen) 08:49:10 ... power consumption at a smart home 08:49:55 ... the sensor, then air conditioner 08:50:12 ... phase 3 includes Mozilla's light 08:50:50 ... node-red dashboard shows energy managment and solar panel 08:51:09 ... some problem here 08:51:39 ... then second scenario 08:51:47 ... that is the industry scenario 08:52:00 ... monitors for sensors 08:52:23 ... z-axis acceleration, temperature, humidity and air pressure 08:52:42 ... if there is any abnormal situation, the beacon turns 08:53:04 ... that's it 08:53:14 ... questions/comments? 08:53:17 ml: looks nice 08:53:31 ... we've been seen two demos 08:53:54 topic: TUM 08:54:09 ek: managed to work with Intel 08:54:22 ... so would show that 08:56:36 https://hangouts.google.com/call/Gbgym9gd5j4OUEppg5VJAEEE 08:57:58 Verena is the screenshare 08:59:49 ek: (shows a dashboard software) 09:00:20 ... you can control properties, actions, events here 09:01:22 topic: NHK (revisited) 09:01:36 ml: anything to show now? 09:02:03 he: tx for waiting! 09:02:13 ml: can you please explain your demo? 09:02:26 he: (shows their demo) 09:02:38 ... restarted the TV broadcasting demo 09:03:03 ... Hybridcast TV can receive signals from broadcasting stations 09:03:12 ... which includes a trigger 09:03:28 ... and the application can control the robot cleaner, etc. 09:03:35 ... also there are lights around the TV 09:03:50 ... can be controlled based on the events 09:04:08 ml: embedding some trigger within the TV broadcasting content? 09:04:11 he: yes 09:04:26 ... the TV program wants to use a device 09:04:34 ... stop, change color, etc. 09:06:09 ml: video stream from IP? 09:06:36 ikeo: hybridcast handles both the broadcasting content and the IP video stream 09:06:55 ... event trigger message is a so-called shot 09:07:54 -> https://github.com/w3c/wot/tree/master/plugfest/2019-tpac-fukuoka diagram on the README.md 09:08:43 kaz: maybe you can explain the mechanism by showing the diagram on the README.md file 09:09:30 he: (Hybridcast Connect Application Demo) 09:09:32 ... tx 09:09:51 ... it's combination of broadcasting content and IP content 09:10:09 ... broadcasting content provides an event message as a trigger 09:10:51 ... hybridcast application transfers that event to the hybridcast connect application (=a node.js application) 09:11:24 ... the protocol between the hybidcast appliation and the hybridcast connect application is a proprietary one 09:12:07 ml: everything is controlled based on the event message included in the broadcast content 09:12:14 ... how to control the devices then? 09:13:00 ... the application can be interactive? 09:13:20 he: the user should be able to decide the scenario 09:13:39 ... in this scenario, we make a demo to make the story simple 09:16:27 kaz: provides some explanation about the basic mechanism of Hybridcast 09:16:48 topic: Next steps 09:16:54 ml: we got nice demos 09:17:03 ... and we got some actions 09:17:28 mm: maybe we should clarify who to get together tomorrow during the usual PlugFest call 09:17:39 ml: good idea 09:17:57 ... let's check what to be done 09:18:19 Action: Oracle to regenerate TDs 09:18:53 Action: Intel to fix digest auth, mark camera properties as read only 09:21:46 [Kaz's note: There are several remaining slots for preparation: (1) PF call on Sep. 11, (2) Demo prep day on Sep. 15 and (3) Tuesday on Sep. 17 at W3C Team room ] 09:22:17 ek: has updated TUM's TDs 09:27:48 (some discussion on demo session; details to be discussed during the main call tomorrow) 09:27:59 ml anything else for today? 09:28:03 (none) 09:28:05 [adjourned] 09:28:19 rrsagent, draft minutes 09:28:19 I have made the request to generate https://www.w3.org/2019/09/10-wot-pf-minutes.html kaz 09:28:34 endo_ has left #wot-pf