WoT Discovery

<kaz> scribenick: andrea_cimmino

Prev minutes

Meeting starts reviewing the minutes

<kaz> Sep-14

some minor typo in conversation identified

one thing to thing for considering is using JSOS

McCool: we no longer make decisions to make public minutes during minutes
... from now on, minutes are published as draft in the public mailing list
... everything that is said in minutes will be public
... therefore, today we just mark the minutes as official

they are marked as official since no objections are presented

McCool creates a new issue, which is basically about using JOSE in Directory service

issue #71

<kaz> Issue 71 on JOSE

https://github.com/w3c/wot-discovery/issues/71

McCool creates the issue to suggest using the JOSE in the API

<McCool> https://github.com/w3c/wot-discovery/issues/71

no more follow up from the minutes

<kaz> RFC7520

Edge computing PoC

McCool: ...edge workers PoC for W&N is something interesting to work with. We should aim at considering this

TPAC agenda review

we move to talk about TPAC Agenda

<inserted> vF2F wiki

McCool: ...during the week agenda will be created, any conflicts?
... TPAC is allocated during 5 days
... anyone with conflicts or preferences for those days?

Cristiano has a conflict for the 22 of October

McCool: ...then, 20 or 21 will be picked

<kaz> vF2F agenda and conflicts

McCool: the 20th of October is the chosen day
... ...there are 3 hours allocated for discovery
... ...then, 20 min for discussion
... if nobody brings any question, issues will be reviewed
... each slot is already assigned, please be aware

Andrea: where is the template?

McCool: it is located in the WoT github under PRESENTATIONS folder
... in the 2020-10-online-f2f folder

(McCool prepares the slide set, uploads it to GitHub, and updates the template)

McCool: material outside the template, is not a problem as long as it is clear and available

<kaz> presentation template

<McCool> vF2F presentation area

McCool: ...in TPAC there are also join meetings
... some security issues have been created for the meeting, MEIG and PUB are join meetings that are related with the security issues
... for other issues that you may think are relevant for that meeting, label the issue with PUB or MEIG or the entity

<kaz> wot repo issues for the joint meeting agenda

McCool: meeting are short, therefore, issues will be prioritized
... issue #65 in wot-discovery should be reviewed, and the issue about signing TDs (all these related to the DID label)
... let's move on on the agenda
... for the plugfest we need to have a discussion to decide what to have
... it is basically next week, if you can make the plugfest call
... if you have homework, try to have it for Wednesday (meeting day)
... workflow probably will rely on creating TDs, and registering in Link Smart deployment
... we need to ensure that someone is running the Link Smart

Now meeting moves to next agenda item

PRs

<inserted> PR 70

first is #70 from Toumura-san

the PR is accepted and merged with no objections

<inserted> PR 47

next one is #47 from Andrea

Andrea: unfortunately, I could not rebase the project

McCool: I will add my review
... ...do you guys mind to have the discovery meeting during the plugfest?
... ...since no objection is presented, next week we will have the regular meeting of discovery
... ...likely during TPAC, we will need to cancel the meeting of th 5th

<kaz> vF2F time table

McCool adds the information about meetings (cancelation dates, and new dates) on the wiki

McCool: 28th of Sep remains untouched, October 5th is cancelled, and also October 19th
... 12th of October is held, unless there is a conflict
... October 26 meeting will be postpone

<inserted> Cancellation plan

Issues

Now meeting moves to next agenda item, issues

McCool: sequence diagrams, recently they have been added to the Architecture draft, I suggest to use the same tool

(issue https://github.com/w3c/wot-discovery/issues/69)

McCool: ...we want to look tools. plantUML used in discovery
... ...I was discussing in architecture meeting the necessity of having high-level diagrams for describing the process
... we should try to have such higher level diagrams

<kaz> wot-discovery - 5.3 DNS-Based Service Discovery

McCool: ...from now on, let's use the plantUML for diagrams
... generated images are under wot-discovery/images
... upload also the source files

<kaz> example source code of PlantUML for discovery

McCool: we should include more than only 2 actors in the diagrams (Producer, Directory, Consumer, Third-Party service)
... format to upload the images should be svg
... png is nice, but has quality loss
... let's upload both .svg and .png images, but the main one will be .svg (recall uploading also the .puml file)

<kaz> kaz: note that we've been using SVG for our specs and PNG also as fallback

(McCool updates the README with a plantUML reference)

<kaz> updated README

McCool creates an issue, for considering the use of WoT Directories for discovering compute services and utilities (related to Edge Workers)

issue #72, https://github.com/w3c/wot-discovery/issues/72

no more issues to talk about, time is finished for the meeting. For next time, review issue #53

<McCool> https://github.com/w3c/wot-discovery/issues/53

<kaz> [adjourned]