Meeting minutes
Minutes
meeting starts reviewing the minutes from last meeting
McCool: GPR should be
GDPR
… and nvm, is that never mind? maybe just extend
that
Kaz: typos fixed
McCool: we forgot to publish a resolution to publish for PR357
since no objections for publishing the minutes, they are aproved
Quick updates
McCool: any updates?
Farshid: the tools for testing are mostly updated, next weeks they will be done
Farshid: notification is a work is progress
McCool: like 2 weeks?
Farshid: just a few days
Cristiano: could you share the link to the testing tool?
<FarshidT> Testing tool
repo: https://
PRs
PR 370
<kaz> PR 370 - feat: allow Content-Format 50 for CoAP in TD Server #370
McCool: including it in the CR would solve issue #365
McCool: if no objections are presented, this PR should be merged
PR is merged
Publication Preparation
<McCool>
https://
McCool: some things to
fix, the version in the link
… also the organisation of farshid
Farshid: I'm not sure about changing the organisation
Kaz: As I responded to Farshid by email, the affiliation should be "Invited Expert" now. If you want to explicitly mention that former work was done when you were at Fraunhofer, we can mention that as well.
Farshid: I can do the PR
Example spec with former editors:
https://
creates an issue, not a PR
Issues
Issue 371
https://
<kaz> static draft for publication preparation
McCool: I think the
rest of the document is clean, but please review
… also some editor's note maybe should be
removed
Issue 150 and 48
McCool: not sure about including note about Issue 150, and probably we could close note for issue 48
Farshid: we could close it, because it is solved
mccool navigates to the issue
Issue 48
https://
McCool: any objections for closing issue 48?
since no objections are presented the issue is closed
as a result, the editor note shall disappear
McCool: shall be remove this or add it in the spec?
Farshid: fixing this will be complex, it would be better removing
McCool: then let's remove it
Issue 150
<kaz> Issue 150 - Definition of Problem Details error types
McCool marks the issue 150 as deferred for discovery 2.0
Issue 99
https://
McCool: should we defer
this to TD spec?
… we could say that directories do minimum
validation
as resolution the spec will say "SHOULD perform at least Minimum Validation of TDs"
Farshid: we have this, but does not refer to minimum validation
McCool: let's do an informative sentence and remove the current one
<FarshidT> JSON Schema
of directory:
https://
Farshid: we also have a json schema for the directory itself, link is in the IRC
we should also say that validation should include the extension schema defined for directory
McCool: we could do an assertion of this
Farshid: in that case no implementation performs this feature
McCool: so the question is do we allow to reject a TD for any reason?
McCool: we could put in an appendix the JSON schema
McCool: could you farshid do a PR for the assertion
mccool takes note of this on issue 99, as well as the actions to be taken
Issue 176
https://
deferred to discovey 2.0
Issue 234
https://
deferred to discovey 2.0
Issue 82
https://
deferred to discovey 2.0
<kaz> s|s/topic: Issue 82/|subtopic: Issue 82|
PR 370 - revisited
McCool: should we try to add PR 370 into the CR?
https://
since the PR fixes a small piece of text it will be included in the CR
<kaz> [adjourned]