- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Mon, 12 Jul 2021 12:42:47 +0900
- To: public-wot-wg@w3.org
available at:
https://www.w3.org/2021/05/17-wot-discovery-minutes.html
also as text below.
Thanks a lot for taking the minutes, Andrea!
Kazuyuki
---
[1]W3C
[1] https://www.w3.org/
– DRAFT –
WoT Discovery
17 May 2021
[2]IRC log.
[2] https://www.w3.org/2021/05/17-wot-discovery-irc
Attendees
Present
Andrea_Cimmino, Cristian_Glomb, Farshid_Tavakolizadeh,
Kaz_Ashimura, Kunihiko_Toumura, Michael_McCool,
Tomoaki_Mizushima
Regrets
-
Chair
McCool
Scribe
acimmino
Contents
1. [3]Minutes
2. [4]Updates
3. [5]Issues
4. [6]PRs
Meeting minutes
Minutes
[7]May-10
[7] https://www.w3.org/2021/05/10-wot-discovery-minutes.html
meeting starts reviewing the minutes of previous meetings
minutes are approved with no objections
and are published
Updates
meeting moves to updates
Kaz: cases will be updated tomorrow
Issues
meeting moves to issues, in order to close if possible some of
them
<kaz> [8]Issue 164 - Consider adding "poll hook" to
registration
[8] https://github.com/w3c/wot-discovery/issues/164
first issue been reviewed is issue #164
McCool: e issue is for adding a "poll hook" to registration
McCool: issue is quite complicate to be solved in time,
therefore, we should label it as Stretch goal
mccool labels the issue
McCool: s label is for marking non critical issues, which will
be still nice to have
<kaz> [9]Issue 156 - JSONPath and XPath response data models
[9] https://github.com/w3c/wot-discovery/issues/156
next issue reviewed is issue #156
mccool assigns to farshid the issue, under his request
<kaz> [10]Issue 154 - Publish updated WD
[10] https://github.com/w3c/wot-discovery/issues/154
next issue is #154, which is assigned to mccool
<kaz> [11]Issue 150 - Definition of Problem Details error types
[11] https://github.com/w3c/wot-discovery/issues/150
next issue is #150, which topic is using a specific schema for
errors
in this issue farshid presents a list of errors that may occur
in the directory
McCool: se errors should be aligned with error clases used by
Scripting API
McCool: uld use data schemas for error responses in Directory
TM, defined in wot thing description
Farshid: se errors are meant to be protocol agnostic, should we
define them as part of discovery? and also link to the others
mentioned?
McCool: re would you put the error type?
Farshid: will appear in the response body, in the "title" field
Farshid: comments could go to the link in the title, and check
how to solve or info of the error
McCool: think we still want to define errors codes for HTTP
Farshid: , but many things a lot of errors have the same HTTP
error code, these errors are more fine-grained
McCool: true, the problem is making these errors mandatory.
They should be optional
McCool: let's go ahead and do it. Later we will check the
security
as resolution, farshid will create a PR for this errors
<kaz> [12]Issue 149 - Anonymous TDs in a directory
[12] https://github.com/w3c/wot-discovery/issues/149
next issue been reviewed is #149
Farshid: this issue is resolved
McCool: I'm not totally happy with it, but I will mark it as
resolved
mccool closes the issue #149
<kaz> [13]Issue 148 - Discovery context and namespace under
w3.org/ns
[13] https://github.com/w3c/wot-discovery/issues/148
next issue been reviewed is #148
McCool: it is needed a resolution on this issue
McCool: the moment, let's keep using github's URL for the
JSON-LD documents contexts
next issue been reviewed is #146
McCool: this issue relates to pagination
McCool: is there any text describing this?
Farshid: not yet
McCool: we need this in the text
McCool: we need to add "head" request to all endpoints
McCool: not clear how to add this to the TD
McCool: how does this interact with pagination?
Farshid: it should be the same than a regular GET; just the
headers with no body
McCool: let's add an assertion
mccool assigns to farshid the issue
<kaz> [14]Issue 144 - Which aspects of the Directory Service
API's TD are normative?
[14] https://github.com/w3c/wot-discovery/issues/144
next issue been reviewed is #144
mccool answers the comments made previously in the issue
<kaz> [15]Issue 143 - SHACL validation
[15] https://github.com/w3c/wot-discovery/issues/143
next issue is #143
McCool: the issue is about SHACL validation
McCool: the problem with validation is that the json schemas or
shapes should be provided locally
mccool will tweak the text a bit to show the validation
optional
mccool concludes that JSON schema should be a "MUST" and SHACL
should be a "MUST"
(Kaz leaves for another call)
PRs
<kaz> [16]PR 177 - Remove payload-based event filtering
[16] https://github.com/w3c/wot-discovery/pull/177
first PR been reviewed is #177
Farshid: s PR is related with issue #176
mccool merges PR #177
<kaz> [17]PR 174 - Improvements to expiry
[17] https://github.com/w3c/wot-discovery/pull/174
next PR is #174
which is related to issue #18
mccool comments on the issue #18
mccool proposes closing the issue #18
since no objections are presented, the PR is merged
<kaz> [18]PR 175 - Updated directory to new ontology model
[18] https://github.com/w3c/wot-discovery/pull/175
next PR is #175
main issue is the class structure
cimmino will review the PR for next meeting
<kaz> [19]PR 173 - Directory TD refactoring
[19] https://github.com/w3c/wot-discovery/pull/173
next PR is 173
PR 173 is not close, we move to PR 160
mccool comments on the PR, giving 2 options to solve the PR
mccool is going to create an issue and relate it with the PR
additionally, he is setting up some actions for the PR
farshid volunteers for doing the renaming, one of the actions
setted up
in next meeting PR about pagination will be prioritised
[adjourned]
Minutes manually created (not a transcript), formatted by
[20]scribe.perl version 131 (Sat Apr 24 15:23:43 2021 UTC).
[20] https://w3c.github.io/scribe2/scribedoc.html
Received on Monday, 12 July 2021 03:43:03 UTC