W3C

– DRAFT –
WoT Discovery

10 January 2022

Attendees

Present
Andrea_Cimmino, Christian_Glomb, Christine_Perey, Cristiano_Aguzzi, Farshid_Tavakolizadeh, Jan_Romann, Kaz_Ashimura, Kunihiko_Toumura, Michael_Lagally, Tomoaki_Mizushima
Regrets
McCool
Chair
Farshid
Scribe
acimmino

Meeting minutes

Minutes

meeting starts reviewing last minutes

<kaz> Dec-13

since no objections are presented, the minutes will be published

PR

the meeting moves forward to reviewing the PRs

there are 4, one of them is a draft

the rest can be reviewed one by one

PR 252

<kaz> PR 252 - Assertion for optional Notification API

PR #252 is about adding an optional to one assertion, it also includes some minor editorial notes

<kaz> preview for "6.2.2.3 Notification"

since there are no objections for the merging of this PR, it will be merged

PR 253

<kaz> PR 253 - Add Thing Model

next, the PR #253 is reviewed

this PR modifies the thing model, and the references are changed

the Thing Description is changed from normative to informative

<kaz> preview for "8. Directory Service API Specifications"

Christian: how this affects the implementations?

<cris> +1 LGTM

Farshid: ..your thing description is derived from the normative thing model

Christian: then in the implementation test, there will be something to check the fact that the thing description is derived form the thing model?

Farshid: yes

Farshid: what can be done in future, is adding an array of what is required
… but a new PR could specify it

Farshid: anyway, we can have more week for further reviews of this PR

Farshid: we could move also the td file in the root directory of the github to a sub-folder

Kaz: if this section describes different examples of deriving the model, we should clarify this in the document

Kaz: we could modify the title of the sections to show this

Farshid: yes, we can do that

farshid is writing as a comment all these decisions

Jan: Thing Directory should be added in the Thing Description specification ?

Farshid: the spec says that thing model should be replace for Thing in a partial implementation

Farshid: the problem here is that in the spec the assertion regarding the fact that thing model must be replace by thing is very strict
… and maybe it should be more flexible

Farshid: one last question, it seems there is an issue with the word Thing Model that appears in red

PR 251

<kaz> PR 251 - Change event type's naming convention to thing_<past-verb>

this PR is about changing the event types

Andrea: I would prefer not to have just one word without a separator

Kaz: we could use camel case

Farshid: there is just one issue, we have underscore for URI variables

Andrea: sse says something about this? because this would solve the issue

Farshid: it does not, they just provide examples

Farshid: an issue related to this is issue 28

Issue 28 - Directories should notify subscribers when a TD is updated

which requests to retrieve the argument in the events for subscribing to just one TD (this feature was remove in favour of JSON path, but now JSON path was removed)

Issue 100

next Issue review is #100

farshid proposes closing it, and open another for further discussions

discussion continues on #253

Issue 93

<kaz> Issue 93 - Consider using "JSON Lines" for large TDs

next issue is #93

<kaz> closed

Issue 98

<kaz> Issue 98 - Need information model for directory

<kaz> closed

Issue 178

Issue 178 - Review Comments from Ege Korkan

farshid sugest closing it

Issue 30

farshid suggest closing this issue

https://github.com/w3c/wot-discovery/issues/30 Issue 30 - Define out of band information

<kaz> closed

with this the meeting ends

<kaz> [adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).