Re: DRAFT: eXIF 2017-03-05

> From: Cosmin Truta <[email protected]>
> Ok, Phil, I understand your objection. But could you please suggest an
> alternative formulation of that paragraph, removing the redundancy
> that you dislike, so that we can either adopt it as is, or rephrase it
> in a way that is to everyone's liking?

I would simply remove the sentence: "Any gap preceding an IFD is filled with bytes of unspecified content."

But since you asked for a rephrase, I would also make some other minor changes:

The data segment of the eXIf chunk contains an Exif profile in the format specified in "4.7.2 Interoperability Structure of APP1 in Compressed Data" of [CIPA DC-008-2016] except that the JPEG APP1 marker, length, and the "Exif ID code" described in 4.7.2(C), i.e., "Exif", NULL, and padding byte, are not included.  Therefore, it begins with a standard TIFF header (starting with either "II" or "MM", depending upon the byte order used), and contains a 0th IFD (Image File Directory) and optionally a 1st IFD.  The 0th IFD may contain pointers to an Exif IFD and/or a GPS IFD, and the 1st IFD (if any) contains a thumbnail image.

- Phil
------------------------------------------------------------------------------
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