[PNG] (Short) meeting topics for July 11th, 2022

Hello everyone,

Our next meeting is this coming Monday, July 11th, 2022 at 11am US Eastern
Time.
We don't have much to discuss so it will likely be a short meeting (10-15
mins).

The topic is GitHub issue 126 <https://github.com/w3c/PNG-spec/issues/126>
[1].
In the Feb 21st, 2022 meeting
<https://lists.w3.org/Archives/Public/public-png/2022Feb/0003.html> [2] we
decided to not explicitly define behavior which would resolve an ambiguity.
Any action (explicit definition) has a cost. We didn't know of any real
world issues resulting from this ambiguity. We only knew about the
deliberately crafted example image that demonstrates the ambiguity. As a
result, there was no benefit to be won from the cost paid.

However, the image was not deliberately crafted. It is from a bug report
that stemmed from a real world issue.



A side note on progress:
- I took a detour to add a feature to ReSpec that would be useful for us
<https://github.com/w3c/respec/pull/4200> [3]. It should be landing soon.
- Chris Lilley made progress on GitHub issue 82
<https://github.com/w3c/PNG-spec/issues/82> [4].
- I made some progress on GitHub issues 122
<https://github.com/w3c/PNG-spec/issues/122> [5] and 123
<https://github.com/w3c/PNG-spec/issues/123> [6].

Once those last two bullet points land, the only thing blocking WD is
fixing ReSpec errors and warnings.

Does anyone know if we're allowed to make minor editorial (non-technical)
changes between WD and CR? Would doing so complicate things? I ask because
I would like to polish.


Thanks!
- Chris B


[1] https://github.com/w3c/PNG-spec/issues/126
[2] https://lists.w3.org/Archives/Public/public-png/2022Feb/0003.html
[3] https://github.com/w3c/respec/pull/4200
[4] https://github.com/w3c/PNG-spec/issues/82
[5] https://github.com/w3c/PNG-spec/issues/122
[6] https://github.com/w3c/PNG-spec/issues/123