[Scripting] minutes - 29 November 2021

available at:
  https://www.w3.org/2021/11/29-wot-script-minutes.html

also as text below.

Thanks a lot for taking the minutes, Zoltan!

Kazuyuki

---
   [1]W3C

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

                           WoT Scripting API

29 November 2021

   [2]Agenda. [3]IRC log.

      [2] https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#29_November_2021
      [3] https://www.w3.org/2021/11/29-wot-script-irc

Attendees

   Present
          Cristiano_Aguzzi, Daniel_Peintner, Kaz_Ashimura,
          Tomoaki_Mizushima, Zoltan_Kis

   Regrets
          -

   Chair
          Daniel

   Scribe
          zkis

Contents

    1. [4]past minutes
    2. [5]PRs
         1. [6]move section "Terminology and conventions" right
            after "Conformance"
    3. [7]Issues
         1. [8]issue 355
         2. [9]Conformance section necessity

Meeting minutes

  past minutes

   <dape> [10]Nov-22

     [10] https://www.w3.org/2021/11/22-wot-script-minutes.html

   past minutes approved

  PRs

    move section "Terminology and conventions" right after "Conformance"

   <dape> [11]PR 353 - refactor: move section "Terminology and
   conventions" right after "Conformance"

     [11] https://github.com/w3c/wot-scripting-api/pull/353

   <kaz> [12]11. Terminology and conventions

     [12] https://w3c.github.io/wot-scripting-api/#terminology-and-conventions

   Zoltan: nowadays we can remove a lot of duplicated references
   from terminology

   Cristiano: agree to remove all non-WoT related terminology -
   just use links

   Zoltan: let's use ReSpec and Bikeshed web platform cross
   referencing, include link to README

  Issues

    issue 355

   <dape> Rename Use Cases section, [13]https://github.com/w3c/
   wot-scripting-api/issues/355

     [13] https://github.com/w3c/wot-scripting-api/issues/355

   Zoltan: other web specs are using Use Case section, it is
   related to Scripting API use cases

   Kaz: we can change the name of the section to something like
   "expected features"
   … the Scripting editors can make a decision

   Cristiano: not attached to the term Use Cases, but it's clear
   they mean the use cases for the Scripting API
   … if other specs are using this structure, we should adhere to
   this

   Zoltan: some specs are using use cases, some others are not
   … but WoT use cases don't conflict with Scripting use cases,
   the latter are used to implement the former

   Kaz: we could rename to "Features"

   Daniel: no other WoT spec contain "Use Cases"

   Cristiano: could join the editors call to discuss this

    Conformance section necessity

   <dape> [14]Issue 354 - Conformance section necessity

     [14] https://github.com/w3c/wot-scripting-api/issues/354

   <cris> +1 for keeping

   Daniel: looks like we will keep it

   Kaz: as a Note, the whole document is non-normative, including
   in each section a note of not being normative would be too
   annoying

   Zoltan: WoT Scripting is optional, but in order to share code
   between implementations, it should be specified, so there
   should be normative sections.

   Kaz: it is just an informative document

   Zoltan: we should be able to use normative language like MAY,
   SHOULD, etc, otherwise we cannot have any testing

   Daniel: yes, we need to be able to say what to do

   Daniel: asking Kaz to check how to proceed

   Daniel: time is up

   adjourned


    Minutes manually created (not a transcript), formatted by
    [15]scribe.perl version 159 (Fri Nov 5 17:37:14 2021 UTC).

     [15] https://w3c.github.io/scribe2/scribedoc.html

Received on Monday, 10 January 2022 08:22:18 UTC