Meeting minutes
New Business
janina: tpac breakouts open until late Oct
Sheri_B-H: will submit MM/AI intersection
Fazio: have already submitted general conversation
janina: Might not make TPAC date for publication
janina: getting commenters to agree takes the time
CharlesL: put in a CSUN proposal
Sheri_B-H: David and I have put in a workshop proposal
Sheri_B-H: and I put in an accessible procurement proposal
Triage New Github Issues
Fazio: lots of comments from Karl Groves and Kevin White
Fazio: nothing huge, lots of room for tightening things up
<Fazio> w3c/
<gb> Issue 320 Misleading Statement In Research And Standards Review (by Helixopp)
general consensus that this issue is editorial
<Fazio> w3c/
<gb> Issue 319 Research And Standards Review Misplaced (by Helixopp)
janina: not aware that we follow the Microsoft "explainer" approach for notes
janina: most of our audience won't know to look for a second document
Fazio: added comment to 319
david flagged both 319 and 320 as documentation
<gb> Issue 318 Term Proof Point Isn't Clear (by Helixopp)
Sheri_B-H: this is the fight I had with Jeff 4 years ago.
janina: users can change the terms to something that works better for their industry
Fazio: Kevin had another comment about tightening up the Proof Point definition
318 will be assigned to Sheri, she will write a small section in the intro (which she thought was already there). There are references to customization in the spreadsheet
<gb> Issue 317 Inconsistent Heading Style (by Helixopp)
jkline: are any of these show stoppers?
fazio: we need to review each of these to understand that.
Fazio: read out Kevin's email since it didn't go to the public email list
Janina: Fazio to send an email to Kevin asking him to put the rest of the issues in and telling him where he stopped
jkline: ask him to flag the ones he feels need to be solved before the release
Janina: absolutely need to fix inconsistent heading style, flag as editorial
Neha will take care of it
<gb> Issue 316 Communications Proof Point Structure is Too Deep (by Helixopp)
related to 317, assign to Neha
2.5.1.1.1 and deeper need to be moved back one level
<gb> Issue 315 Adjust Proof Point Information Architecture (by Helixopp)
janina: heading structure is better for screen reader users. For example, definition lists are used for document authors, and it is way too chatty
janina: this was an intentional choice where the AT benefits are a side effect
<gb> Issue 314 Abstract Is Too Salesy (by Helixopp)
janina: removed some of the "salesy" stuff previously
Sheri_B-H: we need to put explanations for the acronyms
Fazio: Karl also mentioned acronyms, we need to do a complete review and make sure all acronyms are spelled out the first time
we will pick this up next week