Return-Path: <tiff-admin@remotesensing.org>
Received: from inmx008.isp.belgacom.be (inmx008.isp.belgacom.be [195.238.3.88])
        by mailst006.isp.belgacom.be (8.12.9/8.12.9/Skynet-MAILSTORE-2.14) with ESMTP id i51Fno0U009703
        for <joris.at.lebbeke@skynet.be>; Tue, 1 Jun 2004 17:49:50 +0200
        (envelope-from <tiff-admin@remotesensing.org>)
Received: from yoda.imagelinks.com ([208.24.120.44])
        by inmx008.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id i51Fneji008609
        for <joris.at.lebbeke@skynet.be>; Tue, 1 Jun 2004 17:49:41 +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 i51Fm4q05344;
	Tue, 1 Jun 2004 11:48:04 -0400
Received: from smtp-relay-8.adobe.com (smtp-relay-8.adobe.com [192.150.22.8])
	by yoda.imagelinks.com (8.11.6/8.11.6) with ESMTP id i51Fktq05318
	for <tiff@remotesensing.org>; Tue, 1 Jun 2004 11:46:55 -0400
Received: from inner-relay-3.corp.adobe.com (inner-relay-3 [153.32.251.51])
	by smtp-relay-8.adobe.com (8.12.10/8.12.10) with ESMTP id i51FkF6P023488;
	Tue, 1 Jun 2004 08:46:20 -0700 (PDT)
Received: from seaclus2 (seaclus2.sea.adobe.com [153.32.250.104])
	by inner-relay-3.corp.adobe.com (8.12.9/8.12.9) with ESMTP id i51Fk4kq014029;
	Tue, 1 Jun 2004 08:46:04 -0700 (PDT)
Received: from [153.32.220.138] (foobird.sea.adobe.com [153.32.220.138])
 by mailsea.sea.adobe.com
 (iPlanet Messaging Server 5.2 HotFix 1.18 (built Jul 28 2003))
 with ESMTP id <0HYM00DBWZSLFJ@mailsea.sea.adobe.com>; Tue,
 01 Jun 2004 08:45:57 -0700 (PDT)
From: Steve Carlsen <scarlsen@adobe.com>
Subject: Re: [Tiff] large TIFF - two alternatives
In-reply-to: <40BC6D8D.8070302@informatix.co.uk>
X-Sender: scarlsen@mailsea.sea.adobe.com
To: John Aldridge <john.aldridge@informatix.co.uk>, tiff@remotesensing.org
Cc: cjb@adobe.com
Message-id: <a06020403bce25327ea66@[153.32.220.138]>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
References: <p06020407bcdaeefbd542@[153.32.220.138]>
 <40B5C665.2020807@informatix.co.uk> <40BC6D8D.8070302@informatix.co.uk>
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: Tue, 01 Jun 2004 08:46:01 -0700
X-UIDL: 3a47eaa5fbc6a318f665f824c1f3247b

At 12:50 +0100 6/1/04, John Aldridge wrote:
>This
>
>[Tiff can handle <data-format-of-choice-for-my-application>.]
>
>is both a strength /and/ a weakness. The fact that Tiff has so many different ways of storing data is handy for the writer, but a real pain for the reader. Maybe PNG isn't flexible enough, but Tiff is so flexible that supporting the full spec is a lot of work.

This is true. Which I why I think that New TIFF should be more restrictive in some ways -- at a minimum, a single Endian scheme. Other restrictions could either be global, or perhaps split into several flavors of TIFF files, perhaps broken out by support of varius compression schemes. And perhaps with different extensions, e.g., .tfb for a Basic New TIFF, with of course 8 byte offsets but that supports only 2 compression schemes (uncompressed and ?), or some such thing.

But I don't mind keeping TIFF quite general, either. I'm only spelling out some alternatives.

Regards
SteveC


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