W3C home > Mailing lists > Public > public-wot-wg@w3.org > August 2020

[Scripting] minutes - 10 August 2020

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Tue, 18 Aug 2020 12:44:59 +0900
Message-ID: <87r1s4d3d0.wl-ashimura@w3.org>
To: public-wot-wg@w3.org
available at:
  https://www.w3.org/2020/08/10-wot-minutes.html

also as text below.

Thanks a lot for taking the minutes, Zoltan!

Kazuyuki

---
   [1]W3C

      [1] http://www.w3.org/

                               - DRAFT -

                           WoT Scripting API

10 Aug 2020

Attendees

   Present
          Kaz_Ashimura, Cristiano_Aguzzi, Daniel_Peintner,
          Zoltan_Kis, Tomoaki_Mizushima

   Regrets

   Chair
          Zoltan

   Scribe
          zkis

Contents

     * [2]Topics
         1. [3]Quick updates
         2. [4]Past minutes
         3. [5]Issue 230
         4. [6]Ege's feedback in PDF for issue 230
         5. [7]Issue 228 - wot issue 235
         6. [8]Issue 227 - wot issue 233
         7. [9]Issue# 224
         8. [10]Next meeting
     * [11]Summary of Action Items
     * [12]Summary of Resolutions
     __________________________________________________________

   <scribe> scribe: zkis

Quick updates

   Kaz: some info from the main call last week
   ... we had several events and some of them, e.g., MiniApps,
   would possibly be related to Scripting improvements

   Zoltan: do we have issues for these?

   Kaz: no GitHub issues have been created but we'll invite some
   of the contact persons to one of the WoT main calls and/or the
   TPAC joint meeting

   <kaz> [13]August-5 Main call minutes

     [13] https://www.w3.org/2020/08//05-wot-minutes.html

   <kaz> [14]TPAC vF2F wiki

     [14] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_October_2020

   Kaz: I suggested to have a joint meeting on use cases first,
   before any API changes

Past minutes

   <kaz> [15]July-27 minutes

     [15] https://www.w3.org/2020/07/27-wot-minutes.html

   Approved

Issue 230

   <kaz> [16]Issue 230

     [16] https://github.com/w3c/wot-scripting-api/issues/230

   Daniel: we should use the dated version of TR links

   Kaz: W3C encourages using dated versions

   Zoltan: I don't see the value of making a release just because
   some other documents changed

   Cristiano: I would also prefer the dated URLs for reference
   purposes
   ... I can also see the point in using the latest TR version

   Zoltan: the publication checker anyway needs the dated URL
   versions

   RESOLUTION: we change all referred URLs to dated versions

   [17]https://en.wikipedia.org/wiki/Plugtest#:~:text=A%20plugtest
   %20or%20plugfest%20is,with%20those%20of%20other%20manufacturers
   .

     [17] https://en.wikipedia.org/wiki/Plugtest#:~:text=A plugtest or plugfest is,with those of other manufacturers.

   Zoltan: we can use the word "plugfest" or "plugtest"

Ege's feedback in PDF for issue 230

   <kaz> [18]Ege's comments in PDF

     [18] https://github.com/w3c/wot-scripting-api/files/5017322/ScriptingAPI-review-egekorkan.pdf

   Zoltan: would prefer comments in github as it's difficult to
   spot the issues

   Daniel: maybe we should split and create PR's or issues

   Cristiano: I can also help in this

   Zoltan: OK, then we can split the work

   Daniel: will include a comment in the issue on the split

Issue 228 - wot issue 235

   Cristiano: these are coming from other TF discussions

   <kaz> [19]wot-scripting issue 228

     [19] https://github.com/w3c/wot-scripting-api/issues/228

   <kaz> [20]wot issue 235

     [20] https://github.com/w3c/wot/issues/235

   Zoltan: we need to make the explanation explicit
   ... meaning to update the rationale.md
   ... we can also link the issue that have been discussing the
   topic

Issue 227 - wot issue 233

   <kaz> [21]wot-scripting issue 227

     [21] https://github.com/w3c/wot-scripting-api/issues/227

   <kaz> [22]wot issue #233

     [22] https://github.com/w3c/wot/issues/233

   Zoltan: let's leave these issues (228 and 227) open, they have
   been discussed in the past as well

Issue 224

   <kaz> [23]Issue 224

     [23] https://github.com/w3c/wot-scripting-api/issues/224

   Cristiano: we can add the version property of the WOT object
   ... also discussed in the TD TF, and they suggested looking at
   the JSON-LD group's handling of versioning

   Daniel: we also tried to keep the version info in node-wot, and
   it should be the same

   Daniel is adding a comment

   Cristiano: also, how can we connect the spec version with the
   implementations and Web IDL

   Zoltan: we should declare the version in the spec text, and
   include links in the spec to past versions

   Daniel: we can also flag in the text (without changing the API)

   Zoltan: I can create a PR on this

Next meeting

   <dape>
   [24]https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf
   #Agenda

     [24] https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#Agenda

   Zoltan: will publish the agenda

   [adjourned]

Summary of Action Items

Summary of Resolutions

    1. [25]we change all referred URLs to dated versions

   [End of minutes]
     __________________________________________________________


    Minutes manually created (not a transcript), formatted by
    David Booth's [26]scribe.perl version ([27]CVS log)
    $Date: 2020/08/11 07:00:51 $

     [26] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [27] http://dev.w3.org/cvsweb/2002/scribe/
Received on Tuesday, 18 August 2020 03:45:03 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 18 August 2020 03:45:04 UTC