- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Wed, 02 Dec 2020 18:16:07 +0900
- To: public-wot-ig@w3.org, public-wot-wg@w3.org
available at:
https://www.w3.org/2020/10/01-wot-pf-minutes.html
also as text below.
Thanks a lot for taking the minutes, Ege and Michael Koster!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
WoT online PlugFest - Day 4
01 Oct 2020
[2]Agenda
[2] https://www.w3.org/WoT/IG/wiki/PlugFest_WebConf#Agenda_01.10.2020
Attendees
Present
Kaz_Ashimura, Michael_McCool, Ege_Korkan,
Hiroshi_Fujisawa, Hiroki_Endo, Kunihiko_Toumura,
Michael_Koster, Philip_Blum, Sebastian_Kaebisch,
Daniel_Peintner, Tomoaki_Mizushima, Cristiano_Aguzzi
Regrets
Chair
McCool
Scribe
Ege, mjk
Contents
* [3]Topics
1. [4]Guests
2. [5]Minutes Review
3. [6]Updates
4. [7]PRs
5. [8]NHK demo
6. [9]Map visualization
7. [10]AOB
* [11]Summary of Action Items
* [12]Summary of Resolutions
__________________________________________________________
Guests
<inserted> (Fujisawa-san, AC rep from NHK and Philipp from RIOT
OS again)
Minutes Review
<kaz> [13]Sep-30
[13] https://www.w3.org/2020/09/30-wot-pf-minutes.html
<inserted> scribenick: Ege
McCool: Any corrections?
... Seems not the case, publishing
Updates
McCool: LinkSmart directory is running
... it uses only .jsonld as the suffix
... MEIG will be in the F2F
<kaz> Agenda:
[14]https://www.w3.org/WoT/IG/wiki/PlugFest_WebConf#Agenda_01.1
0.2020
[14] https://www.w3.org/WoT/IG/wiki/PlugFest_WebConf#Agenda_01.10.2020
PRs
<kaz> [15]PRs
[15] https://github.com/w3c/wot-testing/pulls
<kaz> [16]PR 77 by NHK
[16] https://github.com/w3c/wot-testing/pull/77
<kaz> (merged)
<kaz> [17]PR 78 by NHK
[17] https://github.com/w3c/wot-testing/pull/78
<kaz> (merged)
Ege: update TUM TD file extensions
McCool: Let's see if the active.csv looking nice
<kaz> [18]PR 79 by NHK (active.csv)
[18] https://github.com/w3c/wot-testing/pull/79
<kaz> (merged)
<inserted> [19]active.csv here
[19] https://github.com/w3c/wot-testing/blob/master/events/2020.09.Online/active.csv
<inserted> [20]PR 81 by UNIBO
[20] https://github.com/w3c/wot-testing/pull/81
McCool: Could you explain the changes of the Unibo PR?
Cristiano: mostly adding TDs
McCool: I will check later again that active.csv is not broken
again
<kaz> [21]PR 82 by Fujitsu
[21] https://github.com/w3c/wot-testing/pull/82
Matsukura: we have a scenario proposal using the proxy
McCool: So you will keep working on it?
Matsukura: yes
Kaz: the LinkSmart server will get all the TDs from GitHub
automatically, so if Matsukura-san is OK, Fujitsu can provide
another TD for SmartLink as well as the current one for Fujitsu
proxy
McCool: Not sure if they break validation
<mjk> [22]https://github.com/w3c/wot-testing/pull/84
[22] https://github.com/w3c/wot-testing/pull/84
<inserted> scribenick: mjk
McCool: geolocation prototype and identication
... Node-RED has integrated some stuff for local discovery
[23]https://github.com/w3c/wot-testing/pull/85
[23] https://github.com/w3c/wot-testing/pull/85
Toumura: they are running outside of Node-RED
McCool: will review the Node-RED work again wrt. discovery
<kaz> [24]PR 86 by Fujitsu
[24] https://github.com/w3c/wot-testing/pull/86
McCool: Fujitsu uses mDNS discovery
... done with PRs
... agenda check, 15 minutes now for the NHK demo
NHK demo
<McCool_> (btw, forgot about map pr, will go back and look at
that after nhk demo)
Endo: (showing Node-RED flow)
... Node-RED nodes created using TD and node-gen
McCool: integrating devices from TUM and from Fujitsu
... is there a writeup in the README under the NHK directory?
(nhk lost audio connection)
McCool: can we capture screenshots from the demo and get the
video?
Kaz: I'm also asking them about that on a private channel in
Japanese.
Map visualization
Daniel: issue #76
[25]https://github.com/w3c/wot-testing/issues/76
[25] https://github.com/w3c/wot-testing/issues/76
Daniel: took data points and tried to render clickable
... need to standardize geolocation and UI information hooks in
TDs
McCool: created several example test cases
... strawman pattern with a geolocation object that has
internal properties
... accommodating dynamic geolocation data using a json pointer
link to a property
... proposing standard markup for internal properties of an
object and link semantics
Daniel: it's yet another way to define location
McCool: it follows the web geolocation API adds some additional
or missing properties
... need a standard ontology for geolocation information
... better to use annotation rather than specify a structure
Cristiano: difference between link references and a chunk of a
TD
McCool: JSON pointer is an internal link to an element in the
file
<kaz> [26]intel-geolocator.jsonld
[26] https://github.com/w3c/wot-testing/blob/master/events/2020.09.Online/TDs/Intel/intel-geolocator.jsonld
Koster: it adds a processing step to dereference the links
McCool: links can points to static or dynamic data items
Cristiano: the UI metadata can be another use case for links
Kaz: joint discussion with geospatial guy on Oct 7 will follow
up on the geospatial metadata question
AOB
McCool: AOB?
Kaz: NHK has just captured their demo and is wondering if it's
possible to show it now. or maybe tomorrow.
McCool: need to wrap-up for today...
<Philipp_Blum> Just a short question: I have seen the Community
engagement point in the readme. Do you want to have some input
from me for tomorrow? I can create a PR for that.
Philipp: what is the report out and feedback format from the
PlugFest?
McCool: create a github issue
[adjourned]
Summary of Action Items
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [27]scribe.perl version ([28]CVS log)
$Date: 2020/12/02 09:15:51 $
[27] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[28] http://dev.w3.org/cvsweb/2002/scribe/
Received on Wednesday, 2 December 2020 09:16:16 UTC