Re: CALL for DISCUSSION: eXIf 20170115
Willem van Schaik <[email protected]>
| Newsgroups | gmane.comp.graphics.png.general |
|---|---|
| Message-ID | <[email protected]> |
I'm all for short and sharp. However it could help to add some explanation to make life easier for implementers. Like that the chunk data starts with "II" or "MM", so that people realize that it doesn't start with "Exif\0\0". Maybe not strictly necessary, but just to avoid confusion. With or without that addition, I would vote 100% YES on this. This is a simple problem to solve, let's not make it complicated. Willem On 2017-01-24 22:59, John Bowler wrote: > Here's my original proposal (12312016). I accept this is ambiguous, > although no one on this list ever advanced that criticism. While > later proposals may have disambiguated the words they did not change > the proposal: > > PNG CHUNK PROPOSAL: eXIf > > SPECIFICATION > ============= > > The four-byte chunk type field contains the decimal values > > 101 88 73 102 > > The eXIf chunk contains EXIF metadata with a length given by the chunk > length. Such data shall be compatible with specifications issued by > CIPA, "Exchangeable image file format for digital still cameras" [CIPA > DC-008-2016] or its successors. > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > png-mng-misc mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/png-mng-misc > > -- Willem van Schaik [email protected] ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot