VOTE NO: eXIf 2017-0119
John Bowler <[email protected]>
| Newsgroups | gmane.comp.graphics.png.general |
|---|---|
| Message-ID | <CAP7U39-0Nv4OaqKNo5xzga2sFQWT-PQYgAZutBVjmtB4EL6qgA@mail.gmail.com> |
NO eXIf 2017-0119 ftp://ftp.simplesystems.org/pub/png-group/documents png-proposed-eXIf-chunk-2017-0119.html John Bowler <[email protected]> When people started to discuss it it became clear to me that the issues raised by a safe-to-copy chunk containing unsafe-to-copy data are intractable. The simple proposal "eXIF is a chunk containing EXIF" is actually sufficient; the standard PNG editor rules work, but it can be improved by specifying the behavior of non-applicable data (e.g. chroma subsampling information) and adding restrictions on PNG encoders (don't encode stuff that can be encoded as a PNG chunk unless there already is an EXIF tag; e.g. don't invent an 'sBIT' EXIF tag). I'm voting NO both because the current proposal doesn't work and because the simple unsafe-to-copy alternative (now I've worked it out) is easy and will work. -- John Bowler <[email protected]> +1 (541) 450-9885 PO BOX 3151 KERBY OR 97531-3151 USA ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot