[pwg] For Monday: Issues to be Closed

Hi PWG-ers,

As mentioned in the agenda, here is a list of issues that I believe we no longer need to have sitting in our backlog. The list is below with a link to the issue and a short explanation for my reasoning. If there are any strong objections please bring them up on Monday when we discuss this. If there are no strong objections I will be closing the issues directly after the meeting on Monday.

By closing any of these we are not suggesting the conversation is done, but for many of these issues we have left them for too long and if the issue is still applicable it probably needs to be reframed. Any issue in that situation should be opened with new context.

Issues:
https://github.com/w3c/wpub/issues/8 - refocus on security to address new structure of doc
https://github.com/w3c/wpub/issues/10 - same as above, can be continued in #321 and #374 if needed
https://github.com/w3c/wpub/issues/194 - long has sat in propose closing (this might also be made moot by recent changes to spec)
https://github.com/w3c/wpub/issues/314 - introduction of the canonical manifest means this should be closed
https://github.com/w3c/wpub/issues/321 - has sat in propose closing, remaining issue is now being worked on in https://github.com/w3c/wpub/issues/374 - let’s close this one
https://github.com/w3c/wpub/issues/342 - with the new data model, we can allow for the module to decide it’s pagelist requirements - core spec should provide the core pagelist requirements
https://github.com/w3c/wpub/issues/38 - issue of reading order seems settled with in-issue consensus on special ROs having their place (again potentially for modules to declare as well)
Affordances Issues:
                133, 134, 135, 137, 138, 139, 140, 141, 143, 144, 145, 146
                Affordances have been logged and moved to the other document, new affordances issues should be logged separately
https://github.com/w3c/wpub/issues/73 - could be closed after Matt adds clarification to https://w3c.github.io/wpub/#last-modification-date

https://github.com/w3c/wpub/issues/86 - should be covered in affordances, or more formal accessibility review
https://github.com/w3c/wpub/issues/150 - close in favour of related existing issues, solved issues, and for individual issues still required
https://github.com/w3c/wpub/issues/154 - has this been responded to, is it different now with the new format of the spec (Matt suggests we include a link to certification)
https://github.com/w3c/wpub/issues/173 - same as 174<https://github.com/w3c/wpub/issues/173%20-%20same%20as%20174>
https://github.com/w3c/wpub/issues/174 - these changes have been made
https://github.com/w3c/wpub/issues/176 - analysis complete and related issues logged (infoset question also complicated by changes to spec which may require more up-to-date issues)
https://github.com/w3c/wpub/issues/183 - minor consensus reached, manifest will not prevent this

Reply to this email if you will be unable to attend Monday, but otherwise hold any reservations until then.

Thanks,
Wendy


  Wendy Reid

  Senior Quality Analyst

  Toronto, Canada (GMT-5)

[signature_1855839069]<http://www.kobo.com/>

  [signature_939428565] <http://www.facebook.com/Kobo>

  [signature_864538626] <http://www.instagram.com/kobobooks>

  [signature_644909313] <http://twitter.com/kobo>

  www.kobo.com<http://www.kobo.com/>