2004.04.15 00:26 "[Tiff] Large TIFF files", by Lynn Quam

2004.04.26 14:32 "Re: [Tiff] Large TIFF files", by Bob Friesenhahn

In that case we need a volunteer to record, categorize, and summarize ideas and issues voiced on the list so that they can be prioritized and decisions made.

Rereading other threads on this topic, my conclusion is that we do not need a volunteer to turn all of our blabla into categorized blabla, but need a hands-on man to make final descisions and turn 'em into code.

I disagree. We need both an editor to maintain a specification, and we need two (or more) independent development projects to prove the concept and verify the specification (similar to the way the IETF does things). It is not necessary for all verification projects to be open-source. It is only necessary that they interoperate.

Without a validated specification, there is no official format and the only library/program that is sure to support the format is whatever code was used to develop it.

Without a specification, there will be no standard and the result will just be a libtiff-specific hack.

If TIFF64 uses your simple approach, then the specification can be just a few pages since it can describe the difference from baseline TIFF. If it fixes other TIFF flaws, then the specification will be more involved.

Bob

======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us
http://www.simplesystems.org/users/bfriesen