Meeting minutes
Agenda
meeting starts with points to do for having published the standard
Minutes
<kaz> Apr-11
first, minutes are review
McCool: several PR were merged, it was agreed to do normative freezing, and several issue were closed
several issues were marked as closed, today they will be review
mccool proposes publishing the minutes, and since no objections are presented, minutes are published
Use Case requirements
<kaz> coverage.csv
McCool: there is a request for reviewing the use cases requirements
… let's fill the column from discovery with categories
but for now let's skip it, the document completed will be available tomorrow
Testing
next point from agenda is testing
tdd must be uploaded into the wot-testing repository
this is an action for acimmino and farshid
also, using the template from wot-testing > events > templates > TestImplementation
<McCool> https://
fill it with the directory implementations
<McCool> pls put implementation description under Architecture also (see others already there...)
Explainer
<kaz> PR 300 - Create Explainer.md
<kaz> security-request issue 25 - WIP: Web of Things (WoT) Discovery 1.1 2022-04-27 > 2022-08-30
next thing in the agenda is the explainer
McCool: I created a PR but is still empty, we need this for the wide review
… I have created issues in Architecture, Security, Privacy, ....
PRs
next, PRs are reviewed
PR 288
<kaz> PR 288 - WIP: Implementation Report #288
first PR to be review is #288 on the implementation report. remains open
Issues
Issue 299
<kaz> Issue 299 - Feedback on latest Editor's Draft
first issue is #299
McCool: we should assign the different numbers from this issue to people
in order to handle them
<FarshidT> "A server that supports expirable TDs will realize such functionality as described in 7.2.1.2 Registration Expiry. During the partial update operation, if the resulting TD has ttl (relative expiry), the server will calculate and set a new expires (absolute expiry) value."
<FarshidT> "The HTTP server MUST serve the TD with a GET method. A successful response MUST have 200 (OK) status, contain application/td+json Content-Type header, and the TD in body. The server MAY provide alternative representations through server-driven content negotiation, that is by honouring the request's Accept header and responding with the supported TD serialization and equivalent Content-Type header."
mccool assigns the different numbers to people creating a comment in the issue
<kaz> 3, 4, 5: McCool
<kaz> 6: Toumura
<kaz> 7: Farshid, with assintance from Andrea
<kaz> Issues marked as "Propose Closing"
mccool, just for cleaning up, let's start closing the issues with propose closing label
Issues marked as "Propose Closing"
meeting is finished
<kaz> [adjourned]