Return-Path: <tiff-bounces@remotesensing.org>
Received: from inmx007.isp.belgacom.be (inmx007.isp.belgacom.be [195.238.3.89])
        by mailst034.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id i930kfoJ029185
        for <joris.at.lebbeke@skynet.be>; Sun, 3 Oct 2004 02:46:41 +0200
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from xserve.flids.com (adsl-065-083-169-202.sip.mco.bellsouth.net [65.83.169.202])
        by inmx007.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id i930kT0f013679
        for <joris.at.lebbeke@skynet.be>; Sun, 3 Oct 2004 02:46:31 +0200
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from adsl-065-083-169-202.sip.mco.bellsouth.net (localhost [127.0.0.1])
	by xserve.flids.com (Postfix) with ESMTP
	id DE44834A5DF; Sat,  2 Oct 2004 20:46:13 -0400 (EDT)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from psmtp.com (exprod6ob2.obsmtp.com [64.18.1.212])
	by xserve.flids.com (Postfix) with SMTP id 7AAFB34A5A5
	for <tiff@remotesensing.org>; Sat,  2 Oct 2004 20:46:10 -0400 (EDT)
Received: from source ([192.150.22.8]) by exprod6ob2.obsmtp.com ([64.18.5.12])
	with SMTP; Sat, 02 Oct 2004 17:46:07 PDT
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
	i930jxbA024417
	for <tiff@remotesensing.org>; Sat, 2 Oct 2004 17:46:04 -0700 (PDT)
Received: from calsj-dev (calsj-dev.corp.adobe.com [153.32.1.193])
	by inner-relay-3.corp.adobe.com (8.12.9/8.12.9) with ESMTP id
	i930jmks029903
	for <tiff@remotesensing.org>; Sat, 2 Oct 2004 17:45:58 -0700 (PDT)
Received: from [153.32.48.223] (noname.corp.adobe.com [153.32.48.223])
	by mailsj-v1.corp.adobe.com
	(iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003))
	with ESMTP id <0I4Z007L4GSCE3@mailsj-v1.corp.adobe.com> for
	tiff@remotesensing.org; Sat, 02 Oct 2004 17:45:48 -0700 (PDT)
Date: Sat, 02 Oct 2004 17:39:10 -0700
From: Chris Cox <ccox@adobe.com>
Subject: Re: [Tiff] Re: BigTIFF extension issue
In-reply-to: <033601c4a86a$8a32a0b0$0200a8c0@PLATO>
X-Sender: ccox@mailsj.corp.adobe.com
To: tiff@remotesensing.org
Message-id: <p05210601bd84fa7e16f3@[153.32.48.223]>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
References: <4.3.2.7.2.20041001123059.016e72d0@mailsrv1>
	<415D8B80.5000300@pobox.com> <p06110403bd833f3c7cf9@[153.32.220.138]>
	<001d01c4a7de$cf92f6f0$e8c8c950@dfgrrxsknr4e>
	<6.0.0.22.1.20041001135607.0263e220@pop.earthlink.net>
	<p05210607bd837ef12142@[153.32.48.223]>
	<005401c4a81e$228281c0$e8c8c950@dfgrrxsknr4e>
	<p05210602bd83d1d28e3b@[153.32.48.223]>
	<002801c4a835$d37a57c0$e8c8c950@dfgrrxsknr4e>
	<p05210601bd83e499f4b8@[153.32.48.223]>
	<033601c4a86a$8a32a0b0$0200a8c0@PLATO>
X-BeenThere: tiff@remotesensing.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: TIFF and libtiff discussion  <tiff.remotesensing.org>
List-Unsubscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=unsubscribe>
List-Archive: <http://xserve.flids.com/pipermail/tiff>
List-Post: <mailto:tiff@remotesensing.org>
List-Help: <mailto:tiff-request@remotesensing.org?subject=help>
List-Subscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=subscribe>
Sender: tiff-bounces@remotesensing.org
Errors-To: tiff-bounces@remotesensing.org
X-UIDL: 60bac9ff3f535a4db0403c058985893b

At 11:28 AM +0100 10/2/04, Andy Cave wrote:
>Companies/products/people just don't do that. They put a version 
>number inside the file that distinguishes it. And that surely is 
>what we are doing (or should be doing) for BigTIFF, even if it's 
>indirectly so. It's still TIFF.

No, they DO (have done, will keep doing) that.
When the change is big enough, you sometimes have to give it a new name.

Chris



>Andy.
>
>----- Original Message ----- From: "Chris Cox" <ccox@adobe.com>
>To: <tiff@remotesensing.org>
>Sent: Saturday, October 02, 2004 5:53 AM
>Subject: Re: [Tiff] Re: BigTIFF extension issue
>
>>At 6:10 AM +0200 10/2/04, Joris wrote:
>>>  > But end users are only consistent in one way: they just want it to work.
>>>
>>>So this then implies that you have to go and change the file 
>>>extension for every
>>>next version of the format that is not backwards compatible?
>>
>>No, just major changes.
>>
>>Chris
>>_______________________________________________
>>Tiff mailing list
>>Tiff@remotesensing.org
>>http://xserve.flids.com/mailman/listinfo/tiff

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