Meeting minutes
Logistics
McCool: no news
… w.r.t. VPN, did not use it yet
Philipp: issues connecting VPN, might be related to my router
McCool: Who is on VPN
<kaz> Plugfest page listing VPN participants
Kaz: there is a diagram including the VPN participants by Tomura-SAN
PRs
PR 165 from Intel
<kaz> https://
McCool: Intel TDs still need to be fixed
PR 171 from Siemens
<kaz> https://
McCool: Update from Siemens
… readme, active devices and link
Daniel: linked the sub-projects to avoid duplicate content
McCool: Yes, makes sense to consolidate data
PR 172 from Hitachi
<kaz> https://
McCool: Diagram an root README includes all devices. Nice!
… Next, PR#172 from Hitachi
McCool: Issue with @type and TDD
… issue created, see https://
<kaz> new issue 224 on wot-discovery about that point
Christian: Question: what is the right context to be used for TDD
… ns/td or /td/v1
McCool: Should resolve to the same context file
… need to check spec
SK: At the moment we do have temporary context file
… for 1.1. there will be 2022 namespace
Christian: TD spec uses /ns/td
SK: Only the editor draft
McCool: let's merge https://
Kaz: We should be clear about namespace for PlugFest
… maybe adding a note in README
McCool: PR by NHK looks fine, merge https://
<kaz> "https://
Daniel: I think "https://
<kaz> ver 1.0 spec REC uses "https://
<kaz> ver 1.0 spec ED uses "https://
McCool: Everyone should check TDs w.r.t. to context otherwise SPARQL does not work properly
Issues
Size of wot-testing repo
https://
McCool: I think we can delete branches, did so already
… Ege mentions we should not use PDFs or PPTX et cetera
… for the next PlugFest we might need to find a solution
Farshid: CI copies 1 level only, no history
Ege: don't think we should use GH for history
<sebastian> (Sebastian leaves)
Ege: at some point it will be a problem
Kaz: I think the biggest problem is to decide where to put data (in which repo)
… maybe wot-testing should contain only bare stuff for testing
Project: Siemens / Logilab TDD
https://
McCool: partial TDD
… is anyone registering to this directory?
Christian: not sure... but I can upload TDs
Farshid: cloud version is not running
… can expose local version
McCool: link-smart directory service up would be great
… could register TDs and see if we encounter issues (with the script we had)
Farshid: The script could be used for *any* directory... not just link-smart
<FarshidT> sync script: https://
Toumura: I use SPARQL at the moment
McCool: Siemens TDD does not support JSON path
… we might look at test results for support
Farshid: Note: Link-Smart is open-source but Fraunhofer might stop working on it
… I will create clone and continue working on it
Christian: will take a look at script to upload TDs
Next steps
Kaz: I think we should start looking *who* wants to connect which device etc
McCool: Good point, lets create issue
McCool: idea is to add a note to the issue. In the end we should be able to create table
Toumura: ECHONET devices (LED, air conditioner, sensors) were connected from NodeRED
McCool: planned to do Geolocation test (not sure if I manage)
Ege: My student from TUM did some tests
… testing all devices
Kaz: We should clarify what "device" ...not just ECHONET or TUM but rather LED and coffee machine
<kaz> network connection diagram
Ege: student will add documentation to this issue, see https://
Kaz: NHK is providing digital twins via their emulator. will ask them to clarify the detail.
Philipp: failed connecting Arduino / RIoT
… tried OpenVPN client... but router does not interconnect properly
Kaz: using mobile phone connection might be a possibility
Philipp: Good point, will look into
Cristiano: Unibo Farm is online
… at the moment I look into node-wot and actions
… tested SPARQL also but run into some issues
<kaz> [adjourned]