W3C home > Mailing lists > Public > public-wot-wg@w3.org > March 2018

[wot-ig/wg] minutes - 14 March 2018

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Thu, 15 Mar 2018 13:48:42 +0900
Message-ID: <CAJ8iq9WPm4amikFeoP9=X-MybGrd3L7-jRBkqZKtBorLZ-3yAw@mail.gmail.com>
To: Public Web of Things IG <public-wot-ig@w3.org>, public-wot-wg@w3.org
available at:

also as text below.

Thanks a lot for taking these minutes, Nimura-san!




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

                               - DRAFT -


14 Mar 2018


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


          Kaz_Ashimura, Daniel_Peintner, Graeme_Coleman,
          Kazuaki_Nimura, Kunihiko_Toumura, Matthias_Kovatsch,
          Michael_Koster, Michael_McCool, Taki_Kamiya,
          Tomoaki_Mizushima, Toru_Kawaguchi, Michael_Lagally,
          Ryuichi_Matsukura, Zoltan_Kis, Sebastian_Kaebisch


          Matthias, McCool



     * [3]Topics
         1. [4]Quick Updates
         2. [5]About F2F
         3. [6]Resolution for next working drafts
               o [7]TD
               o [8]Binding Templates
               o [9]Scripting API
               o [10]architecture
     * [11]Summary of Action Items
     * [12]Summary of Resolutions

   <kaz> scribenick: nimura


     [13] https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Agenda

Quick Updates

   We will skip next two calls.

   because of IETF/OCF and F2F

   also finishing up the plugfest preparation

   No editor call as well.

   skip task force calls also.

   About daylight saving

   normal time shift during the F2F.

   <kaz> (sync between US and EU after f2f)

   <kaz> (however, the starting times continue to be one hour
   earlier in non-daylight-saving countries, e.g.,

   <kaz> (even after the f2f)

   <kaz> [note: daylight saving shift can't be handled by outlook

About F2F

   14 people for OCF meeting

   27 people open day


     [14] https://www.w3.org/2002/09/wbs/1/WoTF2F201803/results

   if you need power adapter don't forget.

   1 wired connection per person would be necessary then splitted

   <kaz> [15]plugfest requirements

     [15] https://github.com/w3c/wot/blob/master/plugfest/2018-prague/preparation.md#user-content-5-requirements-for-plugfest-setting

   NOTE on PlugFest logistics: Please fill out the requirements
   table above, and also send an email to Michael Lagally ASAP if
   you have additional requirements, e.g., on port configuration

   send the requirement for network or so and arrange by local

   TCP and UDP have different restriction.

   need to be updated for scripting API agenda in F2F

   resolve agenda for F2F today ? then meet plugfest and hash out.

   about interest group:

   lifecycle connected to security...

   Sync of servient is central part of plugfest

   <kaz> [16]f2f agenda input

     [16] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_24-29_March_2018,_Prague,_Czech_Republic#Input

   security meta also relate to plugfest

   HATEOAS is also the topic

   HATEOAS is related simplified TD

   Type of TD: abstract model and separation of binding.

   outline of type of TD can lead the discussion of life cycle of

   4 type were presented before.

   recall the 4 types and discuss in the meeting.


     [17] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_24-29_March_2018,_Prague,_Czech_Republic#Input

   still collecting topics in input section. dead line is by the
   end of this week.

Resolution for next working drafts

   announce the review, issues raised and fix the issues a lot.

   automated tool check the some aspect of document then seems we
   don't finish by tomorrow.


   <mkovatsc_> [18]https://w3c.github.io/wot-thing-description/

     [18] https://w3c.github.io/wot-thing-description/

   any objection?

   <kaz> (none)

   RESOLUTION: Thing Description is accepted to be published as an
   updated WD.

[Binding Templates]

   <mkovatsc_> [19]https://w3c.github.io/wot-binding-templates/

     [19] https://w3c.github.io/wot-binding-templates/

   agree to publication?

   <kaz> as a First public Working Group Note

   no objection

   the resolution accepted also.

   RESOLUTION: publish the binding templates as a first public
   working group note

[Scripting API]

   <kaz> [20]outstanding PR on handler callbacks

     [20] https://github.com/w3c/wot-scripting-api/pull/103

   one outstanding pull request for scripting API there

   issue #102

   <kaz> [21]https://github.com/w3c/wot-scripting-api/issues/102

     [21] https://github.com/w3c/wot-scripting-api/issues/102

   setting generic handler would be fine and can change the
   modification today

   for setting named handler, make name mandatory and first
   argument (handler function is second) define a new function

   define a new function

   for ExposedThing.

   we should avoid last minutes changes.

   but we had inconsistency there.

   and maybe very easy to fix.

   it is kind of late though.

   we agree on no generic handler support for upcoming plugfest

   in one hour, modify and merge the pull request.

   we can use conditional reflection on generic handler.

   RESOLUTION: we'll publish the scripting api after fixing pr 103
   and issue 102


   about architecture document?

   once the draft updated, we can approve by e-mail

   <kaz> [adjourned and move to the plugfest call]

Summary of Action Items

Summary of Resolutions

    1. [22]Thing Description is accepted to be published as an
       updated WD.
    2. [23]publish the binding template as a first public working
       group note
    3. [24]we'll publish the scripting api after fixing pr 103 and
       issue 102

   [End of minutes]

    Minutes formatted by David Booth's [25]scribe.perl version
    1.152 ([26]CVS log)
    $Date: 2018/03/15 04:45:21 $

     [25] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [26] http://dev.w3.org/cvsweb/2002/scribe/
Received on Thursday, 15 March 2018 04:49:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:27:49 UTC