10:55:48 <RRSAgent> RRSAgent has joined #wot-pf
10:55:48 <RRSAgent> logging to http://www.w3.org/2017/10/04-wot-pf-irc
10:58:49 <yamada> yamada has joined #wot-pf
10:59:56 <zkis> zkis has joined #wot-pf
11:02:00 <kaz_> Meeting: WoT PlugFest
11:02:06 <dape> dape has joined #wot-pf
11:02:18 <kaz_> present+ Kaz_Ashimura, Ryuichi_Matsukura, Takeshi_Yamada, Zoltan_Kis
11:02:41 <kaz_> present+ Tomoaki_Mizushima
11:03:11 <kaz_> present+ Daniel_Peintner
11:04:47 <kaz_> Agenda: https://www.w3.org/WoT/IG/wiki/PlugFest_WebConf#Agenda
11:05:05 <Soumya> Soumya has joined #wot-pf
11:05:41 <kaz_> present+ Soumya_Kanti_Datta
11:05:50 <kaz_> present+ Uday_Davuluru
11:06:30 <uday> uday has joined #wot-pf
11:06:49 <kaz_> scribenick: kaz
11:07:16 <kaz_> present+ Michael_McCool
11:08:02 <McCool> McCool has joined #wot-pf
11:08:29 <McCool> present+ Michael_McCool
11:09:43 <kaz_> topic: TPAC/PlugFest registration
11:10:08 <kaz_> https://www.w3.org/2002/09/wbs/1/WoTPlugFest201711/
11:10:13 <kaz_> https://www.w3.org/2002/09/wbs/35125/TPAC2017/
11:10:34 <kaz_> topic: PlugFest proposal update
11:10:46 <kaz_> -> https://lists.w3.org/Archives/Public/public-wot-ig/2017Oct/att-0005/Servients_TPAC2017_171004d.pptx Matsukura-san's slides
11:11:00 <Mizushima> Mizushima has joined #wot-pf
11:11:06 <kaz_> matsu: updated the slide based on the information on the f2f wiki
11:11:16 <kaz_> ... you can see there are 5 colors
11:11:43 <kaz_> ... application servient, remote proxy servient, local proxy servient, device servient and devices
11:12:03 <kaz_> ... the left most row is Panasonic
11:12:08 <kaz_> ... the second row is Siemens
11:12:36 <kaz_> ... then Lemonbeat, Intel, SmartThing, Eurecom
11:13:05 <kaz_> ... will get concrete information on Eurecom from Soumya
11:13:08 <kaz_> soumya: next week
11:13:17 <kaz_> matsu: the right most row is Fujitsu
11:13:27 <kaz_> ... Nimura and myself
11:13:39 <kaz_> present+ Sebastian_Kaebisch
11:13:55 <kaz_> ... also Mizushima-san from IRI will provide an application servient
11:14:00 <ohura> ohura has joined #wot-pf
11:14:01 <mjkoster> mjkoster has joined #wot-pf
11:14:05 <kaz_> mm: sorry have not put info on the wiki yet
11:14:12 <kaz_> ... would provide various devices
11:14:19 <mjkoster> I'm having trouble starting webex
11:14:30 <kaz_> ... not device servient itself but device servient generator
11:14:40 <kaz_> matsu: application as well?
11:14:45 <kaz_> mm: yes
11:14:49 <kaz_> ... using Alexa
11:15:00 <kaz_> ... web service is visible globally
11:15:20 <kaz_> ... bridge between Alexa and WoT devices
11:15:42 <kaz_> uday: allocate devices dynamically?
11:15:56 <kaz_> mm: want to talk to whatever Things dynamically
11:16:06 <kaz_> ... and generate voice interface for them
11:16:11 <kaz_> ... turn on/off
11:16:18 <kaz_> ... would see semantic tagging
11:16:32 <kaz_> ... the idea is more generic one
11:16:39 <kaz_> ... likewise OCF Thing
11:17:05 <kaz_> uday: Alexa already knows about the devices?
11:17:15 <kaz_> mm: no, dynamically asks about that
11:17:55 <kaz_> kaz: it seems there is a list of issues on p3
11:17:57 <kaz_> mm: yeah
11:18:08 <kaz_> ... would like to demonstrate semantic interoperability
11:18:29 <kaz_> ... proxy things could be useful but not unique
11:18:38 <kaz_> ... there could be more dynamic mechanism
11:19:00 <kaz_> mm: also think we need some directory service somewhere
11:19:06 <kaz_> matsu: tx for your comments
11:19:13 <Mizushima> Mizushima has joined #wot-pf
11:19:14 <kaz_> ... would be useful to have those points on the wiki
11:19:27 <kaz_> ... and discuss it in detail later
11:19:28 <kaz_> mm: ok
11:19:38 <kaz_> present+ Michael_Koster
11:19:48 <kaz_> present+ Kazuaki_Nimura
11:20:01 <kaz_> present+ Masato_Ohura
11:20:14 <kaz_> (Michal_Koster joins)
11:20:27 <kaz_> matsu: Koster, do you have any update on your side?
11:20:37 <kaz_> ... device servient, etc.
11:21:18 <kaz_> kaz: expectation for your devices and servients?
11:21:27 <kaz_> koster: Smart Thing devices
11:21:48 <kaz_> ... exposed as a "device"
11:21:55 <kaz_> mm: as an OCF device?
11:21:58 <kaz_> koster: yeah
11:22:04 <kaz_> ... light and motion sensor
11:22:18 <kaz_> ... will show the information on the f2f wiki
11:22:27 <kaz_> matsu: ok
11:22:51 <kaz_> ... maybe Matthias could provide a remote proxy as well
11:23:20 <kaz_> ... Daniel and Sebastian, do you know if Siemens can provide app servient and proxy servient?
11:23:33 <kaz_> dape: finish by beginning of Nov but not completed
11:23:41 <kaz_> sk: working on that
11:23:45 <mjkoster> q?
11:23:53 <kaz_> ... some slide maybe in 2 weeks
11:23:58 <kaz_> ... about how it works
11:24:04 <mjkoster> q+
11:24:16 <kaz_> sk: btw, "TD repository" is missing here
11:24:31 <kaz_> ... to find all the accessible Things
11:24:43 <kaz_> mm: yeah, how to discover Things/services
11:24:58 <kaz_> ... web services are visible and accessible, though
11:25:12 <kaz_> matsu: TD repository is one of the important issues
11:25:21 <kaz_> ... would like to talk about that in detail later
11:26:20 <kaz_> dape: not only who but one in the local side and another in the Internet side
11:26:33 <kaz_> kaz: why don't you explain the 2nd slide, Matsukura-san?
11:26:44 <kaz_> matsu: (go ahead to the 2nd slide)
11:27:04 <kaz_> ... devices on some locations
11:27:13 <kaz_> ... applications can be located in the Internet side
11:27:43 <kaz_> mm: one assumption here is all the applications work on the Internet side
11:27:56 <kaz_> ... on the other hand there can be apps on the local side like fog apps
11:28:15 <kaz_> ... also NATs accept all the global addresses?
11:28:39 <kaz_> koster: accepts all the incoming addresses. right?
11:29:14 <kaz_> mm: we can reach between different networks
11:29:27 <kaz_> ... there are 3 different networks here
11:30:00 <kaz_> koster: 2 different networks via a remote proxy
11:30:03 <kaz_> mm: right
11:30:27 <kaz_> matsu: this slide shows the combination of possible servients
11:30:44 <kaz_> ... we want to get information for the PlugFest
11:30:53 <kaz_> ... e.g., what kind of devices will be used
11:31:02 <kaz_> ... and application scenario
11:31:13 <kaz_> kaz: and the interface between servients
11:31:15 <kaz_> matsu: yes
11:31:27 <kaz_> ... (p3: Issues for TPAC plugfest)
11:31:27 <kaz_> ... issues
11:31:33 <kaz_> ... 1. interface between servients
11:31:42 <mjkoster> q?
11:32:10 <kaz_> ... need to think authentication, discovery/TD exchange, firewall/NAT, Event operation
11:32:21 <kaz_> ... 2. TD management
11:32:38 <kaz_> ... need to think about how to create the URI
11:33:00 <kaz_> mm: we should try discovery API
11:33:07 <kaz_> ... e.g., the one of node-wot
11:33:27 <kaz_> ... should be set up to look up local TD directory
11:33:32 <kaz_> ... and need to set up TD directory
11:33:59 <kaz_> ... other people use something other than node-wot
11:34:08 <kaz_> ... in that case, how to handle discovery?
11:34:17 <kaz_> ... where is "it"?
11:34:35 <kaz_> koster: one common directory to discover TD?
11:34:48 <kaz_> mm: Fujitsu may have their own implementation for discovery
11:35:28 <kaz_> ... local proxy could delegate discovery capability to remote proxy
11:35:37 <kaz_> koster: we've not clarify how to handle that yet
11:35:52 <kaz_> ... p
11:36:02 <kaz_> s/... p/
11:36:17 <kaz_> ... the basic case is having everything within home
11:37:13 <kaz_> mm: the basic case could be having one global chaching directory
11:37:32 <kaz_> ... would be happy to have one single point for now
11:37:40 <kaz_> s/chaching/cashing/
11:38:54 <kaz_> kaz: confirm everybody happy and provide servients
11:39:02 <kaz_> ... and file issues
11:39:06 <kaz_> mm: wot repo?
11:39:09 <kaz_> kaz: that's fine
11:39:29 <kaz_> mm: we have 2 proxies for the local network in SF
11:39:41 <kaz_> s/proxies/local proxies/
11:40:27 <kaz_> matsu: and each of the two remote servients correspond to one of them
11:40:44 <kaz_> q?
11:40:56 <kaz_> matsu: we should clarify the way how to register Things
11:41:11 <kaz_> mm: idea here to create a generic proxy service?
11:41:17 <kaz_> matsu: right
11:41:27 <kaz_> mm: we need to document the interface for that purpose
11:41:42 <kaz_> ... discover and identify the devices
11:42:11 <kaz_> koster: proxies have both the capabilities of expose/consume
11:42:36 <kaz_> mm: need to define TD for the local proxy servient
11:42:54 <kaz_> ... how to search devices within the local network from the outside
11:43:00 <kaz_> s/outside/outside?/
11:43:27 <kaz_> mm: discovery the Things dynamically or any provisioning?
11:43:55 <kaz_> koster: we have multiple problems
11:44:03 <kaz_> ... we have local proxy and remote proxy
11:44:26 <kaz_> ... what is exposed for the north-bound?
11:44:30 <kaz_> mm: OCF talks with CoAP
11:45:11 <kaz_> koster: the assumption here is
11:45:42 <kaz_> ... possibly have multiple protocols, CoAP, MQTT, etc.
11:45:48 <kaz_> ... or simply HTTP
11:46:02 <kaz_> mm: I'm creating a bridge
11:46:12 <kaz_> ... could create a proxy as well
11:46:52 <kaz_> q
11:46:55 <kaz_> s/q//
11:47:05 <kaz_> mm: this diagram is misleading
11:47:27 <kaz_> ... OCF device doesn't know the local proxy servient
11:47:44 <kaz_> ... on the other hand, the local proxy servient need to talk with the device servient
11:49:14 <kaz_> kaz: we should clarify that the green box "device servient" is just a device which handles the specific devices
11:49:44 <kaz_> mm: yes, for my side, the blue box itself is a servient
11:51:49 <kaz_> kaz: I guess the point here with the blue box is describe the pattern of Panasonic's system
11:51:52 <kaz_> mm: yeah
11:51:56 <kaz_> ... both patterns make sense
11:52:26 <kaz_> ... device servient+device vs servient device(which includes both device servient and device at once)
11:53:26 <kaz_> koster: in that case, some of the blue boxes can be directory connected to the yellow box (=local proxy servient)
11:54:50 <kaz_> kaz: so we should rather start with green boxes which expose device capability
11:54:54 <kaz_> mm: right
11:55:02 <kaz_> matsu: ok
11:55:59 <kaz_> ... would suggest you also generate diagrams of your systems and descriptions :)
11:56:06 <kaz_> mm: where to store the resources?
11:56:14 <kaz_> kaz: how about wot repo
11:56:27 <kaz_> ... under plugfest sub directory?
11:57:14 <McCool> https://www.w3.org/WoT/IG/wiki/F2F_meeting,_4-10_November_2017,_Burlingame,_CA,_USA#Suggested_Hotels
11:57:26 <kaz_> mm: visit the above f2f wiki
11:57:34 <kaz_> ... point the wot repo
11:57:43 <kaz_> ... and diagrams, etc.
11:58:03 <McCool> issue prefix "PlugFest4Q17
11:58:14 <kaz_> ... and issues should have prefix like "PlugFest4Q17"
11:58:42 <kaz_> kaz: and we can create a label "PlugFest4Q17" as well
11:58:45 <kaz_> mm: right
11:58:47 <McCool> and please document that in a section of the wiki page above...
11:59:48 <mjkoster> ack m
11:59:50 <kaz_> kaz: at some point we could think about MD and HTML on the wot/plugfest repo as well
12:00:32 <kaz_> ... btw, the minutes to be published publicly?
12:00:35 <kaz_> all: fine
12:00:40 <kaz_> [adjourned]
12:00:49 <kaz_> rrsagent, make log public
12:00:49 <McCool> McCool has left #wot-pf
12:00:53 <kaz_> rrsagent, draft minutes
12:00:53 <RRSAgent> I have made the request to generate http://www.w3.org/2017/10/04-wot-pf-minutes.html kaz_
12:01:02 <mjkoster> mjkoster has left #wot-pf
12:06:47 <Soumya> Soumya has left #wot-pf
12:09:22 <Mizushima> Mizushima has left #wot-pf
12:11:17 <ohura> ohura has left #wot-pf
12:26:15 <zkis> https://github.com/w3c/wot-scripting-api/issues/64
12:29:04 <zkis> https://github.com/w3c/wot/issues/352
14:03:25 <Zakim> Zakim has left #wot-pf