<inserted> (Fujisawa-san, AC rep from NHK and Philipp from RIOT OS again)
<kaz> Sep-30
<inserted> scribenick: Ege
McCool: Any corrections?
... Seems not the case, publishing
McCool: LinkSmart directory is
running
... it uses only .jsonld as the suffix
... MEIG will be in the F2F
<kaz> Agenda: https://www.w3.org/WoT/IG/wiki/PlugFest_WebConf#Agenda_01.10.2020
<kaz> PRs
<kaz> PR 77 by NHK
<kaz> (merged)
<kaz> PR 78 by NHK
<kaz> (merged)
Ege: update TUM TD file extensions
McCool: Let's see if the active.csv looking nice
<kaz> PR 79 by NHK (active.csv)
<kaz> (merged)
<inserted> active.csv here
<inserted> PR 81 by UNIBO
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> PR 82 by Fujitsu
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> 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
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> PR 86 by Fujitsu
McCool: Fujitsu uses mDNS
discovery
... done with PRs
... agenda check, 15 minutes now for the 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.
Daniel: issue #76
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> 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
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]