00:34:10 barryleiba has joined #wot 01:17:32 barryleiba1 has joined #wot 03:24:12 ahaller2 has joined #wot 04:44:35 jungbin has joined #wot 07:06:03 JonathanJ has joined #wot 07:06:34 jungbin has joined #wot 07:15:01 JonathanJ1 has joined #wot 07:19:59 JonathanJ has joined #wot 07:25:01 JonathanJ1 has joined #wot 07:35:54 Hyunjin has joined #wot 07:38:48 yingying has joined #wot 07:39:34 yingying_ has joined #wot 07:40:05 ying_ying has joined #wot 07:53:22 Tomoyuki has joined #wot 07:53:31 masato has joined #wot 07:53:36 dsr has joined #wot 07:55:07 Karen has joined #wot 07:58:46 taki has joined #wot 08:00:28 kotakagi has joined #wot 08:01:03 sam has joined #wot 08:01:10 meeting: WoT IG Lisbon Face to Face 08:01:24 chair: Joerg_Heuer 08:01:37 agenda: https://www.w3.org/WoT/IG/wiki/F2F_meeting,_September_2016,_Portugal,_Lisbon#Agenda 08:01:51 rrsagent, set logs public 08:02:11 dape has joined #wot 08:02:26 katsu has joined #wot 08:03:05 kaz has joined #wot 08:03:12 barryleiba has joined #wot 08:03:19 rrsagent, make log public 08:03:23 rrsagent, draft minutes 08:03:23 I have made the request to generate http://www.w3.org/2016/09/23-wot-minutes.html kaz 08:04:00 mkovatsc has joined #wot 08:04:20 Fernando has joined #wot 08:05:06 ryuichi has joined #wot 08:05:08 mdadas has joined #wot 08:05:17 present+ Dave_Raggett 08:05:26 victor has joined #wot 08:05:38 present+ 08:05:51 present+ Yingying_Chen 08:06:26 Present+ Mohammed Dadas 08:06:28 Hyunjin has joined #wot 08:07:06 DarkoAnicic has joined #wot 08:07:12 present+ DarkoAnicic 08:07:24 scribe: Darko 08:07:49 Joerg: recap the activities from the first day W3C Wot F2F 08:08:06 daisuke has joined #wot 08:08:09 mmiya has joined #wot 08:08:42 kinjim has joined #wot 08:08:53 i/recap/scribenick: DarkoAnicic/ 08:08:58 Topic: Report Breakouts 08:09:28 joerg has joined #wot 08:10:03 jwehrman has joined #wot 08:10:25 yam has joined #wot 08:10:46 Andrei has joined #wot 08:10:55 Kajimoto-san: proposal on a lifecycle model for TD 08:11:50 daisuke_ has joined #wot 08:11:57 Kajimoto-san: the discussion on the topic will be continued via mailing list 08:13:29 present+ 08:13:46 rrware has joined #wot 08:13:51 joerg: to demonstrate the lifecycle, we could try at a plugfest to connect things at have one thing changing the TD of another thing during the lifecycle. 08:15:10 Johannes: proposal on events/subscriptions - micro use cases/application patterns 08:16:23 -> https://github.com/w3c/wot/tree/master/proposals/subscriptions 08:17:40 s/subscriptions/subscriptions RESTful handling of Subscriptions/ 08:17:55 domguinard has joined #wot 08:18:15 Johannes: we have identified 5 tasks and volunteers to work on 08:19:49 Dave: we distinguish two levels: application level and the protocol binding level 08:21:02 -> https://github.com/w3c/wot/issues scripting API issues list 08:21:11 along with the role of simple negotiation, e.g. where app requests some characteristic and uses introspection to see what the given protocol binding is able to offer. 08:21:59 -> https://github.com/w3c/wot/issues/235 issue 235 08:22:28 Johannes: we work on integrating into the API. Please provide your proposals by creating a pull request and discuss it over web conferences 08:23:58 Victor: report from the discussion on TD & hypermedia control (Hydra) 08:24:38 -> https://www.w3.org/WoT/IG/wiki/images/c/c9/TDvsHydra.pdf TD vs Hydra 08:24:39 JonathanJ has joined #wot 08:24:49 Victor: the question was whether we can use Hydra to model TD interactions 08:25:56 Victor: Hydra could be used for modeling operations of properties and actions 08:27:37 Victor: discussion on suported protocols by Hdra 08:28:16 s/suported/supported/ 08:28:21 s/Hdra/Hydra/ 08:28:40 rrsagent, draft minutes 08:28:40 I have made the request to generate http://www.w3.org/2016/09/23-wot-minutes.html kaz 08:28:46 Victor: an extension of scritp API could enable Hydra 08:29:35 ohsumi has joined #wot 08:29:52 Victor: discussion on Hydra will continue. bergi and Victor could take action on the implementation part. 08:30:36 Dave: we should invite Hydra community to participate to our plugfests 08:30:36 Dave: Hydra can be seen as another kind of netowkr services platform, and as such one that the web of things should be able to accommodate. We should consider inviting the Hydra CG to participate in a future plugfest to explore and demo such integration. 08:30:55 present+ Kaz_Ashimura(W3C), Dave_Raggett(W3C), Joerg_Heuer(Siemens), Matthias_Kovatsch(Siemens), Sebastian_Kaebisch(Siemens), Yingying_Chen(W3C), Ryuichi_Matsukura(Fujitsu), Kazuaki_Nimura(Fujitsu), Daniel_Peintner(Siemens), Takuki_Kamiya(Fujitsu), Fernando_Serena(UPM), Ryan_Ware(Intel), Barry_Leiba(Huawei) 08:31:55 Topic: F-Interop Project (Cesar Viho) 08:32:08 present+ Kinji_Matsumura(NHK), Masaru_Miyazaki(NHK), Koichi_Takagi(KDDI), Cesar_Viho(Inria), Federico_Sismondi(INRIA), Victor_Charpenay(Siemens), Frank_Reusch(RWE), Darko_Anicic(Siemens) 08:33:09 Cesar Viho: presenting F-Interop platform - an EU H2020 project 08:33:19 -> http://www.f-interop.eu/ F-Interop Platform 08:35:06 present+ Katsuyoshi_Naka(Panasonic), Masato_Ohura(Panasonic), Kazuo_Kajimoto(Panasonic), Yoshiaki_Ohsumi(Panasonic), Johannes_Hund(Siemens), Uday_Davuluru(RWE), Andrei_Ciortea(Univ._Lyon), Dom_Guinard(EVRYTHNG), Hyejin_Lee(HCTF), Daisuke_Ajitomi(Toshiba), Claes_Nilsson(Sony), Mohammed_Dadas(Orange), Suguru_Asai(UNI), Yuki_Matsuda(UNI), Kenichi_Nunokawa(Keio), Toshihiko_Yamakami(ACCESS) 08:35:07 Cesar Viho: it is about a platform for remote conformance tests for SDOs and SMEs 08:36:08 present+ Jeff_Wehrman(PTC), Hyunjin_Shin(HCTF), Bo_Chen(China_Unicom), Jonathan_Jeon(ETRI) 08:36:10 rrsagent, draft minuts 08:36:10 I'm logging. I don't understand 'draft minuts', kaz. Try /msg RRSAgent help 08:36:14 rrsagent, draft minutes 08:36:14 I have made the request to generate http://www.w3.org/2016/09/23-wot-minutes.html kaz 08:36:19 s/rrsagent, draft minuts// 08:38:01 Cesar Viho: different configurations will be possible to test 08:38:05 masato has joined #wot 08:39:02 Cesar Viho: 32 testbeds, 4755 nodes across Europe 08:39:19 ryuichi has joined #wot 08:40:27 olivexu has joined #wot 08:40:39 Cesar Viho: different standards are targeted, e.g., CoAP, 6TiSCH, 6LowWPAN, ETSI. Posibility to include oneM2M and W3C WoT. 08:41:22 Cesar Viho: we are here to explore this possibility. 08:41:48 sebastian has joined #wot 08:41:56 Federico: presents an example of CoAP test 08:43:31 Federico: status - the infrastructure is under development (not yet done). 08:46:13 Karen has joined #wot 08:49:29 Federico: shows a demo for F-interop - interoperability test Copper running against Californium 08:50:55 nunoken has joined #wot 08:51:31 Joerg: how do you specify test cases? 08:51:40 hjlee has joined #wot 08:52:21 present+ Zoltan_Kis(Intel), Andrew_Min-gyu_Han(Hansung_Univ.;guest), Debbie_Dahl(Inveted_Expert), Ari_Keranen(Ericsson), Milan_Patel(Huawei) 08:54:01 Federico: 2 files are needed, the test (description) and test analysis 08:54:09 Karen_ has joined #wot 08:55:15 dape has joined #wot 08:55:38 Federico: tests can be provided by anyone, i.e., not only platform operators 08:57:04 q+ to ask about anaysis of testing use cases for patterns that could be used to define declarative test specifications 08:57:06 Federico: simpler than TTCN-3 08:57:21 q- 08:57:45 ddahl has joined #wot 08:57:53 Karen has joined #wot 08:58:26 Federico: the platform will be available next year, for the detailed timeplan see the slides 08:59:41 Cesar Viho: please help us with requirements from W3C WoT to be addressed in the platform architecture 09:00:13 cabo has joined #wot 09:00:51 present+ Carsten_Bormann(TZI) 09:02:25 Cesar Viho: contribution to provision of tests will be paid 09:02:42 Present+ Jonathan_Jeon(ETRI) 09:05:01 s/Cesar Viho:/Cesar_Viho:/g 09:05:12 rrsagent, draft minutes 09:05:12 I have made the request to generate http://www.w3.org/2016/09/23-wot-minutes.html kaz 09:05:16 Dave: thank you. The platform is interesting for IG and for the WG pretesting 09:05:58 Dave: I note that the WoT IG could play a valuable role for exploring how to do testing in support of the WoT WG, which will formally define the set of tests needed for REC track specs 09:06:06 I am also interested in how tests can be applied to different layers in the abstraction stack 09:06:43 q+ 09:06:48 ack d 09:06:48 dsr, you wanted to ask about anaysis of testing use cases for patterns that could be used to define declarative test specifications 09:07:10 Dave: would be good to have a possibility to declarative specify tests 09:09:23 I have two questions: the first is whether you have looked at about anaysis of testing use cases for patterns that could be used to define declarative test specifications 09:09:35 Federico: it needs to be discussed in the phase of defining requirements 09:09:56 The second is how tests can be applied to different layers in the abstraction stack, and whether you have explored that in practice? 09:10:01 zkis has joined #wot 09:10:16 Johannes: a proposal to look for a language for behavioral tests 09:10:31 Karen has joined #wot 09:11:25 Joerg: could you please explain more the details about different components in the architecture, e.g., agents 09:12:47 Karen has joined #wot 09:13:01 Johannes: agents support flexible testing. 09:14:44 Matthias: we want o support multiple protocols. How to find a good strategy to define tests and not to have explosion of all possible combinations of features for diff. protocols etc. 09:15:38 s/Johannes:/Federico: 09:16:18 Matthias: could you support the testing for online plugfests 09:16:52 Cesar Viho: yes, we will work on this 09:18:56 Cesar Viho: we will work on a reference model to support multiprotocol testing 09:19:33 q+ 09:19:58 ack kaz 09:22:14 Kaz: W3C has a test facility but your platform can extend our infrastructure. Hope it can be integrated. 09:23:35 Cesar Viho: we need to study how the integration would be possible. But we offer a complete platform 09:23:41 ack dsr 09:24:09 joerg has joined #wot 09:24:09 Dave: I need a need for work on understanding what kinds of instrumentation hooks are needed for Web of Things servients to support higher level testing. This sounds like it would need coordination with your group if we are to be able to integrate with your framework. How do you see such a collaboration working? 09:24:14 olivexu has joined #wot 09:24:24 q+ 09:24:32 s/Cesar Viho:/Cesar_Viho:/g 09:24:32 Hyunjin has joined #wot 09:25:01 Federico: we are open for colaboration, let us talk. 09:25:27 s/need a need/see a need/ 09:26:51 Joerg: proposes to set up few simple tests from our existing test suit. 09:28:13 Cesar Viho: agrees with the propsoal. 09:28:49 sebastian: how to enable tests for small devices, microcontrollers w.r.t. authentication etc. 09:29:28 kotakagi has joined #wot 09:29:34 Federico: the authentication is needed, but we will find a way to make it working for small devices too. 09:30:13 ddahl has joined #wot 09:31:09 kotakagi has joined #wot 09:31:41 Joerg: thanks, we will organize a follow up. 09:32:04 Joerg: coffee break. WE will continue at 11:00. 09:33:16 JonathanJ has joined #wot 09:40:38 rrsagent, create minutes 09:40:38 I have made the request to generate http://www.w3.org/2016/09/23-wot-minutes.html DarkoAnicic 09:44:48 ddahl has joined #wot 10:02:09 dsr has joined #wot 10:02:21 mdadas has joined #wot 10:04:01 zkis has joined #wot 10:04:59 kaz has joined #wot 10:05:11 uday has joined #wot 10:05:14 JonathanJ has joined #wot 10:05:28 rrsagent, draft minutes 10:05:28 I have made the request to generate http://www.w3.org/2016/09/23-wot-minutes.html kaz 10:06:00 ryuichi has joined #wot 10:07:00 UNI Overware to Map the Real World to the Cyber World by Yuki: 10:07:18 ahaller2 has joined #wot 10:07:30 ->https://www.w3.org/WoT/IG/wiki/images/e/ee/DemoScriptForLisbon20160922%28WotPUB%29.pdf 10:09:30 yuki: UNI Universal natural Interface, not only develops logic to IoT but also interface 10:11:04 Yuki: UNI projects real world onto cyber world 10:11:42 tripu has joined #wot 10:12:11 UNI product descriptions 10:12:41 s/UNI Overware/topic: UNI Overware/ 10:13:26 yam has joined #wot 10:13:42 address mapping of real world ip devices to UNI addresses 10:14:47 basic structure of vertex discussed 10:15:38 Hyunjin has joined #wot 10:15:40 oVo - represents everything as vertex in graph data 10:16:02 rrsagent, draft minutes 10:16:02 I have made the request to generate http://www.w3.org/2016/09/23-wot-minutes.html kaz 10:16:28 oVo briefly dscribed 10:16:34 i/UNI Overware/[ morning break ]/ 10:16:35 rrsagent, draft minutes 10:16:35 I have made the request to generate http://www.w3.org/2016/09/23-wot-minutes.html kaz 10:17:02 i/UNI Universal/scribenick: uday/ 10:17:06 rrsagent, draft minutes 10:17:06 I have made the request to generate http://www.w3.org/2016/09/23-wot-minutes.html kaz 10:17:24 oVo- 32 byte ID 16bytes for UNI ID+ 16 Bytes for IPv6 adress of host 10:18:18 ovo is like apointer to memory 10:19:07 UNI software landscape presented 10:19:30 noifd is interface to kernel application 10:20:45 for WoT servient a new service can be implemented above the noifd 10:21:32 associations between UNI and outside UNI discussed 10:21:52 main customers are in healthcare and medical sectors 10:23:08 UNI system can communicte to external services over WoT interfaces, but currently they dont have it 10:23:20 but would like to implement in coming months 10:23:41 UNi system could run WoT script on UNI system 10:24:00 supports may languages and interfaces 10:24:52 all binary is stored in integrated server 10:26:02 sebastian has joined #wot 10:26:05 UNI system demonstrated 10:27:24 Demo scenario: connect devices to UNI n/w with UNI UPnP 10:27:38 play song in multiple rooms 10:29:40 real time demo of network buldup 10:32:35 real time connection of new vertices 10:35:22 olivexu has joined #wot 10:36:26 can play media on any device in the network 10:38:06 also gathers context and modifies play list accordingly 10:38:56 rrsagent, draft minutes 10:38:56 I have made the request to generate http://www.w3.org/2016/09/23-wot-minutes.html kaz 10:40:04 next steps: going to implement WoT interface 10:40:12 join next plug fest 10:40:39 Q1 2017- UNI peripherals SDK release 10:41:44 in design phase of other products- UNI ZMOT 10:42:01 UNI home server in design 10:42:23 Jorg: thanks yuki 10:42:48 sebastian: do you rely on existing ontology or do you define new one 10:43:14 yuki: can use existing semantic but user can add new 10:43:18 sam has joined #wot 10:43:19 q+ 10:43:32 ack seb 10:43:37 q+ johannes 10:45:05 Johannes: what are different interfaces about 10:45:39 yuki: we have a translator ot the graph layer 10:47:07 johannes: is XPIF translated to any other protocol 10:48:23 yuki: explains path to talk between devices 10:49:02 yuki: internally there is own protocol but can have any external protocol 10:49:07 ack jo 10:49:31 Yuki: UNI has some part of propreitary 10:50:04 Kaz: Questions life cycle management of cyber mapping 10:50:43 ack kaz 10:51:00 yuki: have mechanism to update data itself, so easy to maintain for clients 10:51:30 Joerg: thanks, need follow up on this and good for plugfest activity 10:52:09 yuki: will implement WoT interface and would like to join next plugfest 10:52:57 Joerg: is interfacing vis OIC for protocol mapping possible? 10:53:05 yuki: yes we could 10:54:09 kinjim has joined #wot 10:54:37 End of session 10:54:40 [ lunch till 1pm ] 10:54:47 rrsagent, draft minutes 10:54:47 I have made the request to generate http://www.w3.org/2016/09/23-wot-minutes.html kaz 10:57:33 JonathanJ has joined #wot 11:05:35 olivexu_ has joined #wot 11:08:31 zkis has joined #wot 11:30:05 cabo has joined #wot 11:32:08 tripu has left #wot 11:51:51 Tomoyuki has joined #wot 11:57:35 joerg has joined #wot 11:59:37 taki has joined #wot 12:00:14 masato has joined #wot 12:00:43 dsr has joined #wot 12:03:53 kaz has joined #wot 12:06:37 katsu has joined #wot 12:06:45 ryuichi has joined #wot 12:08:44 yingying has joined #wot 12:09:10 uday has joined #wot 12:09:33 yam has joined #wot 12:09:44 JonathanJ has joined #wot 12:09:54 yingying_ has joined #wot 12:10:57 zkis has joined #wot 12:10:58 mmiya has joined #wot 12:12:53 q+ who is scribing? 12:13:54 ddahl has joined #wot 12:16:13 topic: PlugFest Preparation 12:16:20 scribenick: kaz 12:16:39 jwehrman has joined #wot 12:17:21 how to enter the PlugFest is not clear 12:17:49 mk: good to have strategy 12:17:50 domguinard has joined #wot 12:18:28 sebastian has joined #wot 12:18:28 ... need to skim all the resources and see if need to update 12:21:30 ... we could improve communication 12:26:17 Preparation feedback: 12:26:29 - How to enter the plugfest not clear 12:26:50 - simpler to find the plugfest page for impleenters as landing page 12:27:15 - plugfest does not look in the Web as awsome as it looks in the clear structure in real 12:27:36 - The WoT Pitstop (e.g., Coap.tech) 12:27:43 joerg: volunteers? 12:28:41 EVRYTHNG would volunteer for that 12:28:57 sam has joined #wot 12:29:20 s/impleeenters/implementers/ 12:29:40 s/impleenters/implementers/ 12:31:41 mk: how/where to publish things? 12:31:50 ... would be better to have some official server? 12:35:06 ahaller2 has joined #wot 12:35:22 jh: could host a gh-pages branch 12:35:38 dom: pretty easy 12:36:32 joerg: who would take the challenge for this idea? 12:36:39 ... Dom and Johannes? 12:36:41 Yuki_Matsuda has joined #wot 12:37:05 dsr has joined #wot 12:37:59 ahaller2 has joined #wot 12:38:45 mk: bringing our own wifi router would be easier 12:39:40 joerg: move forward to the technical topics 12:39:55 ying_ying has joined #wot 12:40:19 seba: maybe would make sense to restructure the Thing Description 12:40:49 mk: maybe Events and Subscriptions 12:41:32 ... monitoring, canceling, update as well 12:42:07 s/maybe/Experiment with Actions, / 12:42:21 dsr: lifecycle concerns 12:42:40 kaji: depends on the demo scenario 12:43:07 jwehrman has joined #wot 12:43:20 ... Thing Lifecycle topic should be included in the "Scenarios" section 12:44:31 jh: would make the preparation easier with PlugFest Buddy for new articipants 12:44:38 s/articipants/participants/ 12:45:13 dom: next step for complexity? 12:45:19 joerg: proposal? 12:45:27 s/proposal/what is your proposal/ 12:45:28 DarkoAnicic has joined #wot 12:45:38 present+ DarkoAnicic 12:45:44 dom: we have lights and so on and they talk with each other 12:46:06 mk: what kind of interaction should be included? 12:46:21 dom: make sense to discuss the scenario as the group 12:47:12 ... beyond the device, there is a strong concept of connecting with larger ecosystem like social network 12:47:42 ... brainstorming on the scenario? 12:48:04 joerg: adds: bringing things to the Web. What could be a fancy one? 12:48:48 mk: Daniel has a robot. maybe would fit with the scenario 12:48:58 seba: should consider security more 12:50:14 Karen has joined #wot 12:50:44 joerg: adds: restart security scenario based on the Nice PlugFest 12:50:59 ... non repository-based TD scenario 12:51:06 mk: discovery API 12:52:24 jh: yes, discovery would be appealing 12:53:11 mk: maybe we could move one script API from a servient to another one 12:54:23 joerg: adds: existing/potential/upcoming runtime implementations: TNO, Siemens, Intel, Fujitsu 12:55:20 jh: we might want to brainstorm this 12:56:01 ... can join the plugfest by accessing a Web page, etc. 12:56:24 joerg: what about protocol mapping? 12:57:15 mk: proposals started but people are busy 12:57:40 ... maybe Panasonic and Fujitsu could work on Echonet Lite? 12:57:55 ... to restart the protocol work 12:58:50 ... UNI also might want to join 12:59:27 yuki: wonders 12:59:55 ... probably we could work on some protocol for medical use cases 13:00:09 ... we can join the discussion on protocol binding 13:00:14 joerg: would be great 13:00:31 mk: what about Jonathan? 13:00:39 ... you sent some idea to the ML 13:01:06 jj: we can use Web browser as a universal client for IoT 13:01:50 mk: we would need Web browser vendor 13:03:12 ... TD can be loaded and rendered on a Web browser natively 13:03:20 s/can/could/ 13:03:47 rrsagent, draft minutes 13:03:47 I have made the request to generate http://www.w3.org/2016/09/23-wot-minutes.html kaz 13:04:11 joerg: ok 13:04:15 ... any other ideas? 13:04:16 (none) 13:04:48 joerg: we still have two topics 13:04:59 ... reorganization of TD structure 13:05:27 ... and synchronizing Things and Proxies 13:05:56 Andrei has joined #wot 13:06:04 darko: joint discussion with geospacial 13:06:12 joerg: ok 13:06:17 s/joerg: ok// 13:06:30 rrsagent, draft minutes 13:06:30 I have made the request to generate http://www.w3.org/2016/09/23-wot-minutes.html kaz 13:06:41 my proposal mail - https://lists.w3.org/Archives/Public/public-wot-ig/2016Sep/0032.html 13:06:44 dsr has joined #wot 13:07:03 scribenick: dsr 13:07:20 Topic: Thing description restructuring 13:07:42 Sebastian presents his proposal 13:09:00 Today we have a basic structure with the name of the thing, fields for describing how to access it, and the application interaction model (properties, actions and events) 13:09:34 -> https://github.com/w3c/wot/tree/master/proposals/td-restructuring Thing Description Restructuring 13:09:59 Maxime has joined #wot 13:10:01 https://github.com/w3c/wot/tree/master/proposals/td-restructuring 13:12:04 Sebastian: some people are unclear when to use properties or actions when you want to model something that is mutable. 13:12:41 present+ Maxime_Lefrancois(Univ._Lyon) 13:12:56 Dom: in our experience, we require properties to be read-only 13:13:11 present+ Antonio_Olmo_Titos(W3C), Philipp_Hoschka(W3C) 13:13:32 Carsten: we are not going to have some a clean world, there are going to be mutable properties 13:14:23 There will be many sequences of operations we want to support. I am in favour of unifying this somehow 13:15:30 Sebastian asks Dom for clarification on the EVRYTHNG approach 13:16:48 q+ 13:17:23 q+ 13:17:24 Carsten: in a Yang model you can say that a field is @1, but it doesn’t say how 13:17:30 kinjim has joined #wot 13:17:30 IETF YANG - https://tools.ietf.org/html/rfc6020 13:17:37 barryleiba has joined #wot 13:18:28 Matthias: I expect that there will be a demand for a richer interaction model 13:18:48 jhund has joined #wot 13:18:50 @1 = "config true" 13:19:04 s/@1/config true/ 13:19:24 s/@1/config true/ 13:20:04 q? 13:20:39 Matthias: we still have to have the synchronisation discussion 13:21:33 I see a separation between the informational and physical world 13:21:46 Dom: we use different constructs for those 13:24:14 olivexu_ has joined #wot 13:24:26 q? 13:24:28 ack d 13:24:35 q+ johannes 13:24:52 Dave: there is a broad concensus across IoT work by many groups on the utility of properties actions and events, this is about the way people think about the world 13:25:23 It has stood the test of time for the GUI paradigm 13:25:34 act ta 13:25:37 ack ta 13:26:46 Taki: I support keeping properties and actions separate, as programmers expect and understand these 13:26:57 s/concensus/consensus/ 13:27:03 q? 13:27:06 ack j 13:27:59 Johannes: there are protocols like @2 where you have the split with properties and actions. There they distinguish between the desired state and the last reported state 13:28:32 q 13:28:38 q? 13:28:45 Dave: you often don’t know the true state, only the last report of the state you have had 13:29:40 Dom: NEST also distinguishes these. 13:30:05 q? 13:31:04 q? 13:33:16 Failure is also hard to do synchronously 13:34:13 Dave: the thing description can provide synchronous checks on allowed updates, but errors may take time to report when the latency across the network and sleepy devices is involved. 13:35:26 kaji: how about generating a small team for further discussion? 13:36:03 i/kaji:/scribenick: kaz/ 13:36:33 seba: during the Sunnyvale meeting, there was the first version of TF 13:36:36 s/TF/TD/ 13:37:01 mk: do you have better ideas about the proposed interaction model? 13:37:16 Sebastian: I am not looking to collect or resolve all issues now, this is just the start of the process 13:37:36 i/Sebastian:/scribenick: dsr/ 13:38:35 Matthias: we should discuss accountability, and the ability to see who/what triggered some change, this relates to the notion of subresources 13:39:31 Sub-resources provide a means to help address distributed systems. 13:40:50 e.g. the fact that it can take time for changes to take effect 13:40:53 zkis has joined #wot 13:41:34 nimura: what is the actual Action to be implemented? 13:42:47 mk: would generate a table of expected Actions 13:44:26 q+ to note that the current representation uses an array of properties and allows multiple definitions for the same name, this feels wrong and is easily fixed 13:44:29 seba: some points here have been already touched 13:44:56 ... so far nobody has used Events 13:45:13 jh: we're still working on protocol binding 13:45:34 ... maybe not "Events" but "Event source"? 13:45:54 ... which way to be used for what? 13:46:20 ... Events, Properties, Subscription 13:46:24 q? 13:46:38 q+ dom 13:46:47 ack dsr 13:46:47 dsr, you wanted to note that the current representation uses an array of properties and allows multiple definitions for the same name, this feels wrong and is easily fixed 13:47:22 dsr: multiple definitions for the same name allowed 13:47:41 ... feels wrong and easily fixed 13:47:55 seba: container of interactions 13:48:07 ... characteristic of "@type"? 13:48:35 dom: don't fully understand the difference between Property and Event 13:48:49 q+ to query about @type and semantic types for props/actions 13:49:37 Dave: we have thirty years of widespread experience with properties, actions and events, the GUI paradigm represents huge mindshare for developers and end users alike 13:50:00 ack dom 13:50:19 ack j 13:50:19 jhund, you wanted to query about @type and semantic types for props/actions 13:50:23 +q 13:50:29 q+ 13:51:19 Karen has joined #wot 13:51:31 jh: uestion on @type and semantic types for Property and Action 13:51:56 da: what is the actual exchange in this sample? 13:52:17 seba: shows the current structure 13:52:23 ... and restructuring sample 13:52:28 q+ 13:52:59 q? 13:53:04 ack d 13:53:28 seba: @type is just an array 13:53:44 ... property and maybe event as well could be contained 13:53:51 q? 13:55:19 mf: understand your point here 13:55:33 ... but isn't there a concept model behind this proposal? 13:55:58 ... what is the concept model of TD? 13:57:08 q? 13:57:16 ack m 13:57:22 q+ zoltan 13:57:35 seba: shows the diagram on TD concept 13:58:59 q+ 13:59:08 zoltan: resource type is used for discovery with OCF 13:59:11 ack zoltan 13:59:17 q? 13:59:46 zoltan: maybe "@type" is not a good name but we need additional information for discovery 14:00:12 mk: we don; 14:00:25 s/don;/don't have good model for vocabulary/ 14:00:50 Vagner_BR has joined #wot 14:01:03 ... serialization as JSON-LD 14:01:33 q? 14:01:56 seba: this is a very big topic 14:03:22 ... proposed next step 14:03:34 ... setup Web meetings about this topic 14:03:53 ... get an agreed TD version till the end of Oct. 14:04:20 joerg: would be better to fix TD asap because it's a fundamental building block 14:04:35 mk: what's the implication for implementations? 14:04:48 ... easily extract patters? 14:05:24 q? 14:05:59 Dave: I think it is important to work on developing a rough consensus on the requirements for thing descriptions as an output to the WG, and this can be done independently of the serialisation formats 14:06:14 seba: how to organize this TD call? 14:06:15 Karen has joined #wot 14:06:26 ... separate call or part of the regular call? 14:06:56 mk: would suggest generating some initial proposal by a small group 14:07:07 ... and then bring your proposal to the main call 14:07:12 q? 14:07:30 taki: Event and Property 14:07:37 ack tak 14:07:41 ... Event is not closer as Action 14:08:30 dsr: generate requirements for TD regardless of serialization would be good input for WG 14:08:45 q? 14:08:53 rrsagent, draft minutes 14:08:53 I have made the request to generate http://www.w3.org/2016/09/23-wot-minutes.html kaz 14:09:19 topic: Synchronizing Things and Proxies, Protocol Mapping 14:09:55 mk: we've already heard about Property, Action and Event 14:10:22 ... missing people for Bluetooth low energy 14:10:59 ... volunteers on HTTP: Johannes, Panasonic 14:11:08 ... CoAP 14:11:22 zoltan: Node.js based and browser based 14:11:40 mk: can join PlugFest? 14:11:51 zoltan: Michale Koster has generated a demo 14:12:05 mk: I've created Bacnet demo 14:12:27 ... different protocols to be handled 14:12:49 ... I can provide some experience on Bacnet 14:12:55 ... Lemonbeat as well? 14:13:34 mk: Louay working on Homekit 14:13:47 q+ 14:14:07 mk: would have a new placeholder 14:14:13 dom: zigbee 14:14:20 q- 14:14:36 ... interested in how to implement demos 14:14:48 mk: flexible structure of resources 14:15:03 ... firstly we write demos manually 14:15:37 ... for Bacnet there is a domain specific ontology 14:15:48 ... you could implement clusters 14:15:58 ... first manually and second automation 14:16:06 ... Zigbee is good 14:16:26 dom: Zigbee and Bluetoogh 14:16:31 Yuki_Matsuda has joined #wot 14:17:01 mk: sometimes you don't need discovery since everything is there 14:17:18 dom: our gateway convert these protocols 14:17:35 mk: offline conversion is interesting 14:17:41 s/convert/converts/ 14:17:49 mk: welcome to the TF :) 14:18:11 ... your name to be included 14:18:23 dsr: could we have better public pages? 14:18:36 mk: improvement of the current practice document 14:18:46 ... main thing I'd like to work on 14:19:21 s/public pages/public pages with a view to inviting help from protocol experts/ 14:19:49 dom: specification for the payload? 14:19:57 mk: can use content-type 14:21:08 seba: MQTT is one of the popular protocols for IoT 14:21:40 ... MQTT people should also involved? 14:22:45 mk: OCF or OneM2M is an example 14:23:53 (some more discussion on liaisons) 14:24:16 mk: there is nobody here who uses MQTT for products 14:24:23 dom: we use MQTT for products 14:24:36 mk: what do you connect with MQTT 14:24:42 s/MQTT/MQTT?/ 14:25:02 dom: from the cloud or gateway, easier to use WebSocket 14:25:37 mk: having a starting point would be good 14:26:17 q? 14:27:49 mk: who provides MQTT solution? 14:28:01 ... customers already have MQTT? 14:28:02 q+ 14:28:12 frank: project collaboration 14:28:41 q? 14:28:58 ohsumi has joined #wot 14:29:18 mk: it's beyond our Charter but bridging with MQTT would be interesting 14:30:20 this is what I meant as you can specify the sub-protocol, as the as part of the original handshake: Sec-WebSocket-Protocol: mqtt, wamp (for instance) 14:30:26 jh: maybe we could come up with a proposal to involve MQTT people? 14:30:40 https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API/Writing_WebSocket_servers 14:30:54 ack jhund 14:31:07 dsr: there are many sub protocols 14:31:20 We do have mqtt protocol binding work in progress, is this different? 14:31:23 ... exploration by the IG would be useful 14:31:58 mk: any other comments? 14:32:21 (none) 14:32:55 topic: Synchronization of WoT Servients 14:33:27 matsu: discussion on deployment of WoT systems during the Montreal meeting 14:34:35 ... (shows the Architecture document: http://w3c.github.io/wot/architecture/wot-architecture.html ) 14:34:50 ... 5.4 WoT servient on Cloud Server 14:35:09 ... (goes back to the slides) 14:35:15 ... Background 14:35:37 Karen has joined #wot 14:36:01 ... synchronization between multiple WoT Servents is required in some conditions 14:36:34 ... WoT Servients has resources corresponding to devices 14:36:46 ... Synchronie WoT Servients 14:36:58 ... message handling 14:38:56 ... two kinds of virtual devices: original one and shadow of that 14:39:11 ... Control actual device from App script 14:39:45 ... Handle event from actual device 14:41:06 ... when the legacy device generates an Event, the original device gets synchronized with the shadow 14:41:11 ... What should we do next? 14:41:27 ... how to search original devices on GW from the cloud 14:41:56 ... how to synchronize device resources between WoT Servients 14:42:05 ... how to communicate via firewall between the Gateway and the Cloud 14:42:21 ... also hsould consider how to handle time critical devices from the cloud 14:42:26 s/hsould/should/ 14:42:28 q? 14:42:32 q+ dsr 14:42:34 ack d 14:43:08 dsr: worth discussion on time-critical synchronization 14:43:36 matsu: many building blocks are involved here 14:43:58 mk: have quite a lot of ideas 14:44:10 Dave: I too have worked on this and have implementation experience to share 14:44:16 mk: how to proceed? 14:44:18 I have had good results using a pattern like subscription with MQTT transport to synchronize state between gateways and multiple cloud servers 14:45:09 matsu: would prioritize the domains 14:45:40 ... there are many companies in PlugFests 14:45:57 ... could be a target for the next PlugFest 14:46:01 q? 14:46:07 q+ johannes 14:46:08 ack j 14:46:27 jh: the question is how to describe the situation? 14:46:41 ... what if there are 100s of devices? 14:47:02 ... might want to think about early prototypes 14:47:19 ... for one of the future PlugFest 14:47:36 matsu: 1000s of devices are possibly connected 14:47:59 ... smart house includes many devices in it 14:48:38 ... some kind of abstraction would be needed 14:48:55 jh: you have one thing and a shadow 14:49:02 ... could be for multiple devices? 14:49:26 matsu: it's another issue 14:49:45 mk: we have different building blocks 14:50:07 ... shadow replacing an actual device 14:50:25 ... and a shadow app on the cloud 14:50:43 ... kind of like the Microsoft architecture 14:50:45 this is how a lot of cloud services work today 14:51:01 the interaction is with the shadow 14:51:08 matsu: yeah, there are similar approaches 14:51:11 which is a proxy for the device 14:51:33 dsr: you have a gateway, cloud and application server 14:51:38 ... a long proxy chain 14:51:42 THe app may noe ever know the device address 14:51:48 ... definitely interesting to discuss 14:51:56 s/The/The/ 14:52:31 Karen has joined #wot 14:52:52 s/noe/not 14:52:58 yuki: question on proxy vs actual servient 14:53:23 ... many proxies can correspond to multiple servients 14:53:53 rrsagent, draft minutes 14:53:53 I have made the request to generate http://www.w3.org/2016/09/23-wot-minutes.html kaz 14:54:22 mk: Matsukura-san, could you organize a call for participation for this topic? 14:54:24 matsu: yes 14:54:47 joerg: great discussions for this afternoon 14:54:56 ... tx for the staff's supports 14:55:18 ... demonstrations and joint discussions during this week 14:55:31 ... organizational topics as well 14:55:45 ... tx for the staff 14:55:49 (our pleasure :) 14:55:55 s/staff/staff again/ 14:56:40 joerg: and tx again for all your supports! 14:57:22 cabo: IRTF meeting Saturday/Sunday 14:57:34 s/IRTF/IRTF joint/ 14:58:04 ... some of the discussions from this WoT IG meeting would be handled 14:58:22 s/would be handled/will be handled there/ 14:58:35 joerg: tx again and have a safe trip back home! 14:58:39 cabo has joined #wot 14:58:41 [ meeting adjourned ] 14:58:48 rrsagent, draft minutes 14:58:48 I have made the request to generate http://www.w3.org/2016/09/23-wot-minutes.html kaz 14:59:04 ddahl has left #wot 15:13:03 JonathanJ has joined #wot 15:15:38 JonathanJ has joined #wot 15:19:35 barryleiba has left #wot 15:22:13 rrware has joined #wot 16:09:26 dsr has joined #wot 16:37:37 dsr has left #wot 19:52:09 cabo has joined #wot 20:13:27 cabo has joined #wot 20:44:43 jungbin has joined #wot 21:13:24 Karen has joined #wot 21:16:53 ahaller2 has joined #wot 21:45:50 ahaller2 has joined #wot 22:12:16 ahaller2 has joined #wot