Meeting minutes
Minutes
no objections to publishing
Developer Meeting preperation
<kaz> Discovery Slides
McCool: will use the Discovery time slot on April 17th
McCool: Discovery has half the assertions compared to TD, but there are twice assertions at risk
… we need to spend the next weeks to resolve as many as possible
Kaz: we need to specifically ask for some potential participants for the developer meeting
<Mizushima> +1 kaz
McCool: the list of implementations also isn't complete
… we could send a post to invite everyone
Kaz: we should invite at least all the known implementers
McCool: we have too many assertions to go through during an hour
… we can try to filter out some that are unlikely to be implemented
… 18 assertions have 1 implementation. It is easier to resolve those first.
… our deadline is May 17th.
… this gives us another two week to take care of editorial issues.
PRs
PR 469
Add workaround for mandatory response contentType:
McCool: the PR adds informative text
… merged
PR 470
<McCool> PR 470 - Rework RFC 9175 assertion and make it informative
<FarshidT> s/460/470 Rework RFC 9175 assertion and make it informative/
Kaz: we don't need to talk about all at-risk items during the dev meeting, but rather concentrate on the important ones
McCool: merged PR 470
PR 471
<kaz> PR 471 - Update context URLs
context file: https://
Farshid: the context isn't just for the directory, but rather the whole discovery. It is also used for self-describing devices and ThingCollection
McCool: it is better to split them into multiple context files
McCool: will document the discussion on Github and update the PR
<kaz> [adjourned]