Return-Path: <tiff-admin@remotesensing.org>
Received: from inmx009.isp.belgacom.be (inmx009.isp.belgacom.be [195.238.3.146])
        by mailst006.isp.belgacom.be (8.12.9/8.12.9/Skynet-MAILSTORE-2.14) with ESMTP id i3QEaBPK001997
        for <joris.at.lebbeke@skynet.be>; Mon, 26 Apr 2004 16:36:11 +0200
        (envelope-from <tiff-admin@remotesensing.org>)
Received: from yoda.imagelinks.com ([208.24.120.44])
        by inmx009.isp.belgacom.be (8.12.9/8.12.9/Skynet-IN-2.32) with ESMTP id i3QEZvgX018006
        for <joris.at.lebbeke@skynet.be>; Mon, 26 Apr 2004 16:35:58 +0200
        (envelope-from <tiff-admin@remotesensing.org>)
Received: from yoda.imagelinks.com (localhost.localdomain [127.0.0.1])
	by yoda.imagelinks.com (8.11.6/8.11.6) with ESMTP id i3QEXTn29847;
	Mon, 26 Apr 2004 10:33:30 -0400
Received: from fuzzylog.simplesystems.org (fuzzylog.simplesystems.org [65.66.246.65])
	by yoda.imagelinks.com (8.11.6/8.11.6) with ESMTP id i3QEWcn29805
	for <tiff@remotesensing.org>; Mon, 26 Apr 2004 10:32:39 -0400
Received: from scooby.simplesystems.org (scooby.simplesystems.org [65.66.246.67])
	by fuzzylog.simplesystems.org (8.9.3/8.9.3) with ESMTP id JAA19444;
	Mon, 26 Apr 2004 09:32:13 -0500 (CDT)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@scooby.simplesystems.org
To: Joris <joris.at.lebbeke@skynet.be>
cc: Chris Cox <ccox@adobe.com>, Tiff mailing list <tiff@remotesensing.org>
Subject: Re: [Tiff] Large TIFF files
In-Reply-To: <002b01c42b75$bb68c4b0$e1b588d9@dfgrrxsknr4e>
Message-ID: <Pine.GSO.4.44.0404260921200.11901-100000@scooby.simplesystems.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: tiff-admin@remotesensing.org
Errors-To: tiff-admin@remotesensing.org
X-BeenThere: tiff@remotesensing.org
X-Mailman-Version: 2.0.13
Precedence: bulk
List-Help: <mailto:tiff-request@remotesensing.org?subject=help>
List-Post: <mailto:tiff@remotesensing.org>
List-Subscribe: <http://remotesensing.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=subscribe>
List-Id: TIFF and libtiff discussion <tiff.remotesensing.org>
List-Unsubscribe: <http://remotesensing.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=unsubscribe>
List-Archive: <http://remotesensing.org/pipermail/tiff/>
Date: Mon, 26 Apr 2004 09:32:14 -0500 (CDT)
X-UIDL: 93ea0d6f20ddc89541e7109b5dfe5ac4

On Mon, 26 Apr 2004, Joris wrote:

> Bob wrote:
> > 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

_______________________________________________
Tiff mailing list
Tiff@remotesensing.org
http://remotesensing.org/mailman/listinfo/tiff
