<kaz> scribenick: FarshidT

Reviewing the minutes

<kaz> Apr-27 minutes

no objections. Will publish the minutes.

Going through the agenda

McCool: partial TDs
... multiple results in a query. Possibly related to https://github.com/w3c/wot-discovery/issues/16
... compare and contrast query/filter approaches
... we should discuss each major topic in a github issue.

Query and filter operations

Issue: https://github.com/w3c/wot-discovery/issues/17

McCool: (off-topic) creating an issue for partial/part of TD considerations.

Issue: https://github.com/w3c/wot-discovery/issues/21

TTL Support

Issue: Query and filter operations

McCool: is there a way for the consumers to know how long a thing has been alive
... adding additional use-case for when a device is ungracefully deinstalled or died.

Issue: https://github.com/w3c/wot-discovery/issues/18

McCool: different ways of setting keepalive info, TTL time boundary, configurable TTL boundary. (more info in github issue comments)

Farshid: use created/modified fields to know when TD was updated in directory

McCool: need to look into the specs to know what those fields refer to. They probably refer to TD creating time on the device.
... add directory-specific info an out-of-band and include the TD inside

Farshid: out-of-band info makes the submitted (TD) and queried (object with a TD) payloads inconsistent.

McCool: keeping the TD intact and avoiding the modification makes it possible to check the integrity of TDs
... push (device checks in) vs poll (directory checks the thing status) to know the status of things

Farshid: for polling, need a different implementation / access control for every protocol

McCool: can use a proxy to poll the device status without accessing the device itself

Kaz: have to establish trust between the device and proxy. maybe we ourselves don't have to think about the mechanisms but we should survey the existing mechanisms.

<inserted> McCool's updated comments for issue 18

Multiple results in a query response

McCool: adding points in a comment to the issue https://github.com/w3c/wot-discovery/issues/16

Farshid: pagination of TDs in API response, TDs are an array inside an object with pagination info (page, total, perpage)

McCool: what about a corner case, where an individual TD is very large

Farshid: we did break TDs in pagination as part of previous implementations but it adds complications to the client. And different pages may end up with different models when dealing with partial TDs.

McCool: notes added to issue 16: https://github.com/w3c/wot-discovery/issues/16#issuecomment-623514384
... would like to have a resolution on pagination issue next Monday, 11th

Closing

McCool: need to look at use cases to see if there discovery requirements to discuss the security issues

<kaz> [adjourned]