W3C home > Mailing lists > Public > public-wot-ig@w3.org > September 2020

[wot-usecases] minutes - 6 August 2020

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Mon, 07 Sep 2020 20:36:17 +0900
Message-ID: <87a6y1lsy6.wl-ashimura@w3.org>
To: public-wot-ig@w3.org, public-wot-wg@w3.org
available at:
  https://www.w3.org/2020/08/06-wot-uc-minutes.html


also as text below.

Thanks,

Kazuyuki

---
   [1]W3C

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


                               - DRAFT -

                             WoT Use Cases

06 Aug 2020

   [2]Agenda

      [2] https://www.w3.org/WoT/IG/wiki/IG_UseCase_WebConf#Agenda_6.8.


Attendees

   Present
          Kaz_Ashimura, Jennifer_Lin, Michael_Lagally,
          Michael_McCool, Ryuichi_Matsukura, Tomoaki_Mizushima

   Regrets

   Chair
          Lagally

   Scribe
          kaz

Contents

     * [3]Topics
         1. [4]Prev minutes
         2. [5]ITU-T liaison
         3. [6]Issues and PRs
         4. [7]AOB?
     * [8]Summary of Action Items
     * [9]Summary of Resolutions
     __________________________________________________________

Prev minutes

   [10]May-14

     [10] https://www.w3.org/2020/05/14-wot-uc-minutes.html


   approved

   [11]May-28

     [11] https://www.w3.org/2020/05/28-wot-uc-minutes.html


   approved

   [12]July-9

     [12] https://www.w3.org/2020/07/09-wot-uc-minutes.html


   approved

   (with the fix for "ca" to "Cristiano")

   [13]July-23

     [13] https://www.w3.org/2020/07/23-wot-uc-minutes.html


   approved

ITU-T liaison

   Lagally: Ilyoung is not around yet, but I've been looking at
   their documents

   [14]https://www.itu.int/ITU-T/recommendations/rec.aspx?rec=1169

   9

     [14] https://www.itu.int/ITU-T/recommendations/rec.aspx?rec=11699


   [15]https://www.itu.int/ITU-T/recommendations/rec.aspx?rec=1264

   7

     [15] https://www.itu.int/ITU-T/recommendations/rec.aspx?rec=12647


   [16]https://www.itu.int/ITU-T/recommendations/rec.aspx?rec=1302

   7

     [16] https://www.itu.int/ITU-T/recommendations/rec.aspx?rec=13027


   [17]https://www.itu.int/ITU-T/recommendations/rec.aspx?rec=1363

   7

     [17] https://www.itu.int/ITU-T/recommendations/rec.aspx?rec=13637


   Lagally: (goes through those documents)

   McCool: we should ask Gyu Myoung about how they update their
   documents
   ... for example, terminology should be aligned with our work

   Lagally: yeah, would have further collaboration as well

   McCool: also what "Web interface" means in their documents
   ... human interface?
   ... or including M2M interface?
   ... also "agent" and "broker", etc.

   [18]Y-4400 - T-REC-Y.2063-201207-I

     [18] https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-Y.2063-201207-I!!PDF-E&type=items


   McCool: we should look at what Mozilla does as well
   ... there should be some common pattern

   (discussion on "Figure 8-1 íV Conceptual model of the web of
   things" on p6)

   McCool: wondering what the "agents" expose, e.g., HTTP
   ... also is there any entity who does registration?
   ... also service discovery mechanism
   ... may be human registers information manually

   Kaz: regarding the Figure 8-1, maybe the "Web of things broker"
   layer is similar to our "Binding Templates"
   ... so we could think about that kind of similarity
   ... but I believe we should start with concrete use cases and
   requirements which are underlying

   Lagally: yeah

   McCool: a deep dive into Mozilla architecture might be also
   useful as well
   ... maybe we could ask Ben as well to review this document
   ... also (as already mentioned) wondering about the discovery
   mechanism

   Lagally: would everybody to take a look
   ... also (as Kaz mentioned) use cases and requirements are very
   important too

   McCool: Appendix I has description on "Use cases and scenarios
   of the web of things"
   ... about "Home control services using WoT"
   ... smart home environment
   ... robot thing is also interesting
   ... commanding for remote access
   ... wondering if there are other use cases in other documents

Issues and PRs

   [19]Pullrequests

     [19] https://github.com/w3c/wot-usecases/pulls


   [20]PR 33

     [20] https://github.com/w3c/wot-usecases/pull/33


   Lagally: would like to convert new proposals into HTML

   McCool: wondering when to convert the new ones into HTML

   Lagally: also how to deal with cross reference between vertical
   ones and horizontal ones

   [21]Issue 39

     [21] https://github.com/w3c/wot-usecases/issues/39


   McCool: might want to have a dashboard for cross referencing

   [22]https://github.com/w3c/wot-usecases/pull/38


     [22] https://github.com/w3c/wot-usecases/pull/38


   McCool: would like to have input from Jennifer

   Jennifer: don't want to make the use case too narrow

   McCool: we're concerned about visualization as well
   ... related to WebGL, etc.

   Lagally: do you want to have some more offline discussion about
   this use case?

   McCool: would have some more one-on-one discussion with
   Jennifer

   Lagally: ok

   McCool: we can add a sentence for the moment saying
   visualization is out of scope

   [23]PR 33

     [23] https://github.com/w3c/wot-usecases/pull/33


   McCool: horizontal discovery use case
   ... discovery itself is not a vertical use case but horizontal
   technology

   Lagally: ok
   ... do we need further review for this?

   Jennifer: let's quickly see this

   Lagally: (goes through the proposal)

   [24]changes

     [24] https://github.com/w3c/wot-usecases/pull/33/files


   Jennifer: everything to be sent to a specific network?

   McCool: depending on the requirements
   ... possibly a distributed mechanism with multiple networks
   ... single network is appropriate for smarthome use cases,
   though

   Jennifer: ok
   ... fine with having a generic description for this

   McCool: ok
   ... the point here is having generic distributed mechanism as
   well
   ... maybe we can add a comment on discovery service

   Lagally: people may think the "service" is hosted by some
   device server

   McCool: "discovery service" here is more abstract one
   ... maybe would be clearer to say "discover mechanism" here
   ... which possibly includes several components

   Lagally: (creates a new issue for wot-architecture)
   ... incorporate the discovery terminology into terminology
   section

   <mlagally>
   [25]https://github.com/w3c/wot-architecture/issues/530


     [25] https://github.com/w3c/wot-architecture/issues/530


   Lagally: what about "Variants" here?

   McCool: let's not merge this yet but think about the
   terminology a bit more

   Jennifer: thought this proposal is almost ok from my viewpoint

   McCool: will go through the proposal again

   Lagally: btw, we should add Jennifer to the "Reviewer(s)"
   section

   McCool: ok

AOB?

   Lagally: will remind our ITU-T colleagues of the joint
   discussion.

   [adjourned]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes manually created (not a transcript), formatted by
    David Booth's [26]scribe.perl version ([27]CVS log)
    $Date: 2020/08/09 23:55:49 $

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

     [27] http://dev.w3.org/cvsweb/2002/scribe/

Received on Monday, 7 September 2020 11:36:24 UTC

This archive was generated by hypermail 2.4.0 : Monday, 7 September 2020 11:36:25 UTC