Re: CFD: eXIf 2017-06-10

> On June 15, 2017 at 1:02 AM Cosmin Truta <[email protected]> wrote:
> 
> 
> On 9 June 2017 at 11:49, Glenn Randers-Pehrson wrote:
> > CALL for DISCUSSION
> > eXIf 2017-06-10
> > ftp://ftp.simplesystems.org/pub/png-group/documents/eXIf/
> > png-proposed-eXIf-chunk-2017-06-10.html
> > Glenn Randers-Pehrson <[email protected]>
> >
> > also available at
> > http://www.simplesystems.org/png-group/proposals/eXIf/png-proposed-eXIf-chunk-2017-06-10.html
> 
> Hi,
> 
> The 2017-06-10 edition of the draft is very good. I would like to make
> a suggestion to make it better, if only a little. (I emphasize on
> _suggestion_, because I would vote "yes", regardless whether my
> suggested change gets accepted or not.)
> 
> I suggest moving the 2nd bullet point from the section "eXIf
> Recommendations for Decoders", to a separate section called "eXIf
> General Recommendations", or "eXIf Interoperability Considerations",
> or something else that is neither specifically "for decoders", nor
> "for encoders", nor "for editors", nor for any other specific category
> of implementations.
> 
> 
> == eXIf Interoperability Considerations ==
> While the PNG specification allows the chunk size to be as large as
> 2^31-1 bytes, application authors should be aware that, if the Exif
> profile needs to be interoperable with the JPEG format, the total
> length of the eXIf chunk data may need to be adjusted to not exceed
> 2^16-9 bytes, so it can fit into a JPEG APP1 (Exif) segment.
> ==

I agree with these suggestions and have posted an updated proposal at
http://www.simplesystems.org/png-group/proposals/eXIf/png-proposed-eXIf-chunk-2017-06-15.html

Attached to the proposal is a provisional updated PNG extensions
document (version 1.5.0) with proper internal cross links, etc.

Glenn

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot