#1143: [wg/png] PNG Working Group Charter
Discussions
Log in to see TAG-private discussions.
Comment by @christianliebel Aug 28, 2025 (See Github)
@svgeesus Thanks a lot for the details! 😊
Discussed
Sep 1, 2025 (See Github)
Christian: charter looks OK to me. Jeffrey is concerned that the new compression algorithm is not backwards compatible. Should they introduce a new media type for that?
Martin: I think Jeffrey is entirely right. If you can't consume the content without new code, it's a new format.
Discussed
Sep 8, 2025 (See Github)
Christian: 4th ed includes HDR/SDR. 5th edition includes new compression algorithm that will break compatibility with existing image files. Thoughts so far are that we're fine with it, but they need to make sure you can treat the new images files safely. Martin suggestetd that if you need new code to interpret it, then it's a breaking change.
Yves: Same issue with all the containers that embed differnt formats. E.g. video like Matroska. I treat this as the same case.
Matthew: My read was that if it needs new code to interpret it, it's a new format. A way to make it safe is to duplicate the old format, but then you've lost the benefit. Don't see how this is fine if that's the way to solve it. That would be hard.
Jeffrey: There's a comment Christian linked to in the discusion that makes the point I would make: if existing decoders can't decode new files, then it's a new format. It's true that's been done in video codecs, but I think it's new for images, and we should hold that line. We also have 2 new generations and 3 new formats for images WebP, AVI..., JPEG XL that all do better than PNG. Any suggestion to break compatibility with PNG needs to be compared to those new formats and justify itself. We should be sceptical of any backwards-incompatible changes.
Christian: Do the same review resolutions apply to charter reviews?
Jeffrey: There are no rules; we can use what's appropriate. The text of the charter review is more appropriate than the code - it'll be pasted into the strategy repo thread.
Christian: I'd remove the resolution, add what you said to the proposed comment, and then we can discuss again. Will post to (TAG's) private repo for discussion.
OpenedAug 26, 2025
This issue was created because the 'horizontal review requested' label was added to § https://github.com/w3c/strategy/issues/514
This review is requested prior to the Advisory Committee Review.
New charter proposal, reviewers please take note.
Charter Review
Charter
Expected end of charter refinement phase: unknown
If applicable:
diff from previous charter
chair dashboard
Existing WG recharter
Horizontal Reviews: apply the Github label "Horizontal review requested" to request reviews for accessibility (a11y), internationalization (i18n), privacy, security, and TAG. Also add a "card" for this issue to the Strategy Funnel.
Communities suggested for outreach
Known or potential areas of concern
Where would charter proponents like to see issues raised? (this strategy funnel issue, a different github repo, email, ...)
This issue
Anything else we should think about as we review?
Note: proposed chairs should be copied @programmax
Charter facilitator(s)
<!-- Content below this is maintained by @w3c-tag-bot -->Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1143