AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
July 2007

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



Valid HTML 4.01!



Thread

2007.07.04 16:56 "BigTIFF extension", by Kemp Watson
2007.07.04 17:35 "Re: BigTIFF extension", by Andrew Brooks
2007.07.04 18:13 "Re: BigTIFF extension", by John Aldridge
2007.07.04 18:51 "Re: BigTIFF extension", by Toby Thain
2007.07.05 10:27 "Re: BigTIFF extension", by Andrey Kiselev
2007.07.04 18:25 "Re: BigTIFF extension", by Phil Harvey
2007.07.04 18:52 "Re: BigTIFF extension", by Toby Thain
2007.07.04 19:59 "Re: BigTIFF extension", by Phil Harvey
2007.07.04 21:23 "BigTIFF extension", by <kemp@extelligence.net>
2007.07.04 21:36 "Re: BigTIFF extension", by Toby Thain
2007.07.05 05:08 "Re: BigTIFF extension", by Joris Van Damme
2007.07.04 22:11 "Re: BigTIFF extension", by Stephen Carlsen
2007.07.05 02:41 "Re: BigTIFF extension", by Joris Van Damme
2007.07.05 04:19 "Re: BigTIFF extension", by Kemp Watson
2007.07.05 04:54 "Re: BigTIFF extension", by Stephen Carlsen
2007.07.05 15:54 "Re: BigTIFF extension", by Toby Thain
2007.07.05 16:18 "Re: BigTIFF extension", by Joris Van Damme
2007.07.05 16:51 "Re: BigTIFF extension", by Andrew Brooks
2007.07.04 20:52 "Re: BigTIFF extension", by Joris Van Damme
2007.07.04 21:04 "Re: BigTIFF extension", by Toby Thain
2007.07.05 05:07 "Re: BigTIFF extension", by Joris Van Damme
2007.07.05 10:06 "Re: BigTIFF extension", by John Aldridge
2007.07.05 13:23 "Re: Tiff Digest, Vol 38, Issue 12", by Gary Mcgath
2007.07.05 13:56 "Re: Tiff Digest, Vol 38, Issue 12", by Joris Van Damme
2007.07.05 14:14 "Re: Tiff Digest, Vol 38, Issue 12", by Gary Mcgath
2007.07.05 14:39 "Re: Tiff Digest, Vol 38, Issue 12", by Joris Van Damme
2007.07.05 21:04 "Re: Tiff Digest, Vol 38, Issue 12", by Chris Cox
2007.07.05 21:38 "Re: Tiff Digest, Vol 38, Issue 12", by Joris Van Damme
2007.07.05 22:02 "Re: Tiff Digest, Vol 38, Issue 12", by Toby Thain
2007.07.05 15:26 "Re: Tiff Digest, Vol 38, Issue 12", by Andrey Kiselev
2007.07.05 16:23 "Re: BigTIFF", by Gary Mcgath
2007.07.05 16:54 "Re: BigTIFF", by Joris Van Damme
2007.07.05 18:51 "Re: BigTIFF", by Craig Bruce
2007.07.05 20:30 "Re: BigTIFF", by Gary Mcgath
2007.07.05 21:03 "Re: BigTIFF", by Joris Van Damme
2007.07.05 20:14 "Re: BigTIFF", by Michael Wolf
2007.07.05 08:09 "Re: BigTIFF extension", by Andy Cave
2007.07.05 13:40 "Re: BigTIFF extension", by Joris Van Damme
2007.07.05 21:00 "Re: BigTIFF extension", by Chris Cox
2007.07.05 21:19 "Re: BigTIFF extension", by Joris Van Damme
2007.07.05 22:13 "Re: BigTIFF extension", by Bob Friesenhahn
2007.07.06 12:36 "Re: BigTIFF extension", by Gary Mcgath
2007.07.09 14:10 "Re: BigTIFF extension", by Joris Van Damme
2007.07.09 15:11 "Re: BigTIFF extension", by Toby Thain
2007.07.09 16:11 "Re: BigTIFF extension", by Stephen Carlsen
2007.07.09 16:21 "Re: BigTIFF extension", by Andy Cave
2007.07.09 16:25 "Re: BigTIFF extension", by Gary Mcgath
2007.07.09 16:35 "Re: BigTIFF extension", by Toby Thain
2007.07.09 18:36 "Re: BigTIFF extension", by Phil Harvey
2007.07.05 16:26 "Re: BigTIFF extension", by Joris Van Damme
2007.07.05 18:56 "Re: BigTIFF extension", by Toby Thain
2007.07.04 19:17 "Re: BigTIFF extension", by Frank Warmerdam
2007.07.05 20:31 "Re: BigTIFF extension", by Chris Cox
2007.07.04 19:13 "Re: BigTIFF extension", by Bob Friesenhahn
2007.07.05 16:32 "Re: BigTIFF extension", by Kemp Watson
2007.07.05 18:10 "Re: BigTIFF extension", by Joris Van Damme

2007.07.09 14:10 "Re: BigTIFF extension", by Joris Van Damme

Gary,

Gary McGath wrote:
> To make it clear what species of dog I have in this fight: I'm looking
> at the issue primarily from an archiving standpoint. If people a
> hundred years from now dig through the metaphorical ruins and find a
> file and a copy of the relevant specification, will they be able to
> reconstruct its presentation?
>
> If BigTIFF is incorporated into the official spec as TIFF 7.0 _and_
> it's widely disseminated enough that it effectively supersedes TIFF
> 6.0, then that's accomplished; otherwise they'll see something which
> looks sorta like TIFF, and they might or might not be able to reverse
> engineer the differences.

Though we seem to arive at different conclusions, our way of thinking is not 
much different. I too, look at it from this archiving standpoint. I'm a 
strong believer in open formats, for the simple reason that I believe a 
user's data should be regard his own property to move into and out of 
applications as he sees fit. I too, have this notion of 'digital dark age', 
and I ask myself constantly if our grandchildren will be able to view our 
data.

I think we should work from the assumption that we'll succeed in having 
BigTIFF incorporated in a TIFF 7.0, or at the very least that we'll succeed 
in having some official form of the proposal as official specification 
supplement. If we don't work from that assumption and towards that goal, our 
work is not of much value.

Sofar, the official owner of the TIFF format has neither officially 
accepted, nor officially rejected BigTIFF. Let's wait and see, and help out 
all we can, and push things as hard as we can, and assume that the owner 
will do the responsible thing.

> If BigTIFF had been conceived from the beginning as a revision rather
> than a variant of TIFF, I suspect some things would have been done
> differently. For example, the new header might have specified whether
> to use classic or expanded format for the IFD offsets, the tag
> counts, and the number of values within a tag respectively, since it
> might not be necessary to incur the extra overhead of all three.

You'd be making 2*2*2 = 8 version of the most basic structure, if I 
understand we're you're heading. You'd furthermore cause considerable 
complication for editing, as editing is mostly appending new blocks and 
updating pointers to the blocks and may change required bitdepths of those 
pointers as the file grows. I think our current accepted proposal is much 
cleaner and more carefull.

> The
> existing proposal is more of a clean break from TIFF

Some people keep saying that, but I totally dissagree. We broke absolutely 
nothing, except for one single thing (the bitdepth of file offsets), and we 
broke that one single thing in a totally consistent manner. TIFF minus the 
particular file offset bitdepth, is still 99.99% of TIFF.


Best regards,

Joris Van Damme
info@awaresystems.be
http://www.awaresystems.be/
Download your free TIFF tag viewer for windows here:
http://www.awaresystems.be/imaging/tiff/astifftagviewer.html