12:06:30 <RRSAgent> RRSAgent has joined #wot
12:06:30 <RRSAgent> logging to http://www.w3.org/2016/06/01-wot-irc
12:07:17 <kaz> kaz has joined #wot
12:07:30 <sebastian> sebastian has joined #wot
12:09:00 <Zakim> Zakim has joined #wot
12:09:06 <kaz> zakim, pick a scribe
12:09:06 <Zakim> I don't who is present, kaz
12:09:54 <kaz> present+ Kaz, Dave, Michael, Achille, Daniel, Katsuyoshi, Sebastian, Joerg, Johannes, Kazuaki, Masato, Matthias, Ryuichi, Takuki, Toru, Victor, Yingying, Yun
12:09:58 <kaz> zakim, pick a scribe
12:09:58 <Zakim> Not knowing who is chairing or who scribed recently, I propose Toru
12:10:23 <victor> victor has joined #wot
12:10:23 <sebastian> present+ Sebastian_Kaebisch
12:10:35 <kaz> zakim, pick a scribe
12:10:35 <Zakim> Not knowing who is chairing or who scribed recently, I propose Daniel
12:10:49 <dape> scribe: dape
12:10:55 <dape> scribeNick: DP
12:11:17 <dape> TOPIC: Quick Status Updates
12:11:27 <dape> MK: Any quick issue?
12:11:43 <dape> .. none heard
12:11:50 <dape> TOPIC: F2F Beijing
12:11:58 <michael> michael has joined #wot
12:12:03 <kaz> Agenda: https://www.w3.org/WoT/IG/wiki/IG_WebConf#Agenda_of_next_WoT_IG_WebConf:_1_Jun_2016
12:12:10 <dape> YY: Send out information for F2F
12:12:24 <kaz> -> https://www.w3.org/WoT/IG/wiki/Main_Page#Face-to-Face_Meetings f2f wiki
12:12:42 <dape> YY: Email contains all information about registering
12:13:09 <Yingying> ->https://www.w3.org/WoT/IG/wiki/F2F_meeting,_July_2016,_China,_Beijing#Room_Reservation
12:13:11 <dape> ... please fill in form.. deadline is 24th June
12:13:23 <dape> ... there is limited number of rooms
12:13:37 <dape> ... also, please register for meeting
12:13:58 <dape> ... moreover, for VISA there is information as well on wiki page
12:14:10 <kaz> s|https://www.w3.org/WoT/IG/wiki/Main_Page#Face-to-Face_Meetings|https://www.w3.org/WoT/IG/wiki/F2F_meeting,_July_2016,_China,_Beijing|
12:14:16 <dape> ... detailed agenda for first 2 days is on wiki also
12:14:32 <jhund> jhund has joined #wot
12:14:39 <dape> MK: Any more information w.r.t network setup?
12:15:03 <dape> YY: network should be OK, no credentials needed
12:15:22 <dape> ... we still need to test our requirements
12:15:29 <dsr> with support for wifi and cabled Ethernet
12:15:31 <dape> YY: Daniel proposed test tool
12:15:44 <kaz> present+ Carsten
12:16:08 <dsr> q?
12:16:10 <dsr> q+
12:16:17 <dape> DP: will provide test tool tool
12:16:28 <kaz> s/tool tool/tool soon/
12:16:31 <dape> MK: looked into VPN as well..
12:16:48 <dape> s/MK/Koster
12:17:23 <dape> ... need to check whether VPN is possible as well? could send pre-configured RASPI
12:17:43 <dape> ... could I send the device or is it blocked?
12:18:15 <dape> YY: There are some website outside China which we can't access
12:18:46 <dape> Koster: we should check whether some webpages work as well...
12:18:49 <dape> q+
12:19:56 <dape> Koster: should have fallback... e.g., with VPN
12:20:34 <dape> MK: should also try router and connect it to the network...
12:20:42 <dape> YY: Switch?
12:20:55 <dape> MK: a basic Wifi router
12:21:35 <dape> Koster: local network maybe better also
12:21:57 <dape> https://www.w3.org/WoT/IG/wiki/F2F_meeting,_July_2016,_China,_Beijing#Requirements
12:22:12 <kaz> s|https:|-> https:|
12:22:24 <dsr> ack dsr
12:22:29 <kaz> s|Requirements|Requirements PlugFest Requirements wiki|
12:22:30 <dape> DP: should collect requirements on wiki
12:22:33 <kaz> rrsagent, make log public
12:22:36 <mkovatsc> q?
12:22:37 <kaz> rrsagent, draft mintues
12:22:37 <RRSAgent> I'm logging. I don't understand 'draft mintues', kaz.  Try /msg RRSAgent help
12:22:42 <kaz> rrsagent, draft minutes
12:22:42 <RRSAgent> I have made the request to generate http://www.w3.org/2016/06/01-wot-minutes.html kaz
12:22:53 <kaz> s|rrsagent, draft mintues||
12:23:04 <dape> DR: peer-to-peer messaging also important! Does tool handle that?
12:23:17 <dape> Koster: local network could be a solution
12:23:35 <kaz> q+
12:23:37 <cabo> cabo has joined #wot
12:24:16 <dape> DP: p2p might be more tricky...
12:24:28 <dape> YY: guideline might be good
12:25:09 <dape> Kaz: Daniel could work on guideline...
12:25:20 <dape> Daniel: Will try...
12:25:48 <dape> Kaz: Should fix requirements table as soon as possible
12:25:57 <mkovatsc> q?
12:26:10 <dape> q-
12:26:11 <mkovatsc> ack dape
12:26:17 <mkovatsc> ack kaz
12:26:48 <dape> Kaz: Soumya plans remote plugfest participation..
12:26:58 <dape> YY: will check with Soumya
12:26:59 <mkovatsc> q?
12:27:05 <kaz> s/plans/might be planning/
12:27:24 <dape> TOPIC: Architecture document
12:27:39 <kaz> -> http://w3c.github.io/wot/architecture/wot-architecture.html WoT Architecture
12:28:10 <dape> Toru shows Architecture document
12:28:50 <dape> Toru: document is on github and has 7 chapters
12:28:56 <dape> .... 1. introduction
12:29:01 <joerg> joerg has joined #wot
12:29:09 <dape> ... 2. Terminology
12:29:53 <dape> ... 3. chapter is about requirements... general info about flexibility, compatibiliyt, and safety
12:30:03 <dape> .. please comment if you have issues
12:30:08 <kaz> q+
12:30:15 <dape> ... 4. chapter is about scenarios
12:30:31 <dape> .... Nimurasan worked on those scenarios
12:30:48 <dape> .. inside home but also outside home
12:31:16 <dape> ... also variations whether to have home hub instead of direct connection
12:31:36 <dsr> q+ to ask about clarifying role of firewall for smart homes in the architecture
12:31:43 <dape> ... other  scenarios through proxy in cloud
12:32:27 <dape> ... other scenario is about factory and connected car ... both need gateway
12:33:02 <dape> ... finally thing-to-thing scenario (e.g, sensor to air conditioner)
12:33:17 <Karen> Karen has joined #wot
12:33:19 <dape> ... 5. chapter is about "mapping variations"
12:33:51 <dape> ... similar to 4... but more detailed behavior is explained
12:34:22 <dape> ..e.g. fig 14, between gateway and cloud
12:34:45 <dape> ...6. chapter is about WoT servient
12:35:10 <dape> ... also handles interfaces... discovery, server, ..
12:35:14 <dsr> q+ to clarify whether we expect electronic appliances to be WoT servients, or not?
12:35:24 <dape> ... also propitiatory API
12:35:38 <dape> ... 7. Conclusion
12:36:04 <kaz> q?
12:36:17 <kaz> q+ k_nimura
12:36:17 <kaz> ack k_nimura
12:36:31 <dape> Nimurasan: based on scenario section I updated use-case document..
12:36:41 <kaz> -> http://w3c.github.io/wot/wot-ucr.html Use Case document
12:36:47 <dsr> q+ to ask if we want to include sensor networks which often talked about for the IoT
12:36:54 <dape> ... I added smart home scenario
12:37:35 <kaz> q?
12:37:35 <dape> q?
12:38:15 <mkovatsc> ack kaz
12:38:20 <dape> Kaz: we should clarify relationship between use-case and architecture document
12:38:29 <dape> .. could simple merge them
12:38:46 <dape> ... or have separate documents ...
12:39:11 <dape> ... use-case scenario section should be before requirements section
12:39:41 <jhund> q+
12:40:06 <dape> ... use-cases in architecture document could go right after terminology
12:40:52 <mkovatsc> q?
12:41:00 <dape> Toru: use-cases more  user perspective while scenarios more deployment
12:43:03 <dape> Kaz: scenario should be part of use-case description.. unless it is really about deployment
12:43:19 <dape> Toru: could you make pull-request Kaz?
12:43:46 <dape> Kaz: Also, content of Section 4 should appear before requirements section
12:44:19 <kaz> s/unless it is really about deployment/if it's rather description on concrete deployed systems, the title here (which is currently "Scenarios") should be something like that (deployed system images)/
12:44:19 <mkovatsc> q?
12:44:26 <mkovatsc> ack dsr
12:44:26 <Zakim> dsr, you wanted to ask about clarifying role of firewall for smart homes in the architecture and to clarify whether we expect electronic appliances to be WoT servients, or not? and
12:44:29 <Zakim> ... to ask if we want to include sensor networks which often talked about for the IoT
12:44:56 <dape> Dave: document shows firewall...
12:45:17 <dape> ... what about smart meters ... clarify firewall role
12:46:08 <dape> .. Fig1. shows WoT Server ... WoT should show that we also support devices that not support WoT per se
12:46:31 <dape> ... lots of discussion about sensor networks...
12:46:55 <dape> ... also home health care .. where to put it, in the arch-document or use-cases?
12:47:33 <kaz> q+
12:47:39 <dape> Toru: w.r.t. scenario we don't want to exclude non WoT devices... there are just examples
12:47:57 <kaz> q+ to ask if "firewall" is really a necessarily component of the system architecture
12:48:04 <dape> Dave: could say "each example illustrates ..."
12:48:30 <dape> Toru: do you propose referencing use-case documents..
12:48:49 <dape> Dave: Yes, .. need to say why we have those scenarios and not others in arch document
12:48:57 <dsr> ack dsr
12:49:01 <mkovatsc> q?
12:49:06 <k_nimura> q
12:49:25 <kaz> q+ k_nimura
12:49:39 <dape> Johannes: use.cases speaks about domains.. while arch-document talks about deployment
12:50:04 <dape> ... need to clarify this difference
12:50:13 <dsr> we need to explain the criteria for including the examples in the architecture document, to say that we are not excluding other kinds of examples, but these are covered in the use cases document
12:50:17 <mkovatsc> q?
12:50:18 <kaz> s/use.cases/use cases/
12:50:24 <mkovatsc> ack jhund
12:50:40 <kaz> ack k
12:50:43 <kaz> ack k
12:50:43 <Zakim> kaz, you wanted to ask if "firewall" is really a necessarily component of the system architecture
12:51:01 <mkovatsc> q?
12:51:18 <dape> Kaz: wonder whether terminology "firewall" is needed.. suggest removing it
12:51:35 <dape> .. rather think about security and privacy separately.
12:52:06 <dape> Dave: IPv4 and IPv6 ... and firewall.. important for architecture..
12:52:42 <dape> Kaz: currently we have just one statement about firewall ... detailed explanation should go into dedicated section
12:52:58 <kaz> q?
12:53:25 <dsr> some possible additions include healthcare, smart meters, sensor network examples and telemetry
12:54:16 <dape> Nimurasan: Fig14 tries to show combination of servient
12:54:47 <dape> ... firewall is not tackled here... should remove it
12:55:06 <dape> Torusan: can remove "firewall" here
12:55:25 <dape> Kaz: need more information somewhere else
12:55:44 <dape> Dave: Also IPv4, IPV6 issues et cetera
12:56:19 <dape> Dave: who are we targeting with this document?
12:56:36 <taki> q+
12:56:39 <dape> ... technical audience. not sure.. not enough technical details
12:56:45 <kaz> present+ Kazuo
12:57:18 <kaz> kaz: would suggest we talk with Kajimoto-san :)
12:57:20 <dape> Kaijmoto: security is important
12:58:42 <k_nimura> q
12:58:43 <mkovatsc> q?
12:58:43 <dape> .. we should add deliverable to WG ... continue to discuss it in WG
12:58:46 <mkovatsc> q+
12:58:54 <kaz> q+ k_nimura
12:59:23 <dape> Kaijmoto: Security seems an endless issue
12:59:24 <michael> I need to drop off for board meeting, thanks
12:59:57 <dape> Dave: yes, but people will look at W3C how we handle it
13:00:11 <kajimoto> kajimoto has joined #wot
13:00:11 <dape> ... agree, we don't need to handle it in this document
13:00:23 <mkovatsc> q?
13:00:31 <dsr> I agree that we don’t need to handle security and privacy in this document, at least not now
13:00:51 <mkovatsc> ack taki
13:01:21 <dape> Taki: order of chapters: definition of WoT serviant in terminology section.. in section 6 the details are given
13:01:38 <dape> ... information should come earlier
13:02:18 <dape> Toru: I agree
13:02:27 <dape> Kaijmoto: makes sense
13:02:49 <dape> Taki: will create issue or PR
13:03:33 <mkovatsc> ack
13:03:39 <mkovatsc> q?
13:03:44 <dape> MK: level of details is OK... more should come later... maybe in other WG document
13:03:49 <mkovatsc> ack m
13:04:35 <dape> Nimurasan: propose closing document in IG... and work in WG again
13:05:13 <dape> MK: yes, plan to release document soon...
13:05:30 <dape> s/plan/we plan
13:05:32 <mkovatsc> q?
13:06:01 <dape> MK: please add issues to github... so that editors can work on the final comments...
13:06:10 <dape> .... release planned for mid of June
13:06:27 <dape> TOPIC: Current Practices document
13:06:43 <dape> MK: Johannes updated scripting API
13:06:52 <kaz> -> http://w3c.github.io/wot/current-practices/wot-practices.html current practices document
13:07:05 <dape> ... also talked with Sebastian... w.r.t. to new type system
13:07:12 <kaz> q+
13:07:22 <kaz> ack k_nimura
13:07:23 <kaz> ack k
13:07:26 <dape> MK: are there any issue / comment w.r.t. to this document?
13:08:17 <dape> Kaz: got MMI wg request? Should we have github PRs?
13:08:38 <dape> MK: Yes, can discuss PR?
13:08:49 <dape> .. direct commit should be avoided
13:09:18 <dape> MK: fixed critical issues in charters
13:09:25 <dape> .. no todos left
13:09:36 <dape> .. think ready to share with others
13:09:57 <kaz> i/fixed critical/topic: Charters/
13:10:23 <dape> ... one remaining issue: missing text for figure (relation between WG and IG)
13:10:32 <kaz> -> http://w3c.github.io/wot/charters/wot-ig-2016.html draft IG Charter
13:10:37 <kaz> -> http://w3c.github.io/wot/charters/wot-wg-2016.html draft WG Charter
13:10:54 <dape> ... we have figure in IG charter... and we have also text there
13:11:09 <dape> ... should we have text in WG charter as well
13:11:39 <dape> Dave: Payment wg had similar issue... lets refer from WG to IG text
13:11:42 <dape> MK: Will do so..
13:11:46 <kaz> s/as well/as well?/
13:12:29 <dape> ... IG charter issue: test interoperability issue (discussion on mailinglist)
13:12:43 <dsr> Is the following “take part in interoperability experiments across implementations for ideas at different levels of maturity”
13:12:57 <dape> Dave: Jonathan wanted some explanation..
13:13:11 <dape> Dave: is the proposed text OK?
13:13:24 <dape> MK: Good for me
13:13:39 <kaz> q+
13:13:44 <dape> Dave: will reach out to Jonathan and check
13:14:23 <dape> Dave: plan to show IG charter next Wednesday.. make comments quickly..
13:14:32 <kaz> q?
13:14:33 <mkovatsc> q?
13:14:45 <mkovatsc> ack kaz
13:15:22 <dape> Kaz: there are 2 locations IG charter mentions testing... should try to converge on mailinglist
13:15:48 <dape> MK: we still take comments... this might be still revised
13:15:56 <mkovatsc> q?
13:16:09 <dape> TOPIC: Proposals
13:16:23 <jhund> aq+
13:16:34 <dsr> q+
13:17:06 <dape> Johannes: proposed scripting API updates...
13:17:24 <jhund> https://github.com/w3c/wot/issues/173
13:17:43 <kaz> s|https|-> https|
13:17:51 <dape> .. plan is to discuss it on Github.. will merge later in Current Practices document
13:18:05 <jhund> https://github.com/w3c/wot/tree/master/proposals/restructured-scripting-api
13:18:08 <dape> ... please comment and discuss
13:18:10 <kaz> s|173|173 Issue on Structure/concretisation of the Scripting API|
13:18:30 <kaz> s|https:|-> https:|
13:18:51 <kaz> s|scripting-api|scripting-api actual proposal on scripting API|
13:18:57 <kaz> rrsagent, draft minutes
13:18:57 <RRSAgent> I have made the request to generate http://www.w3.org/2016/06/01-wot-minutes.html kaz
13:19:38 <dape> Dave: Last week I was in Spain... next Thursday I am talking with OPC ... about Semantics... also Industry 4.0 folks ...
13:19:43 <kaz> i/Quick Status Updates/scribenick: dape/
13:19:45 <kaz> rrsagent, draft minutes
13:19:45 <RRSAgent> I have made the request to generate http://www.w3.org/2016/06/01-wot-minutes.html kaz
13:19:56 <Yingying> q+
13:19:59 <dape> q+
13:20:09 <dsr> ack dsr
13:20:29 <kaz> Meeting: WoT IG
13:20:32 <kaz> Chair: Matthias
13:20:34 <kaz> rrsagent, draft minutes
13:20:34 <RRSAgent> I have made the request to generate http://www.w3.org/2016/06/01-wot-minutes.html kaz
13:20:44 <dape> Sebastian: Would like to see more technical discussions? PlugFest is rather soon
13:21:04 <dape> ... can we reserve some time ?
13:21:10 <dape> MK: Indeed...
13:21:22 <kaz> i/Last week/topic: AOB/
13:21:24 <kaz> rrsagent, draft minutes
13:21:24 <RRSAgent> I have made the request to generate http://www.w3.org/2016/06/01-wot-minutes.html kaz
13:21:37 <kaz> q?
13:21:40 <mkovatsc> q?
13:21:47 <mkovatsc> ack Yingying
13:22:28 <dape> Yingying: for F2F meeting: CETC would like to give some demos... can we have a slot for this as well
13:22:39 <dape> ... would like to explain demo
13:23:07 <dape> ... 15th of June could be a good date..
13:23:57 <kaz> s/this as well/this as well?/
13:25:08 <mkovatsc> Bryan Sullivan of AT&T
13:25:48 <dape> Yingying: should get in touch with Bryan Sullivan... will try to give a presentation
13:26:43 <dape> Dave: Yes... should get updates from OMA and other groups as well
13:27:12 <dape> Dave: How do we manage it?
13:27:26 <kaz> -> https://lists.w3.org/Archives/Public/public-wot-comms/2016Feb/0006.html wot comm mintues
13:27:41 <dape> Joerg: Need to understand how to incorporate it topic-wise
13:28:00 <dape> ... we need context (discussed also before)
13:28:59 <dape> ... need person(s) who takes care of each liaison
13:29:33 <mkovatsc> q?
13:29:37 <dape> Dave: let's discuss this during next comm call
13:29:53 <mkovatsc> ack dape
13:31:13 <dape> DP: wanted to talk about "call for implementations" .. will do next week
13:31:57 <kaz> [ adjourned ]
13:32:00 <kaz> rrsagent, draft minutes
13:32:00 <RRSAgent> I have made the request to generate http://www.w3.org/2016/06/01-wot-minutes.html kaz
13:54:59 <dsr> dsr has joined #wot
14:27:24 <dsr> dsr has joined #wot
15:22:48 <dfr> dfr has joined #wot
15:52:21 <kaz> kaz has joined #wot
15:58:22 <Zakim> Zakim has left #wot
16:30:16 <dsr> dsr has joined #wot