W3C home > Mailing lists > Public > public-wot-ig@w3.org > February 2018

[PlugFest] minutes - 14 February 2018

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Sat, 17 Feb 2018 03:21:01 +0900
Message-ID: <CAJ8iq9Ukt3Vxr7CM8f-FL5LTKdJrV8SMNeC2GLjJG8cmLnNZ5Q@mail.gmail.com>
To: Public Web of Things IG <public-wot-ig@w3.org>, public-wot-wg@w3.org
available at:
  https://www.w3.org/2018/02/14-wot-pf-minutes.html

also as text below.

Thanks a lot for taking these minutes, Daniel!

Kazuyuki

---

   [1]W3C

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

                               - DRAFT -

                              WoT PlugFest

14 Feb 2018

Attendees

   Present
          Kaz_Ashimura, Benjamin_Klotz, Kunihiko_Toumura,
          Michael_Koster, Toru_Kawaguchi, Soumya_Kanti_Datta,
          Daniel_Peintner, Tomoaki_Mizushima, Matthias_Kovatsch

   Regrets

   Chair
          Koster

   Scribe
          dape

Contents

     * [2]Topics
     * [3]Summary of Action Items
     * [4]Summary of Resolutions
     __________________________________________________________

   <scribe> scribe: dape

   Koster: on Agenda is process check-list
   ... talk about servient to servient (with proxy)
   ... would like to start with review where we are
   ... what are we developing to help people be prepared
   ... we have questionnaires
   ... will turn into W3C forms
   ... want to collect information what is being implemented
   ... also, we have regular wiki collecting what people bring
   with them
   ... entry form from previous PlugFests could be re-used
   ... maybe add additional columns (if necessary)

   Daniel: entry form == wiki page

   [5]https://www.w3.org/WoT/IG/wiki/F2F_meeting,_4-10_November_20
   17,_Burlingame,_CA,_USA#Participation

      [5] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_4-10_November_2017,_Burlingame,_CA,_USA#Participation

   [6]https://www.w3.org/WoT/IG/wiki/F2F_meeting,_24-29_March_2018
   ,_Prague,_Czech_Republic#PlugFest_.2824-25_Mar_2018.29

      [6] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_24-29_March_2018,_Prague,_Czech_Republic#PlugFest_.2824-25_Mar_2018.29

   <kaz>
   [7]https://www.w3.org/WoT/IG/wiki/F2F_meeting,_24-29_March_2018
   ,_Prague,_Czech_Republic?

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

   Daniel: current PlugFest wiki misses entry form

   Koster: Yes, need to add this
   ... any updates to this kind of wiki needed?

   Daniel: Might want to think about splitting PlugFest
   information

   Koster: create new page, yes
   ... move the table

   <kaz> [8]participation table for Burlingame

      [8] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_4-10_November_2017,_Burlingame,_CA,_USA#Participation

   <kaz> [9]Prague f2f wiki doesn't have that table

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

   Matthias: fear duplicate information in several places

   <kaz> [10]preparation page for Prague

     [10] https://github.com/w3c/wot/blob/master/plugfest/2018-prague/preparation.md

   Koster: propose one location...
   ... moving to preparation page?

   <kaz> +1

   Matthias: yes

   Koster: PRs for updates should work nicely

   Matthias: Powerpoint is also fine.. easy to edit
   ... need to share information during PlugFest also

   Koster: single Powerpoint for all participants ?
   ... living document during PlugFest
   ... Markdown seems easier .... line by line changes

   Matthias: Need to take care to avoid duplication of information

   Koster: might need to have slide-deck and Markdown?
   ... we have wiki, markdown, and ppt
   ... don't need table of participants on wiki
   ... will collect entries on markup via PR
   ... powerpoint for summary

   Toru: have preparation.md already

   Koster: yes, copy from previous PlugFest

   Toru: could make PRs to that MD file

   Kaz: Could use markdown table generator

   <kaz> [11]tables generator

     [11] http://www.tablesgenerator.com/markdown_tables

   Koster: Ok, looks good
   ... get started... please comment if there are suggestions
   ... next is what we did in Burlingame.... state machines,
   diagrams
   ... implementation guidance and scenarios
   ... for scenarios we look at discovery, proxy etc
   ... might we want to start writing test-cases?
   ... proxy has same system features as a servient
   ... write to down what we want to test

   Kaz: agree
   ... btw, during the Burlingame PlugFest, there are various
   applications and devices generated by multiple participants as
   shown in the following diagram
   [12]Application, Remote Proxy, Local Proxy and Device in
   Burlingame

     [12] https://github.com/w3c/wot/blob/master/plugfest/2017-burlingame/images/PlugfestResult_Nov5.png

   Various applications and devices connected via proxies in
   Burlingame PlugFest

   Kaz: And most of those applications and devices were connected
   with Fujitsu's Remote/Local Proxies
   ... So I've started to think we could use Fujitsu's
   Remote/Local Proxies as the basic framework and concentrate on
   the interfaces, (1) the interface between Application Servients
   and Remote Proxy (green lines on the left side in the below
   diagram) and (2) another interface between Local Proxy and
   Device Servients (brown lines on the right side in the below
   diagram)
   [13]Application, Remote Proxy, Local Proxy and Device

     [13] https://www.w3.org/app-proxy-dev.png

   Fujitsu's remote proxy and local proxy as a possible framework
   for various applications and devices

   Koster: yes, enables transparent proxying
   ... need to provide implementation guidance
   ... proxy consumes device and expose them
   ... a) in the same fashion
   ... b) in a different way (other protocol)
   ... do we need to think about common TDs?
   ... is there a thing directory ?
   ... there are a lot of questions
   ... Fujitsu has a framework

   Kaz: Matsukura-san said can provide them

   Toru: what exactly?

   Kaz: Local proxy and remote proxy as a packaged framework for
   PlugFest

   Koster: shall we try to organize review
   ... what it does
   ... what can be used

   Kaz: yes
   ... will ask Matsukura-san

   Koster: <describes proxy lifecycle>
   ... special cases
   ... 3 directories (which could be connected)
   ... we start introducing lots of system variables
   ... what should be our next steps
   ... suggest to schedule review of Fujitsus framework
   ... also suggest different guidance documents for the different
   proxies cases

   Kaz: will talk to Matsukura-san again... about concrete
   interface description

   Koster: Maybe there are some simple tests we can run
   ... to ensure basic stuff works

   Kaz: yes, this is important
   ... for CR we need test cases (besides spec itself)

   Toru: we should also review what we did in Burlingame
   ... what could be the improvements

   Kaz: Exactly

   Koster: Let's put this on the agenda for next week
   ... feedback round during call
   ... will implement entry form
   ... get questionnaire made

   <kaz> [adjourned]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes formatted by David Booth's [14]scribe.perl version
    1.152 ([15]CVS log)
    $Date: 2018/02/16 18:18:23 $

     [14] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [15] http://dev.w3.org/cvsweb/2002/scribe/
Received on Friday, 16 February 2018 18:22:09 UTC

This archive was generated by hypermail 2.3.1 : Friday, 16 February 2018 18:22:10 UTC