Re: DRAFT: eXIf 2017-03-09

On 11 March 2017 at 22:18, Glenn Randers-Pehrson wrote:
> Mainly what it achieves is to remind encoders that are
> converting a TIFF with widely-separated IFDs that they
> either have to fill in the gap with whatever they like,
> or, more sensibly, remove the gaps and adjust the
> pointers to the IFDs accordingly.  For people copying
> a JPEG APP1, not so much, because that has probably
> already been taken care of.

Ok. Let us leave the normative section intact, as Phil and John have
suggested, and let us say what Glenn considers it important to say, in
an informative section.

I agree that this is an important reminder, and I also agree that it
needs not be in the normative part of the specification.

**

eXIf Recommendations for Encoders

The EXIF specification allows areas of unspecified content around the
TIFF IFD structures. Encoders should not leak uninitialized memory
into these areas.

**

Sincerely,
Cosmin

------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford