[wot-ig/wg] minutes - 13 January 2021

available at:
  https://www.w3.org/2021/01/13-wot-minutes.html

also as text below.

Thanks a lot for taking the minutes, Daniel!

Kazuyuki

---
   [1]W3C

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

                               WoT-IG/WG

13 January 2021

   [2]Agenda. [3]IRC log.

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

Attendees

   Present
          Daniel_Peintner, David_Ezell, Ege_Korkan, Jennifer_Lin,
          Kaz_Ashimura, Kunihiko_Toumura, Michael_Koster,
          Michael_Lagally, Michael_McCool, Sebastian_Kaebisch,
          Takahisa_Suzuki, Tetsushi_Matsuda

   Regrets
          -

   Chair
          McCool

   Scribe
          dape, kaz

Contents

    1. [4]Agenda
    2. [5]Minutes review, https://www.w3.org/2020/12/
       16-wot-minutes.html
    3. [6]Quick updates
    4. [7]Virtual F2F Planning
    5. [8]Liaisons
    6. [9]TF Reports
    7. [10]AOB
    8. [11]Summary of action items

Meeting minutes

  Agenda

   McCool: Agenda bashing

  Minutes review, [12]https://www.w3.org/2020/12/16-wot-minutes.html

     [12] https://www.w3.org/2020/12/16-wot-minutes.html

   McCool: Spatial data joint call
   … some people gave emails

   Kaz: is properly organized

   McCool: IETF

   Koster: TODO on my side
   … working on it

   McCool: OPC-UA liaison
   … should discuss all liaisons today -> updated agenda

   McCool: Comments on minutes?

   no objections -> minutes approved

  Quick updates

   McCool: Joint calls coming up
   … Spatial data on the web, next Tuesday
   … see [13]https://github.com/w3c/wot/issues/955
   … main topics: AR use cases
   … proposed agenda in GH issue
   … ontology discussions taking place on mailinglist

     [13] https://github.com/w3c/wot/issues/955

   McCool: APA call, [14]https://github.com/w3c/wot/issues/953
   … Jan 27, 9am ET
   … re-use PlugFest slot
   … please label issues with "accessibility" accordingly

     [14] https://github.com/w3c/wot/issues/953

   McCool: Microsoft DTDL, open topic
   … still need to find proper slot

   Lagally: Ought to restart discussions

   McCool: Could aim for February

   McCool: Publication follow-up

   Kaz: created 5 PRs
   ... Architecture: [15]https://github.com/w3c/wot-architecture/
   pull/576
   ... TD: [16]https://github.com/w3c/wot-thing-description/pull/
   1027
   ... Discovery: [17]https://github.com/w3c/wot-discovery/pull/
   108
   ... Profile: [18]https://github.com/w3c/wot-profile/pull/62
   ... Scripting API: [19]https://github.com/w3c/
   wot-scripting-api/pull/288

     [15] https://github.com/w3c/wot-architecture/pull/576
     [16] https://github.com/w3c/wot-thing-description/pull/1027
     [17] https://github.com/w3c/wot-discovery/pull/108
     [18] https://github.com/w3c/wot-profile/pull/62
     [19] https://github.com/w3c/wot-scripting-api/pull/288

   Kaz: small fixes, should be merged in the each TF call

  Virtual F2F Planning

   McCool: Talked about Pune but because of Covid we will not have
   any F2F
   … hence will be virtual
   … proposal
   … Plugfest: March 1-5, 9am (?) ET
   … Virtual F2F: March 15-26, 8-11am (?) ET
   … Need a doodle to finalize

   McCool: Other alignments
   … should have solid drafts till then
   … in June 2021: F2F and PlugFest
   … in PF slot we should talk about possible themes/topics

   McCool: Kaz, can you setup Doodles?

   Kaz: OK

   McCool: should have main call, avoiding others call

   McCool: Known conflicts?

   -> none heard

   Action: kaz to generate doodle for March vF2F

  Liaisons

   McCool: IETF/ASDF/T2TRG

   McCool: calls set already?

   Koster: Not sure, Ari just came back

   McCool: OPC-UA ?

   Sebastian: looked into validation
   … using SHACL
   … compare with OPC-UA approach
   … not sure if the group we are in contact with is the *right*
   group
   … addressing OPC-UA bindings ... joint discussions to follow

   McCool: meeting scheduled?

   Sebastian: no appointment in my calendar yet
   … will check

   McCool: ITU-T SG20

   Lagally: in 2 weeks we will discuss topic in use-case call

   McCool: 26th?

   Lagally: Yes

  TF Reports

   Daniel: validation for *partial* TD like Thing Model, fragment
   TD, Discovery, ...

   Lagally: terminology for partial TD
   … need definition..

   Daniel: Yes, difficult to draw a line among them.

   Daniel: kind of lost about how to define/validate them

   Lagally: should discuss it during the Architecture call
   tomorrow, Jan 14
   … you can say our specific partial TD could be validated by
   JSON Schema
   … is that right?

   <dape> McCool: propose moving it to acrh call

   McCool: we should discuss it during the TD/Arch calls

   McCool: Security
   … discussed 2 issues
   … 1. post from external person, issue #197
   … formulated response
   … got response, did not have time to look at it
   … relates to architecture also

   Lagally: does hspaay propose a way to solve the issue?

   McCool: mentions that we require all being server
   … it is not correct. Explained it. Will try to invite hime to
   call..

   McCool: 2. topic: API key and PSK key missing descriptions
   … another issue popped up, ID for Philips hue is in URL
   … we do not support this yet
   … URI template?
   … try to resolve it soon

   Ege: Will talk about it in TD call

   McCool: Discovery call

   Kaz: Skimmed existing issues and PRs
   … will talk about resolutions next week

   McCool: Marketing

   Sebastian: talked about animation video
   … final steps
   … exchange with Coralie
   … waiting for feedback from APA / Josh
   … final voice-over is still missing
   … quickly talke about new web page (TD content)

   Kaz: Asked Josh already
   … got response -> will forward that response

   McCool: "Getting started" content needs to be improved on web
   page
   … grab examples from Cristiano

   McCool: PF/Testing
   … defer to PF call
   … in 2 weeks we can conflicts

   McCool: TD/Bindings

   Sebastian: today we will restart work
   … e.g. security and Philips Hue

   Lagally: Link relation types
   … do we plan to explain link relation type

   Sebastian: Still lots of work needed
   … cannot say whether it is achievable

   Lagally: Just initial set?

   Sebastian: Do we have an initial list?

   <kaz> [20]Discovery minutes item 7

     [20] https://www.w3.org/2021/01/11-wot-discovery-minutes.html#t07

   Lagally: Yes, but might need further work

   Kaz: Talked about it in discovery call as well
   … Farshid is planning to work on proposal, and we'll see what
   type would fit best based on that proposal.

   McCool: need to assemble all requirements popping up in
   different places

   Lagally: We have input from use-cases document as a starting
   point

   Sebastian: TD spec mentions we plan to work on it

   McCool: Use-cases

   Lagally: Call yesterday
   … newcomers from building and AR
   … re-factored all uses from architecture
   … publish by May?
   … draft by March

   Lagally: Architecture
   … no call this week yet
   … tomorrow we will have call (one hour only)
   … terminology will be discussed

  AOB

   McCool: AOB?

   Kaz: Perey invited expert status?

   McCool: geospatial expert

   Kaz: let's talk about it in chairs call

   McCool: adjourned

   McCool: PF in 9 minutes

Summary of action items

    1. [21]kaz to generate doodle for March vF2F


    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, 3 March 2021 09:10:49 UTC