<scribe> scribenick: kaz
McCool: plugfest time changed
... now June 15-19
... would suggest we cancel the regular calls
... will make official resolution next Wednesday
... let's review the minutes quickly
McCool: we didn't really do a
doodle
... but simply shifted the date by 2 weeks
... (goes through the minutes)
... did some work on testing
... scenarios as well
... WISHI to be finalized
... would talk about the LinkSmart directory today
... typo of "Frsid"
... any objections to publish other than the typo?
(none)
McCool: approved
<McCool> https://github.com/w3c/wot-testing/tree/master/events/2020.06.Online
McCool: go through the wiki and get
resources
... then major sections for setup
... TDs for TD links
... and a section for data to be captured during the
PlugFest
... still ongoing
McCool: TD validation by
Playground
... TD archival to put actual TDs
... register TDs with the LinkSmart directory
... response from the W3C Systeam about VPN
... AWS instance for SoftEther
... they've already installed the software
... and we should set it up
... need to have some bridge software as well
... could be a Raspberry Pi
... the procedure is in progress
Kaz: can ask the Systeam to configure an account for you, McCool
McCool: ok
... we're making progress
... when we've got further information, will put it here on the
setup.md
McCool: there is a link to LinkSmart setting page
McCool: there is a demo page as well
McCool: and Swagger UI there
... could register TDs manually
Lagally: folder structure
... we had some more folders
... having at least "tools" would make sense
McCool: agree
Lagally: probably some tools to be used there
McCool: happy to add a "tools"
directory
... also maybe "prototype" directory
... (create a subfolder and add a placeholder README.md for
tools)
Lagally: another point
... going to have a lot of TDs there
... security credentials for different devices
... what would be the best way to handle them
... to get appropriate credentials properly
... for authorized users
McCool: let me add it to the To Do
list
... (adds it to the "To Do" list on the PlugFest agenda
wiki)
... maybe we could create a mailing list for credential
distribution
Lagally: any mechanism provided by LinkSmart?
McCool: no
... we have to add credentials to this
... we'll have to discuss this
Lagally: basic auth and TLS
McCool: yes
... it's kind of tricky to handle it with VPN, though
... need to see SoftEther configuration
... have to figure out how it works
... how to get keys and how to distribute it
... will think about it
... but probably could use a mailing list for that purpose
Kaz: we could ask all the TF participants for help, e.g., Suzuki-san
McCool: definitely
... (and then adds a subfolder for "scenario" and a placeholder
README.md)
... we already have some like retail
... any volunteers for scenarios?
Sebastian: would like to test features to query states/actions
McCool: yeah
... scenarios are about the usage
... we should document it
... (and adds "prototypes" subfolder and a placeholder
"README.md")
... descriptions of various prototypes
... will add links t othe actual resources
... like LinkSmart directory
... then AI serives by Intel
... Sebastian, you can add your idea here
Sebastian: Query state feature on actions
McCool: (adds it to the list)
... feel free to update the description
McCool: anything else?
... would agree with Kaz that people are encouraged to
volunteer and put their ideas here
... note that TDs are just TDs here
... we've agreed to use ".jsonld" as the identifier
McCool: already put (initial) TDs and also README.md
Kaz: is that the one from TPAC 2019?
McCool: yes, mostly
... copied it from TPAC 2019
Kaz: so people can copy the examples from TPAC 2019 and then add some extensions (if they want)
McCool: right
... (and then create "TDs/active.csv" as an example)
... "Org", "Name", Active"
... the "Name" corresponds to the one within the TD
... getting back to the "data" subdirectory
... the "data" subdirectory has some more subdirectories
... impl, interop and validation
Resources for the Implementation report
McCool: copied the resources from the previous PlugFest
McCool: others' results are also available above
https://github.com/w3c/wot-testing/tree/master/events/2020.06.Online/data/interop
s/inerop/interop Interoperability test reuslts/
McCool: resources for
interoperability testing
... will add detailed descriptions later
Lagally: data is pretty generic
... would be nicer to have more descriptive name/structure
McCool: anyway created an initial
structure
... please put your resources
... I have a todo list on the PlugFest wiki
[[
To Do
* Wiki update
* Scenarios
* Proposals and Prototypes
** LinkSmart directory service (Fraunhofer)
** AI Services (Intel)
* Credential distribution - mailing lists, need to capture links
* SoftEther VPN configuration and testing, bridge setup instructions
* Prework
]]
McCool: adding information to GitHub is good
Matsukura: I've set up an AWS instance for SoftEther myself too
McCool: would like to suggest you put
your information under the "tools" area
... e.g., vpn.md
Matsukura: some additional configuration is needed for the server
McCool: yes, e.g., reserved fixed IP
Matsukura: can provide some additional information
McCool: we could use some IPs within
some specific area
... e.g., from 128 up
Kaz: my question is which AWS instance to be used
Matsukura: ok with using the W3C one
McCool: in that case, let's ask the Systeam to give an account to Matsukura-san
Kaz: so we want to get two more accounts, one for Matsukura-san and another for McCool
McCool: right
... another question is semantic tagging
... to be discussed next time
Koster: tx for the heads-up
... will work on that
McCool: would put that into the directory
Koster: ok
[adjourned]