W3C home > Mailing lists > Public > public-wot-ig@w3.org > July 2016

[beijing-f2f] minutes - prep day - 10 July 2016

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Mon, 11 Jul 2016 09:25:35 +0900
Message-ID: <CAJ8iq9X8Fh8N9sAHqbWZ+LC09GcV5nRe=pcs+y+hdmA5==-Ozw@mail.gmail.com>
To: Public Web of Things IG <public-wot-ig@w3.org>
available at:
  https://www.w3.org/2016/07/10-wot-minutes.html

also as text below.

Kazuyuki

---

   [1]W3C

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

                               - DRAFT -

        WoT IG f2f Meeting in Beijing - PlugFest Preparation Day

10 Jul 2016

   See also: [2]IRC log

      [2] http://www.w3.org/2016/07/10-wot-irc

Attendees

   Present
          Dave, Matthias, Sebastian, Darko, Joerg, Johannes,
          Takuki, Kaz, Yingying

   Regrets
   Chair
          Sebastian

   Scribe
          kaz

Contents

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

   sk: would like to ask you all about your devices

   da: LED board, MCU and proximity sensor

   (Sebastian take notes on the flipchart)

   da: and brightness sensor

   sk: what kind of scenario?

   da: the proximity sensor reads the proximity
   ... the sensor can detect the LED's brightness too
   ... there is a script to control how to change the color
   ... need scripts for the LED and the sensor
   ... and a micro event processor on another board
   ... changing RGB values

   sk: what kind of building blocks inside?

   da: using TD
   ... also use scripting

   sk: available online?

   da: not yet
   ... also might work with other devices

   sk: can work with Johannes's device?

   jh: 2 devices: (1) basic LED board regularly changes the
   brightness

   (Johannes connects his PC to the projector)

   sk: do you have brightness sensor?

   jh: shows the UI of the client "basicLed"
   ... another UI for "fancyLed"
   ... and "servient" and "counter"
   ... basicLed works on a raspberry pi and siemens light board
   ... "voter" UI to let people vote "tooCold" or "tooHot"
   ... servers upload TD to the repository
   ... shows concrete scripts for "voter"
   ... dynamically upload the script to the server
   ... collaboration for producing
   ... but experiencing some issue

   sk: people can download the script and run that locally?

   jh: yes

   sk: would be great if Darko's device can work with Johannes's

   mk: connects the projector to his pc
   ... brought this "BACnet Thing"
   ... BACnet controller - KNX Room Unit and Lighting
   Controller/Blinds Controller
   ... Simulated I/Os at the top
   ... lighting controller and blinds controller actuate devices
   ... overview and summary
   ... features and challenges
   ... error handling, interaction not fit property/action/event
   ... property-specific encoding, property-specific bindings
   ... sub-resource interaction, singleton event modelling
   ... can provide this device for others' scenarios
   ... would try, e.g., Johannes's servient and Panasonic's device
   in Japan using Echonet
   ... including TD, protocol binding

   sk: Nimura-san, short introduction for your device?

   nk: shows his slides on the projector
   ... one page
   ... Scripting API Implementation
   ... would connect with Simens's script

   sk: what kind of communication between LED and WoT servient
   smartphone?

   nk: legacy BLE interface
   ... App Script access the ExposedThing via the ConsumedThing

   rm: shows his slide
   ... Overview of our system
   ... smart home in Kanazawa, Japan
   ... server in Nagoya
   ... and the client here in Beijing
   ... Functional structure
   ... WoT I/F is supported on the server
   ... others are Fujitu's original I/F
   ... HTTP + XML/SOAP
   ... compatible to ITU-T standard
   ... shows live-stream video from Kanazawa, Japan

   sk: can we control this smart house from here?

   rm: yes
   ... but there is some network problem now
   ... will check with my colleagues tomorrow
   ... Nimura-san (and his client software) knows the IP address

   sk: shows his device
   ... Scenario Setup
   ... ESP8266 (NodeMCU), Temperature sensor, ...
   ... if it's too hot, the temp sensor detect that
   ... the sensor sends "search for action @type="tooHot" to the
   TD repository
   ... and the TD repository sends TD back to the sensor
   ... explains the sequence

   ka: the temp sensor is installed/attached to each person to
   detect who feels how?

   sk: yes

   (some more discussion)

   ka: inspired by Sebastian's demo scenario
   ... and think there is a possibility we need some smart
   decision maker module who makes decision on who to send which
   TD to whom based on the situation
   ... e.g., if the temperature is hotter than 100 degree
   centigrade, maybe the TD should be sent to the fire
   extinguisher/evacuation systems instead of the air conditioner
   [6]demo scenario on the flipchart

      [6] https://www.w3.org/wot-f2f/photos/10/DSC_0011.JPG

   Demo scenario on the flipchart (Click to enlarge)

   [7]Demo scenario copied on the wiki

      [7] https://www.w3.org/WoT/IG/wiki/F2F_meeting,_July_2016,_China,_Beijing#Scenario

   [ Prep day adjourned ]

Summary of Action Items

Summary of Resolutions

   [End of minutes]
     __________________________________________________________


    Minutes formatted by David Booth's [8]scribe.perl version
    1.144 ([9]CVS log)
    $Date: 2016/07/11 00:21:41 $

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



-- 
Kaz Ashimura, W3C Staff Contact for Auto, WoT, TV, MMI and Geo
Tel: +81 3 3516 2504
Received on Monday, 11 July 2016 00:26:50 UTC

This archive was generated by hypermail 2.3.1 : Monday, 11 July 2016 00:26:50 UTC