W3C home > Mailing lists > Public > public-wot-ig@w3.org > May 2021

[wot-ig/wg] minutes - 3 March 2021

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Wed, 05 May 2021 15:28:04 +0900
Message-ID: <8735v14ruz.wl-ashimura@w3.org>
To: public-wot-ig@w3.org, public-wot-wg@w3.org
available at:
  https://www.w3.org/2021/03/03-wot-minutes.html

also as text below.

Thanks a lot for takig the minutes, Michael Lagally!

Kazuyuki

---
   [1]W3C

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

                               WoT-IG/WG

03 March 2021

   [2]Agenda. [3]IRC log.

      [2] https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#3_March_2021
      [3] https://www.w3.org/2021/03/03-wot-irc

Attendees

   Present
          Cristiano_Aguzzi, Daniel_Peintner, Ege_Korkan,
          Kaz_Ashimura, Kunihiko_Touomura, Michael_Lagally,
          Michael_McCool, Ryuichi_Matsukura, Sebastian_Kaebisch,
          Takahisa_Suzuki, Tetsushi_Matsuda, Tomoaki_Mizushima

   Regrets
          -

   Chair
          McCool, Sebastian

   Scribe
          kaz, mlagally_

Contents

    1. [4]Agenda
    2. [5]Guests
    3. [6]minutes of last week's call
    4. [7]Marketing updates
    5. [8]WoT Use Cases
    6. [9]repository changes
    7. [10]Plugfest and F2F
    8. [11]F2F planning
    9. [12]Liaisons

