W3C

WoT Discovery

09 Nov 2020

Attendees

Present
Kaz_Ashimura, Michael_McCool, Christian_Glomb, Kunihiko_Toumura, Farshid_Tavakolizadeh, Tomoaki_Mizushima, Cristiano_Aguzzi
Regrets
Chair
McCool
Scribe
FarshidT

Contents


<kaz> scribenick: FarshidT

Minutes

<kaz> vTPAC minutes

<kaz> Oct-12 minutes

McCool: will go through TPAC minutes. This will probably take a whole hour. Let's review the Oct-12 minutes first.
... "fix error" should be changed to "fix respec errors"
... no objections, publishing the discovery minutes.
... next is TPAC minutes
... ToC links are not working

Kaz: there was a typo. Fixed now.

McCool: who is Joshue108?

Kaz: that is Josh O Connor from the W3C Team

McCool: wondering about how to describe the scribes' names

Kaz: scribe names follow the IRC nicknames

McCool: typo: rought

Kaz: fixed

McCool: geospatial queries are complicated. Have to organize a call with them.
... well-know -> well-known
... add "for example" before "an ip address"

Kaz: fixed both

McCool: "we have consider" -> "we have been considering"

Kaz: done

McCool: sensible -> sensitive

Kaz: fixed

McCool: we gotta use TDD consistently. This was done well in the minutes.

Kaz: "verified credentials" -> "Verifiable Credentials"

McCool: "this topic" -> discussion on use during other stages

<inserted> kaz: fixed

McCool: what does "active" mean?
... it is about life cycle. Does "active" mean registered and ready to respond? Need to clarify. Making an issue.

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

McCool: described the issue on github.
... trusty -> trusted
... Creating a github issue for the point raised by kaz related to trustability, response time, etc

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

Farshid: it is also about directories that are meant as different registries. E.g. manufactured things vs operational things.

McCool: describing the issue on Github

Cristiano: this was also raised in TD call. Link above

McCool: going through Thing Model issue
... ben has downvoted, need to ask why

Farshid: why no keep the example TD instead of TD Model? The current example TD contains example security definitions.

Cristiano: TD Model spec may be extended to also allow model templating.

McCool: need to consider our use case in TD discussions (comment on github issue)

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

McCool: restfull -> RESTful
... adding an issue for JSON Lines (https://jsonlines.org/)

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

McCool: json-line -> JSON Lines
... updating the QUIC / HTTP/3 issue (https://github.com/w3c/wot-discovery/issues/84)
... Web Transport WG?

Kaz: that WG is expected to discuss how to apply QUIC to applications

McCool: W3C API

Kaz: this is about API design and pagination to access the W3C DB

McCool: commenting on issue https://github.com/w3c/wot-discovery/issues/16
... PATCH complications
... creating an issue

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

Kaz: we still need two implementations for optional features as well.

Farshid: the spec is already there, treating objects as plain JSONs

Cristiano: the protocol is fine. The request body may not be JSON-LD

McCool: stopping at Syntactic queries section
... will continue the minutes review next week
... merging PR https://github.com/w3c/wot-discovery/pull/89

closing

McCool: more cancellations in December

<kaz> We'll continue the minutes review from the topic on "Syntactic Queries"

<kaz> [adjourned]

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version (CVS log)
$Date: 2020/11/17 07:15:33 $