W3C home > Mailing lists > Public > public-wot-ig@w3.org > May 2019

[TestFest] minutes - 15 May 2019

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Thu, 16 May 2019 18:26:09 +0900
Message-ID: <CAJ8iq9WX+3yD9k74Vao1HUeFh=v6kujBSnKGj1Qrpzh+w3sJpQ@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/2019/05/15-wot-pf-minutes.html

also as text below.

Thanks,

Kazuyuki

---

   [1]W3C

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

                               - DRAFT -

                              WoT TestFest

15 May 2019

Attendees

   Present
          Kaz_Ashimura, Benjamin_Klotz, Christian_Glomb,
          Daniel_Peintner, Ege_Korkan, Kathy_Giori,
          Kunihiko_Toumura, Michael_McCool, Michae_Lagally,
          Takahisa_Suzuki, Taki_Kamiya, Toru_Kawaguchi,
          Ryuichi_Matsukura, Johannes_Hund

   Regrets

   Chair
          Lagally, McCool

   Scribe
          kaz

Contents

     * [2]Topics
         1. [3]Demo
         2. [4]Scenarios
         3. [5]Playground fix
         4. [6]Demo logistics - revisited
         5. [7]F2F part
         6. [8]Testing
         7. [9]TUM invite
     * [10]Summary of Action Items
     * [11]Summary of Resolutions
     __________________________________________________________

   <inserted> scribenick: kaz

   Lagally: 2 topics, demo and test

Demo

   <mlagally>
   [12]https://github.com/w3c/wot/tree/master/workshop/ws2/demos-2
   019-Munich

     [12] https://github.com/w3c/wot/tree/master/workshop/ws2/demos-2019-Munich

   Lagally: workshop demo page above
   ... public GitHub page
   ... all the information is available publicly
   ... not 100% sure about the permission, though

   Ege: need to create a pullrequest for updates

   Lagally: ok
   ... let's go through the current document
   ... we have a participant from Mozilla as well
   ... this list of participants will become longer

   Sebastian: we have Benjamin from BMW as well
   ... Johannes from EcoG as well?

   Lagally: ok
   ... add a placeholder for BMW

   Benjamin: connected vehicle

   Lagally: please update the information
   ... we have weekly calls for demo
   ... every Wednesday
   ... also if you've not done, please add your requirements to
   the table
   ... also esp, if you need some specific ports to be open,
   please specify that

   Sebastian: can start some setting for demo
   ... as much information you give, we can provide necessary
   resources

   Lagally: one more note
   ... set up preparation will be done during the weekend right
   before the workshop, on June 1-2
   ... at TUM
   ... people from Japan has difficulty with some duty
   ... anybody who could join should work together during the
   weekend

   Kathy: detail on when we can access the demo area?

   Sebastian: booked the venue full day
   ... also preparation during the weekend
   ... if you can't make the weekend, would suggest you come early
   morning on Monday
   ... wifi router, etc., will be the same as those we used for
   our previous demos

   McCool: same SSID, etc.
   ... important to record the settings

   Lagally: wifi router from Michael Koster from SmartThings

   Sebastian: also Matthias Kovatsch

   Johannes: credentials for the router?

   McCool: should put the information on email instead of public
   wiki/GitHub
   ... people coming to the demo should check the email

   Kaz: we can send the credential information to the Member list
   ... and put a link to this demo page to that member page

   Ege: setting on Friday at Siemens
   ... then during weekend at TUM
   ... and the go back to Siemens on Monday
   ... networks at TUM
   ... local demo has no problem, but if you use simulators, maybe
   need to check

   McCool: even 22 port was blocked during TPAC in Lyon
   ... NAT-through connection would be OK, though
   ... should test the environment

   Lagally: would be better to bring some fallback
   ... would encourage everybody to think about that

   McCool: possibly a 4G router, but not sure about the cost

   Lagally: anything else on the requirements?
   ... some additional logistics/requirements to be also clarified
   here

   McCool: solo power demo
   ... simulated power supply for window

   Lagally: also a lot of notes here below the table

   Kaz: would be better to use "[1]" notation for footnotes within
   wiki

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

   Lagally: adds description saying "the following notes relate to
   the number in the table above."

