Re: CALL for DISCUSSION: eXIf 20170115

I'm not going to update my programs; they *write* exIf with the ID
code.  The previous convention has been to use a likely unique code on
private chunks to avoid clashing with other uses of the same private
chunk name, and I think that is a good convention to maintain.  It
doesn't make any difference to the proposal or testing it; skipping or
adding 6 bytes is easy and the code has to be changed anyway to write
a public change.

BTW, exiv2 handles the prefix by failing to load the EXIF; no bad
things happen if the prefix is not skipped.

John Bowler

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