- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Thu, 8 Nov 2018 00:36:47 +0900
- To: Public Web of Things IG <public-wot-ig@w3.org>, public-wot-wg@w3.org
available at: https://www.w3.org/2018/11/07-wot-minutes.html also as text below. Thanks a lot for taking these minutes, Michael Koster! Kazuyuki --- [1]W3C [1] http://www.w3.org/ - DRAFT - WoT-IG/WG 07 Nov 2018 Attendees Present Kaz_Ashimura, Michael_McCool, Taki_Kamiya, Toru_Kawaguchi, Dave_Raggett, Michael_Koster, Tetsushi_Matsuda, Daniel_Peintner, Sebastian_Kaebisch, Tomoaki_Mizushima, Zoltan_Kis, Michael_Lagally, Kunihiko_Toumura, Takeshi_Yamada Regrets Chair McCool Scribe mjkoster Contents * [2]Topics 1. [3]Agenda 2. [4]Welcome Michael Koster from SmartThings 3. [5]Talk at IIC DDIM Task Group in Beijing 4. [6]Teleconference times 5. [7]Publication status 6. [8]TPAC report out 7. [9]WG extention and IG rechartering 8. [10]Next f2f options 9. [11]Online PlugFest 10. [12]W3C workshop on WoT 11. [13]Smart cities BG and workshop 12. [14]Agenda for testing call * [15]Summary of Action Items * [16]Summary of Resolutions __________________________________________________________ <inserted> scribenick: mjkoster Agenda Taki: DDIM task group of IIC meeting in Beijing - this group focus on semantic interoperability ... will present WoT and iot.schema.org Welcome Michael Koster from SmartThings McCool: welcome SmartThings Talk at IIC DDIM Task Group in Beijing Taki: the IIC talk is Wednesday, 25 minute talk on semantic interoperability for the industrial use case ... the group is about 3 years old but needs to learn more about existing ontologies ... using the introductory slides and SSN workshop keynote slides for the iotschema part Teleconference times Kaz: TD and Binding were to be combined and we've been holding a doodle poll to see a possible new slot, but it seems the current TD slot would be the best for everyone Sebastian: Tuesday was available but Zoltan can't make that time, is it a hard conflict? Zoltan: don't want to be the blocking factor, and Daniel can attend McCool: we will keep the existing schedule <kaz> [17]Doodle results [17] https://doodle.com/poll/xedw8gzvpanzz3a9 <inserted> Friday 4pm Japan/10am Europe/11pm-1d US Pacific vs Tuesday 10pm Japan/2pm Europe/5am US Pacific Sebastian: Tuesday is also possible since Zoltan is flexible McCool: we could have the TD meeting on Friday and discuss the Tuesday meeting at that time Publication status Kaz: TD document was published on TPAC week ... the others will be published this week TPAC report out McCool: we should go over the resolutions and actions and extract them for discussion Kaz: resolutions are extracted already but we need to get the actions McCool: can discuss actions in the next meeting ... please review the minutes and make comments, suggest changes ... we can accept them at the next meeting WG extention and IG rechartering McCool: assuming we will get a 6 month extension for WG Kaz: working with the project manager to get approval for WG extension by the end of November ... to extend the current charter with no changes McCool: regarding the new charter for IG, we are asking for a 30 month term in order to line up with the IG ... the chairs will do a first draft for the new charter ... not expecting big changes Kaz: agree, no big changes McCool: creating an issue in the wot repository for discussion on rechartering ... please use this issue for discussion <McCool> [18]https://github.com/w3c/wot/issues/594 [18] https://github.com/w3c/wot/issues/594 McCool: suggesting a feature freeze in January, based on working back from the CR dates ... we will need to work on testing and will push the CR out past January ... but April is the absolute latest date Kaz: as our initial plan, we should aim for the end of January (and February at the latest) for CR Zoltan: scripting API is likely to be a note at this point and not a CR McCool: TD is clearly the priority Lagally: we should make sure everyone understands and agrees to the prioritization being done and label the issues accordingly <mlagally> mlagally: we should also clearly mark issues that are deferred into the WoT 2.0 spec <kaz> kaz: have been suggesting we use "v.next" which is commonly used. Next f2f options McCool: we need to focus on testing for the next priority in the online plugfest and f2f meeting ... the schedule aligns with finalizing the TD and getting the CR ready Sebastian: the f2f could focus more on the spec and not as much on interoperability plugfest McCool: it may be 3 or 4 days Sebastian: looking at Siemens support January 29-31 at Princeton, NJ in the US Kaz: so we will focus the 3 days on finalizing the document having no plugfest or openday Online PlugFest McCool: online plugfest can use a repository with tests and set up a series of online meetings ... we can discuss more in the testing call W3C workshop on WoT McCool: May or June is good timing if we have the rec out by then ... or we could have it after August ... Matthias was thinking about late May ... adding another issue for WoT workshop organization Lagally: we already have some discussion started and captured from Friday during the f2f in Lyon <McCool> [19]https://github.com/w3c/wot/issues/595 [19] https://github.com/w3c/wot/issues/595 Smart cities BG and workshop McCool: also need to avoid July and August and it takes 6 months to organize, so it will be later in the year ... will share the slides soon ... WWW2019 is in San Francisco in May which could be an opportunity for co-location Kaz: has a contact for coordination with WWW2019 Agenda for testing call McCool: that's the agenda for todays meeting, any other topics? ... discuss the timeline for testing ... need to complete the plugfest reports ... need to define the requirements ... thinking about making a reporting tool ... any other topics to discuss? ... what about the meeting time? should we shift the testing call to not be after the main call? ... what about online plugfest? we need to do pentesting which requires LAN/VLAN ... should we have a separate repo or leave it under wot? ... any other topics? Dave: the test demo which was not done at TPAC ... and discuss how we will collect the results Kaz: those points like tooling should be discussed later. we need to discuss the initial planning first, maybe a google document to start to handle initial implementation results McCool: we can discuss in the meeting ... meeting adjourned Summary of Action Items Summary of Resolutions [End of minutes] __________________________________________________________ Minutes manually created (not a transcript), formatted by David Booth's [20]scribe.perl version 1.154 ([21]CVS log) $Date: 2018/11/07 15:12:17 $ [20] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [21] http://dev.w3.org/cvsweb/2002/scribe/
Received on Wednesday, 7 November 2018 15:37:49 UTC