Scenarios

   Lagally: we have scenario section
   ... let's first merge the Pullrequests and look into the data
   ... (and goes through the description)
   ... if we have additional participants for integration
   ... industrial integration
   ... energy management
   ... security alert using person detection
   ... and additional scenarios
   ... let's discuss them in the future calls
   ... and then
   ... logistics
   ... please put your TDs under the TDs subdirectory

   Ege: note that TDs to be updated according to the latest spec

   Sebastian: based on the CR version

   McCool: ideally we would use the CR version spec

   Sebastian: would agree we use the CR version

   Lagally: +1
   ... if you don't use it, would get problems with playground
   validator, etc.

   Daniel: will work on node-wot during the weekend

   Lagally: any questions?
   ... problem with implementing the latest CR version of TD?

   Daniel: another fallback, e.g., transformer script?

   McCool: for individual feature test, manual test would be time
   consuming

   Lagally: would be concerned if some of us use another version

   Ege: would support you
   ... this kind of things can be fixed

   McCool: in particular, some conflict with JP members
   ... so can't come until Sunday

   Kaz: we can check the participation
   ... e.g., myself can join the prep on Sunday

   Benjamin: is playground compatible with the CR version?
   ... got JSON-LD error

   Lagally: latest version of playground?

   <ege> [13]http://plugfest.thingweb.io/playground/

     [13] http://plugfest.thingweb.io/playground/

   Ege: above

   Kaz: we need to let everybody know about the CR version once we
   publish it tomorrow

   McCool: we can try online plugfest again
   ... will come on Tuesday

   Kaz: May 28?

   McCool: yes

   Kaz: we should think about what to do when
   ... May 22, 29, June 1, 2

   McCool: would suggest we try online plugfest as well
   ... e.g., 28th, Tuesday
   ... should choose a good time for everybody
   ... e.g., 8-11pm JST

   Sebastian: have to leave
   ... one more topic
   ... possible presentations on demos
   ... presentations and posters?
   ... would that make sense?

   McCool: one table per a scenario?
   ... not convinced for time

   Sebastian: Siemens can print the posters if you can provide the
   data beforehand

   Lagally: what kind of format and size?

   Sebastian: need to check within Siemens
   ... would be nice to have some common representation

   <ege> Update to playground: the new namespace is being used now

   Kaz: so we should think about basic timeline for demo scenario,
   online setting, actual demo and posters

   McCool: would it possible to print it if we provide the data on
   Friday (May 31)?

   Sebastian: need to check

   Johannes: you can check the deadline

   Lagally: one week before would make sense?

   Sebastian: would be enough

   Lagally: we can see what would work and what not during the
   online plugfest on 28th

   Kaz: until when should we finalize the demo scenario for the
   online plugfest?

   Lagally: let's finalize the scenarios by the next call on May
   22

   Sebastian: need to leave now

   Ege: what would be the earliest time allowed to get Siemens?
   ... 6am? 8am?

   Sebastian: will check
   ... and get back to you

   Ege: what about Friday?

   Sebastian: will check about Friday as well

   Lagally: added "TBD" to unclear points
   ... updated structure here
   ... please add your devices to each scenario
   ... also put your name

   McCool: also hyperlinks to TDs

Playground fix

   Ege: solved the issue pointed out by Benjamin on playground

Demo logistics - revisited

   Kaz: would see the possible bridging between Mozilal WebThing
   and WoT

   Kathy: yeah
   ... we just bridge to devices

   McCool: we can continue discussion
   ... about how to use thing description, etc.

   Lagally: (merges the latest PRs for the README.md)

   [14]PR 741

     [14] https://github.com/w3c/wot/pull/741

   [15]PR 740

     [15] https://github.com/w3c/wot/pull/740

   [16]PR 738

     [16] https://github.com/w3c/wot/pull/738

   Kathy: wondering about the table setting
   ... openday and workshop days

   Lagally: need to check with Sebastian
   ... can we talk about that next week?

   Kathy: fine

F2F part

   Ege: preparing for catering, etc.
   ... anyone could sponsor it?

   McCool: any estimate?

   Ege: have exact figure
   ... 586.67 euros

   McCool: people can check within their companies
   ... how long it would take?

   Ege: by May 27
   ... but still can find a way
   ... we can decrease the amount if needed

   Kaz: everybody, please check within your company and get back
   next week, May 22

   [17]f2f registration/demo prep registration

     [17] https://www.w3.org/2002/09/wbs/1/WoTF2F201906/

   <ege>
   [18]https://www.w3.org/WoT/IG/wiki/Main_Page#Main_WoT_WebConf

     [18] https://www.w3.org/WoT/IG/wiki/Main_Page#Main_WoT_WebConf

   Ege: WoT wiki should have two separate links, one for workshop,
   another for f2f

   Kaz: will fix it

Testing

   McCool: pretty quickly

   Kaz: please update the report on GitHub as well

   McCool: will do
   ... also will do clean-up tomorrow
   ... also hyperlinks in the report to be changed to the CR
   version
   ... still need some manual checks

   Ege: catching up with the new CR version for the assertion tool

   McCool: once you've done with it, let me know

   <ege>
   [19]https://github.com/w3c/wot-thing-description/issues/388

     [19] https://github.com/w3c/wot-thing-description/issues/388

   Ege: we already know about some issue above

   McCool: will take a look
   ... think it should be a simple bug
   ... we treat all the assertions separately
   ... it might be too strict
   ... we can think about an easier path at some point
   ... for now just continue the current approach
   ... will look into it
   ... regarding TD Consume vs TD Producer
   ... would see how to represent them
   ... note that there are extra red cells due to change of name,
   etc.
   ... important thing is the template
   ... and putting TDs under the testing subdirectory
   ... will migrate manual.csv
   ... we get the automatic test mechanism, that's great

   Ege: all the input here
   ... to be adapted with the latest TD changes

   McCool: right
   ... names, titles, etc.
   ... in this meeting next week, let's see the updates

TUM invite

   [20]https://www.w3.org/2002/09/wbs/1/WoTF2F201906/results

     [20] https://www.w3.org/2002/09/wbs/1/WoTF2F201906/results

   Kaz: Ege, is it possible for you to send an invite for TUM to
   all the registrants above?

   Ege: can do it

   [adjourned]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes manually created (not a transcript), formatted by
    David Booth's [21]scribe.perl version 1.154 ([22]CVS log)
    $Date: 2019/05/16 09:04:04 $

     [21] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [22] http://dev.w3.org/cvsweb/2002/scribe/
Received on Thursday, 16 May 2019 09:27:15 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 16 May 2019 09:27:16 UTC