Meeting minutes

  Agenda

   <Sebastian walks through the agenda>

  Guests

   Sebastian: no guests today
   … status of Michael Koster is still pending (invited expert)

  minutes of last week's call

   <kaz> [13]Feb-24

     [13] https://www.w3.org/2021/02/24-wot-minutes.html

   McCool: this week there's a conflict between architecture and
   plugfest

   Lagally: we will start at 4pm UTC tomorrow (1 hour later)

  Marketing updates

   Sebastian: we have released out Webpage for the first of March,
   am very happy we have the representation here
   … thanks a lot to Daniel and all contributors
   … the page is online now but perhaps not complete
   … structure of WG is here, now we can optimize step by step
   … people can provide PRs in the weekly marketing call
   … we also have an animation video which is public on youtube
   … this is very helpful to disseminate WoT to the public
   … there was some surprise that the Webpage has been published
   … our assumption was that the publication was ok according to
   our roadmap
   … the process is that everyone in the group can provide a PR,
   the marketing team can decide whether to bring it in

   Lagally: would acknowledge all your hard work on the new WoT
   page
   … but there was some missing piece about the procedure
   … when the marketing TF was formed we had an agreement that all
   external facing communication would require approval in the
   main TF
   … outbound communication is very important, so would record
   clear resolution on the public minutes as well
   … we should clarify the process

   Sebastian: tx for providing your view

   Daniel: there was some kind of misunderstanding, this early
   publication was not well communicated
   … if we want to provide more information we can post on twitter
   … we decided we should not need more circles for blog posts
   … I agree we need to decide on the next steps, how to approve
   changes to the web page

   McCool: Yes, we need a more formal approval process but don't
   want to repeat all work of the marketing group in the main call
   … timing is important in some cases, waiting a week may be too
   long, e.g. for publishing to twitter
   … let's take this off-line, we can work out a proposed
   procedure in the marketing call next week and come back with a
   proposal to the main call next week
   … does this make sense?

   <kaz> kaz: +1

   Sebastian: makes sense for me

   <Zakim> dape, you wanted to use twitter or generic w3c blog is
   still possible

   Sebastian: twitter communication may require faster speed
   … I had the impression that we were very transparent
   … I agree with Lagally that we have to get an approval but we
   did not get any objection
   … We should improve the publication policy, will discuss in
   next Marketing call

   McCool: Bulk of the work can be done in the marketing call, but
   approval should be done in the main call

   <kaz> kaz: +1

  WoT Use Cases

   <kaz> [14]WoT Use Cases Editor's Draft

     [14] https://w3c.github.io/wot-usecases/

   <kaz> ml: Chapter 4 in pretty good shape

   <kaz> ... some cleaning up remaining

   Sebastian: publication is planned for in two weeks

   Kaz: if that is the plan I'm ok to continue the discussion on
   Tuesday
   … but please note that this is an IG note and the first
   publication, so it does not have to be perfect

  repository changes

   Some repos already have been changed (master->main), others not
   yet done

   <kaz> done: wot-testing, wot-discovery, wot-security,
   wot-thing-description

   Ege: I can't change it in the binding templates repo

   <kaz> [at the moment, only the Chairs have the credential]

   McCool: I will make the change tomorrow in the morning

   Lagally: all repos

   McCool: yes

   Lagally: thanks!

  Plugfest and F2F

   <kaz> [15]Plugfest page

     [15] https://github.com/w3c/wot-testing/blob/master/events/2021.03.Online/README.md

   Sebastian: We have some cancelled TF meetings, no TD call today
   … suggest to concentrate on plug fest
   … Plugfest is running quite smoothly

   <kaz> [16]Cancellations during Plugfest this week

     [16] https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Cancellations

   Sebastian: a couple of things are online, Riot OS, Toumura,
   Siemens, Oracle
   … people who take care of the thing models, tooling, a lot of
   things are going on

   <kaz> [17]TDs so far

     [17] https://github.com/w3c/wot-testing/tree/main/events/2021.03.Online/TDs

   Sebastian: our own Plugfest is held right after this call,
   while the IETF hackathon occurs after that.

   McCool: IETF VPN got cancelled
   … we have our own VPN
   … we use issue tracker for porjects
   … plugfest call today has its own WebEx

  F2F planning

   <sebastian> [18]https://www.w3.org/WoT/IG/wiki/
   F2F_meeting,_March_2021

     [18] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_March_2021

   <kaz> [19]vF2F agenda

     [19] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_March_2021#Agenda

   McCool: we should finalize the agenda next week, please put
   times
   … it would be great to have presentation material available
   before the sessions

  Liaisons

   <kaz> [20]WebEx for the liaison discussion (member-only)

     [20] https://lists.w3.org/Archives/Member/member-wot-wg/2021Mar/0008.html

   Sebastian: We will have a meeting tomorrow to clarify plans
   with OPC UA, such as joint charter, everybody is welcome to
   attend the call

   McCool: invite has been already sent

   McCool: time is 1 hour before the plugfest call

   Sebastian: WebThings - Ben will give us an update
   … will also invite eCl@ss

   Kaz: IEC will join the entire session

   <kaz> (ITU-T SG20 also joins the vF2F on March 22)

   <McCool> [21]WISHI workshop

     [21] https://github.com/t2trg/wishi/wiki/Agenda-items#wishi-online-meeting

   McCool: T2TRG - there was a Wishi and IETF hackathon meeting
   … I attended the Wishi meeting, we discussed future topics
   … using SDF in TDs and thing models

   Sebastian: no news on OPC UA, look forward on tomorrow's
   meeting

   mml: OGC - discussed with Christine Perrey, GeoSparql, need to
   follow up

   Kaz: Echonet, will meet this Friday

   McCool: APA - no news

   Lagally: no response on DTDL yet

   topic TF reports

   Daniel: Scripting worked over open issues and merged some PRs,
   we are good for the master-> main change
   … some proposals for API improvement

   McCool: no Security call this week
   … discovery merged a couple of PRs
   … prioritized new topics
   … Will have sth by F2F, but no examples

   Sebastian: Marketing: Webpage, Video already discussed,
   publication policy will be discussed next week

   Lagally: no use case call last week

   Sebastian: plugfest call whole this week
   … TD: some PRs were merged, used in the plugfest
   … first version of a JSON schema for thing models has been
   provided by Ege
   … long discussion about dataschema definition in forms, let's
   see what we learn from the plugfest

   McCool: this was the first time a JSON pointer has been used

   Lagally: architecture: we classified devices based on memory
   footprint, i.e. class-0, class-1, ...

   Kaz: we should use plugfest webex for the plugfest call today.

   <kaz> [adjourned]


    Minutes manually created (not a transcript), formatted by
    [22]scribe.perl version 127 (Wed Dec 30 17:39:58 2020 UTC).

     [22] https://w3c.github.io/scribe2/scribedoc.html
Received on Wednesday, 5 May 2021 06:28:10 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 5 May 2021 06:28:11 UTC