Meeting minutes
Preliminary
meeting will last 2h
Minutes
meeting starts reviewing last meeting's minutes
<kaz> July-19
McCool: since no objections are presented, minutes are published
Cancellation schedule
McCool: next thing to discuss is cancellations, in august no discovery calls will occur
Publication timelines
McCool: regarding the timeline likely we will need an extension of 6 months
McCool: if we add 6 months we will end up in January or Febrary, when we should have the CR transition
… we need also the implementations
mccool is setting up the schedule for the charter end date
McCool: if we have a test fest in september, it will be pretty much the spec
McCool: since farshid will not be available, we could do instead the testfest early october
<McCool> https://
McCool: we could have the test fest a week before the breakout sessions
<kaz> [[
<kaz> 12 October: AC Meeting
<kaz> 18 - 22 October : Breakout sessions
<kaz> 25 - 29 October : WG/IG/BG/CG meetings and Joint Group Meetings
<kaz> ]]
McCool: the week of the 11th is probably a good week for the testfest
Testing
<kaz> WoT Discovery Implementations
McCool: one of our outcomes should be an implementation report
… for discovery
… we should start looking at the list of assertions to check which one are testable
McCool: ...we need implementation descriptions, and start gathering the implementations information
McCool: we need to talk also about testing. We need a test plan
… we need to organise where the test are
McCool: farshid has done some work on this line
Andrea: one of the main problems in the test is the ordering of the array
McCool: well we will change the context to solve this
<FarshidT> Related issue for JSON Array ordering: https://
<FarshidT> I think the spec does say indirectly that the order should be maintained: "A value of type Array MUST be serialized as JSON array". JSON arrays have a consistent ordering.
McCool: is drafting a testing plan
this plan should be the outcome of the testfest
McCool: October up to December we work on test of the implementation
Toumura: wondering about the procedure for the IANA consideration
Kaz: we should talk with PLH
… this is a bit different from the usual IANA registry for Media Types
<McCool> https://
McCool: we should close the issues we have opened, as suggested by farshid, before doing a feature freezing
Toumura: I have Issue 187 Issue 187 - Registration of Well-known URI, Service Name and CoRE Resource Type on that
McCool: for the implementations
Issues to be closed
farshid has annotated some Issues that could be closed
mccool is currently reviewing these
issue #9 gets closed since no objections are presented
<McCool> Issue 9 - Create structure to organize PoCs
<McCool> Issues to be closed
<kaz> Issue 16 - Handle huge set of Thing Descriptions (pagination, streaming, etc.)
next issue to close is issue #16
but for the moment it will be left opened
next issue to be review is #21
<kaz> Issue 21 - Consider Role "Part of" TDs in Query Results
since no objections are presented the issue is closed
next issue to be review is # 63, due to the lack of objections, the issue is closed
<kaz> Issue 63 - How to deal with JSON-LD fragments in query responses
next issue is #28, which is also closed
<kaz> Issue 28 - Directories should notify subscribers when a TD is updated
next issue is #53
<kaz> Issue 53 - Clarifying Introduction Mechanisms
closed
since no objections are presented for closing the issue, issue 53 is also closed.
<kaz> Issue 144 - Which aspects of the Directory Service API's TD are normative?
next issue is #144 which is also closed
<kaz> Issue 86 - "Thing description" for Directory should be a "Thing Model"
next issue is #86
that has been closed, mccool has also add a clarification in the clousure
<kaz> Issue 183 - Identifying what information is conveyed in the TD and what is conveyed in the text
next issue to be review is #183
<kaz> related PR 215 - Add HTTP paths to assertions
McCool: we should make the scopes for OAuth normative
McCool: the thing with this issue is that it has a lot of smaller issues, we should close this and create those smaller issues instead
McCool: maybe we should label as discuss to have some work tracked down
Farshid: there is a PR, if we close it we could close issue #60
current PR under review is #213, about alternative pagination
<kaz> PR 213 - Add alternative payload format (2)
next issue to be review is #39
<kaz> Issue 39 - Immutable Thing Description IDs inside the directory
there is a resolution for closing the issue, and therefore, issue #39 is closed
<kaz> next Issue is 208
<kaz> Issue 208 - Read-Only Directories
meeting finishes due to time
<kaz> [adjourned]