[wot-architecture] minutes - 7 May 2020

available at:
  https://www.w3.org/2020/05/07-wot-arch-minutes.html

also as text below.

Thanks,

Kazuyuki

---
   [1]W3C

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

                               - DRAFT -

                            WoT Architecture

07 May 2020

   [2]Agenda

      [2] https://www.w3.org/WoT/IG/wiki/WG_WoT_Architecture_WebConf#Agenda

Attendees

   Present
          Kaz_Ashimura, Michael_McCool, Michael_Lagally,
          Tomoaki_Mizushima, Zoltan_Kis

   Regrets

   Chair
          Michael_Lagally

   Scribe
          kaz

Contents

     * [3]Topics
         1. [4]Agenda
         2. [5]Backlog
         3. [6]Prev minutes
         4. [7]Virtual f2f planning
         5. [8]Profile
         6. [9]Lifecycle
     * [10]Summary of Action Items
     * [11]Summary of Resolutions
     __________________________________________________________

   Note: The first Architecture call was cancelled as we confirmed
   during the WoT main call.

Agenda

   Lagally: goes through the agenda
   ... main topic should be the lifecycle
   ... btw, the schedule section for the spec work should be
   updated

   McCool: right
   ... the main page also

   Lagally: also we should update the WoT pages

   Kaz: we already started to work on "WoT welcome page"
   ... so we should talk about how to maintain all the pages
   during the marketing call

   Lagally: adds some quick tweaks to the WoT Architecture wiki to
   point the WoT main wiki for the spec schedule

Backlog

   Lagally: presentation o DID?

   McCool: we can certainly reopen that topic

   Lagally: update the description on the Architecture wiki around
   "Backlog"
   ... DID use case + WoT mapping

   McCool: some recommendation on how to use TD
   ... can work on the collab

Prev minutes

   [12]Apr-30 minutes

     [12] https://www.w3.org/2020/04/30-wot-arch-minutes.html

   Lagally: looks good to me

   McCool: good to me too

   Lagally: approved

Virtual f2f planning

   McCool: created a couple of issues for security

   [13]issue 492

     [13] https://github.com/w3c/wot-architecture/issues/492

   [14]issue 493

     [14] https://github.com/w3c/wot-architecture/issues/493

   [15]issue 494

     [15] https://github.com/w3c/wot-architecture/issues/494

   Lagally: ok
   ... ad use case by Ege

   [16]issue 496

     [16] https://github.com/w3c/wot-architecture/issues/496

   McCool: any other place for reservation?

   Lagally: it's just a use case at the moment
   ... need to write up a concrete description (based on the
   template)
   ... will suggest Ege do so
   ... (adds comment to issue 496)

   McCool: would have transaction

   [17]Lagally's new comment to issue 496

     [17] https://github.com/w3c/wot-architecture/issues/496#issuecomment-625322155

   [18]Pullrequest 470

     [18] https://github.com/w3c/wot-architecture/pull/470

   Lagally: transportation use case

   Zoltan: would split it up
   ... create a new transport directory and generate several
   separate use case descriptions

   McCool: yeah
   ... "transportation" sounds like a category

   Lagally: maybe we don't need to create a sub directory
   ... but simply could have multiple descriptions within one file

   Sebastian: ok
   ... will break the description into pieces and then commit the
   changes again

   Lagally: ok

   [19]Pullrequest 487

     [19] https://github.com/w3c/wot-architecture/pull/487

   Lagally: let's defer this until we have Christian

   [20]Pullrequest 491

     [20] https://github.com/w3c/wot-architecture/pull/491

   Lagally: let's merge this

   McCool: one thing need to do first is looking at this as an
   initial path

   Lagally: ok. once we have a bunch of use cases like this, we
   could do proof read
   ... so let's merge this now
   ... (merged)

   [21]Pullrequest 495

     [21] https://github.com/w3c/wot-architecture/pull/495

   Lagally: new one
   ... let's defer this
   ... and review this next week

   [22]Pullrequest 497

     [22] https://github.com/w3c/wot-architecture/pull/497

   Lagally: use case clean-up
   ... retail, audio/video, media information
   ... input from MEIG (NHK)
   ... just cleaning up redundancy, etc.
   ... will fix typo as well
   ... geolocation, mmi, ...

   McCool: "Agriculture" here might be better to be called as
   "Smart greenhouse", etc.

   Lagally: ok
   ... (continue to go through the use cases)

   McCool: happy to merge this PR
   ... note that Oliver is working on x-protocol interworking use
   case

   Lagally: ok
   ... (continue to go through the rest)
   ... gap for digital twin and simulation
   ... deeper consideration and dedicated work
   ... and then some typos
   ... would go ahead and merge this

   McCool: fine

   Lagally: merged

Profile

   [23]Pullrequest 498

     [23] https://github.com/w3c/wot-architecture/pull/498

   Lagally: just quickly skim it
   ... (goes through the proposal)

Lifecycle

   Lagally: would review the updated diagram

   <zkis>
   [24]https://drive.google.com/file/d/1E7dF65r8i1rx5ykJujMYe14RYP
   OvXAPf/view

     [24] https://drive.google.com/file/d/1E7dF65r8i1rx5ykJujMYe14RYPOvXAPf/view

   Lagally: what is the difference between "Operational" and "WoT
   Operational"?

   McCool: "Bootstrapped/Onboarded" is kind of like "Device
   Operational"?
   ... confusion about service keys and application keys

   Sebastian: all the WoT apps have the same service key

   Kaz: we need to define "service" and "application" here
   ... e.g., a service as a session consists of several
   applications

   Lagally: kind of confused
   ... what about thinking about sequence diagram between players?
   ... we should not reinvent a new model if there are existing
   ones, though
   ... let's add definition of terms for this diagram to the
   terminology section of the Architecture document

   Sebastian: yeah, so I'm generating a Pullrequest
   ... we can try to come up with some technology

   McCool: we might want to have folders for application-specific
   vs technology-specific portions

   Lagally: for example, we could have 4 terms to be defined

   Sebastian: note that need to be consistent

   <zkis> [25]https://github.com/w3c/wot-architecture/pull/478

     [25] https://github.com/w3c/wot-architecture/pull/478

   Sebastian: Pullrequest above
   ... one aspect is improving the keys

   Lagally: we continue the discussion next week
   ... and also try to capture the definitions

   Sebastian: e.g., can we have some more discussion during the
   Security call as well?
   ... can work on the update today and tomorrow

   Lagally: let me see

   Sebastian: Monday, 2pm CET

   Lagally: can make it on 11th
   ... and then let's close this at the next Architecture call on
   14th
   ... Zoltan, please ping me once you're ready

   <McCool> added lifecycle to security agenda for May 11:
   [26]https://www.w3.org/WoT/IG/wiki/IG_Security_WebConf#11_May_2
   020

     [26] https://www.w3.org/WoT/IG/wiki/IG_Security_WebConf#11_May_2020

   Lagally: by email
   ... any other business for today?

   (none)

   [adjourned]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes manually created (not a transcript), formatted by
    David Booth's [27]scribe.perl version 1.154 ([28]CVS log)
    $Date: 2020/05/13 07:47:53 $

     [27] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [28] http://dev.w3.org/cvsweb/2002/scribe/

Received on Monday, 18 May 2020 12:29:32 UTC