Meeting minutes
Agenda
<Lagally goes through the agenda>
Quick updates
Lagally has created a Profile issue based on yesterday's discussion.)
@@@ 258 for profile
Minutes
McCool: note that for publication preparation, we need to update the index.html file instead of editing the Overview.html file directory, because Overview.html will be overwritten by ReSpec
… Kaz, please make sure it with Toumura-san
Kaz: ok
(minutes approved)
Call time
Lagally: generated to a new Doodle to see a possible consolidated slot for Profile and Architecture
Issues to close
Issue 522
Issue 522 - Identify Additional System Components
closed
Issue 533
Issue 533 - Lifecycle section: Incorporate review feedback from security group
closed
Issue 534
Issue 534 - Terminology: Consistenly use "Thing Model" across requirements, use cases, specs
closed
Issue 546
Issue 546 - Revise list of co-editors
closed
Issue 551
Issue 551 - Introduction text to chapter 8.1
closed
Issue 552
Issue 552 - Lifecycle intro text
close
Issue 556
Issue 556 - Introduction for Profile section (9.2)
Lagally: for the moment, we don't need this
McCool: need to deal with the TAG review comments around this separately
Lagally: ok
closed
Issue 591
Issue 591 - Clarify optionality discovery mechanisms in section 8.4
closed
Issue 610
Issue 610 - Review / update list of editors
closed
others
(The following issues have been also closed)
652
775
806
Lagally: need Toumura-san for 813
New issues
Issue 817
Issue 817 - Review for unnecessary normative statements [TAG feedback]
McCool: TAG issues should be closed by the TAG
Lagally: ok
McCool: breaking up this issue into smaller issues would make sense
Lagally: what kind of label to be added to this issue?
McCool: can leave it asis
Kaz: maybe putting "tag-needs-resolution" label as usual would be useful so that they can pick it up easily later
Lagally: (adds the "tag-needs-resolution" label)
Issue 818
Issue 818 - Consider whether this makes more sense as a Note [TAG feedback]
Lagally: (adds the "tag-needs-resolution" label to issue 818 as well)
PRs
PR 792
PR 792 - Chapter 9: editorial fixes
merged
PR 795
PR 795 - Address feedback from i18n group
merged
McCool: note we need to think about how to deal with the reference by ReSpec reference
PR 799
PR 799 - Clarifications on discovery
Kaz: changes requested McCool have been applied. right?
Lagally: yes
merged
PR 813
McCool: need to check the link using the Link checker
Kaz: will check with Toumura-san
merged
McCool: we need to fix the index.html under publication/ver11/2-wd
Kaz: seems this PR includes both index.html and Overview.html
… so should be OK
Lagally: I'll also check with Toumura-san
PR 785
PR 785 - WIP: Impl rep update - end of June
McCool: we can merge this PR
… may need some cleaning up later, though
… fixing markup, etc.
… can work on another update
Lagally: ok
merged
Publication
812
<mlagally> Issue 812 - update change log for WD publication
Lagally: related to the change log
… (shows the HTML diff)
HTML diff from the previous draft
assigned to McCool
Issue 805
Issue 805 - Update CoRAL reference
Lagally: thought it had been done
(checks the draft)
Lagally: still need to be updated
assigned to McCool
APA review
Issue 796
Issue 796 - Accessibility (APA) review
assigned to McCool
TAG feedback
issues labeled as "tag-needs-resolution"
Issue 808
Issue 808 - Markup normative sections in Chapter 8
Chapter 8 (which is now Chapter 6. Abstract WoT System Architecture)
McCool: need to identify which subsection is informative
Lagally: let's put another labeled "resolved"
McCool: we can revisit it
Issue 809
Issue 809 - Fix normative references / convert to informative, where applicable
McCool: the question here is if we can check the feature at the implementation level
… related to issue 811
… and 817
Lagally: can I assign you?
McCool: fine. it's part of the core issue
… related to 816 as well
Lagally: (assigns Issue 816 as well to McCool)
(McCool got new assignment for 817, 816, 812 and 811)
Kaz: what about 809?
McCool: put me on 809 too
Kaz: tx!
808
Issue 808 - Markup normative sections in Chapter
closed
Issue 818
Issue 818 - Consider whether this makes more sense as a Note [TAG feedback]
Lagally: (adds notes)
… in this charter period, we decided to update the 1.0 document which is a REC.
… changing the status from REC to Note and other substantial changes at this point is not feasible.
[adjourned]