Meeting minutes
Minutes Review
<kaz> Nov-6
McCool: (goes over the minutes of the last meeting)
… discussed IEEE things, publications, Toumura-Sans PRs ...
… any objections to publishing?
None, minutes are approved
Publications
McCool: Let's talk about this first to make sure that everything is in good shape
… any updates here, Kaz?
Kaz: Not yet
McCool: So we are still waiting for the REC
… but we are in good shape, right?
Kaz: TD is also still in the last stage of publication
Remaining Issues
McCool: There are several issues in the category "Resolve by REC"
… we should either relabel those or mark them as closed
… an issue like #414 could be retired
… the acknowledgements issue could also be closed and be considered as "they are what they are"
… the publication issues will be resolved by publication
Issue 498
<kaz> Issue 498 - Update Acknowledgements
McCool: to resolve the acknowledgment issue, we should have a look at the document
… (opens the rendered version of the document)
… (goes over the current acknowledgements)
… is anyone seeing anything that is missing here?
No comments are made
McCool: Then I think we can close this issue and can have a look at it again for the next version
… (closes the issue)
Issue 410
<kaz> Issue 410 - Use TDD consistently
McCool: I think this one is editorial
… could be closed and revisited for the next version
… will change the label
… (adds the label "defer to Discovery 2.0", removes the "Resolve by REC" label)
Issue 414
<kaz> Issue 414 - make tdd-http-unsupported-feature manual
McCool: What does "manual" mean here?
… seems to be related to manual testing
… and about marking the assertion as manual
… this does not change the REC but only the Implementation Report
… (goes over the CSV table)
… is already marked as manual, so we can close this issue
… need to double-check this
… (checks the rendered implementation report)
… is here under manual, so let's close this one
Closes the issue
Kaz: A general question: I still need to create the transition request for Architecture, TD, and Discovery, and for that we still need to identify the outstanding issues
McCool: Everything that is not marked as "Resolve by REC" is deferred to the next charter
… all of the resources stuff should also be resolved by REC
… let me add the corresponding label
… and get rid of "End by Charter" as that is ambigious
Kaz: Those issues labeled as "Resolve by PR" or "Resolve by CR" could also be closed
McCool: I think these were mostly related to DID
Issue 467
<kaz> Issue 467 - Resolve Remaining DID issues
McCool: Here, everything mentioned in the issue is done
… except that we need a resolvable URL for the registration with the DID registry
… it is a funny one, as we have the REC and the resources, but we need to update the DID registry, which should be done before publication
… so I would mark this as "Resolve by REC" as well
… although it is not strictly necessary, I think it is a good idea
Issue 510
<kaz> Issue 510 - Update Requirements
McCool: We can simply remove the label here
Issue 445
<kaz> Issue 445 - Implementation Report Fixes
McCool: These should be mostly fixed
… anyway, I will remove the "Resolve by PR" label, we should check that all of the points are resolved
Issue 402
<kaz> Issue 402 - Register DID service names
McCool: As mentioned before, this is really "Resolve by REC", as it relates to resources, not an "End of charter" thing
Issue 328
<kaz> Issue 328 - CR WD review June 2022
McCool: This was feedback by Zoltan, should have been taken care of
… but let's defer it to version 2.0
… (adds the corresponding label)
Issue 327
<kaz> Issue 327 - Extend Thing Link use cases in the Explainer
McCool: Not a blocker, let's leave it open for now
Issue 111
<kaz> Issue 111 - Geolocation query filters for AR
McCool: Let me take out the label "Stretch Goal" here
<McCool> w3c/
McCool: and mark it as deferred
Issue 283
<kaz> Issue 283 - Organize Testing
McCool: This is done, so we can resolve it
… I am going to close it
Issue is closed
Issue 79
<kaz> Issue 79 - Define Geospatial query filter for Directories
McCool: I remove the "Stretch Goal" label from this issue
… is also a duplicate
Issue 440
<kaz> Issue 440 - Standardizing how to describe the location of the TD
McCool: I think this is mostly done
… but let's defer this
… (adds the "Defer to Discovery 2.0" label)
Labels for the remaining Issues
McCool: So to answer your question, Kaz, the issues labeled as "resolve by REC" are now the only ones left
<McCool> https://
McCool: question is, though, if they are blockers
… especially the DID issues
Kaz: I don't think they are blockers, maybe we should another type of label here, like "discovery-resources"
McCool: Okay, let's add a new label
… and call it "Resources"
… (creates the label)
<McCool> https://
McCool: (replaces the "Resolve by REC" label with the "Resources" label on the remaining issues)
McCool: So we can officially say we are done, but we only need to publish the resources
… anything else to do, Kaz?
Kaz: No, I don't think so
Use Cases and Requirements
McCool: We have three PRs by Jan
Issue 236 / PR 242
<McCool> Issue 236 - Associate Discovery Requirement with Use Cases
<McCool> PR 242 - Associate Discovery Requirement with Use Cases
McCool: PR is not yet done
Jan: no time to finish it
McCool: ok. let's see the preview then
McCool: need to think about the format too
Jan: some issue about trailing white spaces...
McCool: you also use "[[[ ]]]" notation for references
… we should use this new format consistently
… will make a comment about this on the Pullrequest itself
… (adds comments)
PR 241
PR 241 - Remove trailing whitespace
McCool: HTML itself doesn't care about extra white spaces
… but it would effect the diffs later
… so OK with merging this
(merged)
Discovery PRs
PR 523
<kaz> PR 523 - Update static version for REC publication
McCool: You told me that the process was updated but ReSpec was not, Kaz, is it fixed by now?
Kaz: Should work now
McCool: Let me try again
… let me try to render the document locally again
… (experiences some technical difficulties)
… I will deal with this later, I will send you a link
… once I get this working, I will immediately merge it and send a link to Kaz
Kaz: In the worst case, if ReSpec is still problematic, we can inform the Webmaster and move on with publication
McCool: It is just the publication process
… we can call the meeting adjourned, I will spend the rest of the allocated time to fix this
… (gets the document to render before the meeting is closed)
… (commits the new version)
… I think we can officially merge this now
… any objection to merging?
Kaz: Of the static version? I think that's fine
… (merges PR 523)
Merged
McCool: I will do the same for Architecture right after the security call, move to adjourn
[adjourned]