WoT Discovery

24 May 2021


Andrea_Cimmino, Ben_Francis, Cristiano_Aguzzi, Ege_Korkan, Farshid_Tavakoizadeh, Kaz_Ashimura, Kunihiko_Toumura, Michael_McCool, Tomoaki_Mizushima

Meeting minutes

Minutes Review

<kaz> May-17

McCool: any objections?

(none and approved)


McCool: Update on the publication
… we should talk about the discovery slot in the F2F

<kaz> Proposed Topics within the vF2F agenda

McCool: (edits the agenda with the relevant topics)


McCool: what order should we do these?

Farshid: the top two are easy

<kaz> PR 179 - Replace interaction affordances in directory TD with a single link to its API endpoint

Ben: the third one influences the other ones

Ben: independently, with Ege, we seemed to have reached the conclusion that the TD is not needed

McCool: we have two uses for it, using @type to detect Thing or TDD

Ben: we replace the TD that had all the affordances with a link
… an advanced consumer would use the specification (human readable version)
… one question is the events

McCool: we can still add affordance

Ben: it proved difficult to describe everything in a TD

Ben: so we should do that out of band

Ben: why do we need the API to be protocol agnostic? we can make a new API for another protocol later on

<kaz> Issue 178 - Review Comments from Ege Korkan

Ege: In my issue, I did not mean that it should be protocol agnostic but what are the important parts of the API so that another protocol could also pay attention to that

McCool: let's ask for opinions

Andrea: I feel that it will make it difficult for features like search

Farshid: but how do we find other endpoints

Andrea: we are not removing the affordances by moving them to the uri variables

Cristiano: we should pay attention to the fact that security does not apply to the links

McCool: that is true, can you open an issue in the TD spec

Ege: we can also move it from links to a property

McCool: There is also Issue 178

McCool: There is a philosophical discussion whether TDD is a Thing or not

McCool: Intel's motivation is to do mashups of Things and Services

Cristiano: I think that TDD service is a very important part of the WoT

Ben: I don't think it makes sense to try to describe any service in a TD

Ben: by removing the TDD TD for now, we can solve the describing collection related issues in the meantime and have a TD for TDD later

(sorry I have forgotten to take minutes for the last 15 mins) but the discussions are documented by mm at Issue 178

McCool;s comments on Issue 178

<cris> btw I also agree that we should really be careful to not create a bad designed TD, but I think the propose refactors would improve the situation

<kaz> PR 158 - Combine properties into a single things property

<kaz> McCool's comments

<kaz> PR 160 - Rename actions to match properties and events

McCool: we do not have time left to work on the issues
… I suggest that people continue commenting on the issue 178

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

<kaz> [adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 131 (Sat Apr 24 15:23:43 2021 UTC).