Return-Path: <tiff-bounces@remotesensing.org>
Received: from inmx006.isp.belgacom.be (inmx006.isp.belgacom.be [195.238.2.106])
        by mailst034.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id i94EKNWe013861
        for <joris.at.lebbeke@skynet.be>; Mon, 4 Oct 2004 16:20:23 +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 inmx006.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id i94EK7c9017896
        for <joris.at.lebbeke@skynet.be>; Mon, 4 Oct 2004 16:20:08 +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 9C5BF3511E6; Mon,  4 Oct 2004 10:19:51 -0400 (EDT)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from outmx016.isp.belgacom.be (outmx016.isp.belgacom.be
	[195.238.2.115])
	by xserve.flids.com (Postfix) with ESMTP id 53BD53511C0
	for <tiff@remotesensing.org>; Mon,  4 Oct 2004 10:19:49 -0400 (EDT)
Received: from outmx016.isp.belgacom.be (localhost [127.0.0.1])
	by outmx016.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with
	ESMTP id i94EJbam013934
	for <tiff@remotesensing.org>; Mon, 4 Oct 2004 16:19:39 +0200
	(envelope-from <joris.at.lebbeke@skynet.be>)
Received: from dfgrrxsknr4e (184-89.240.81.adsl.skynet.be [81.240.89.184])
	by outmx016.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with SMTP
	id i94EJSnE013863; Mon, 4 Oct 2004 16:19:29 +0200
	(envelope-from <joris.at.lebbeke@skynet.be>)
Message-ID: <000e01c4aa1d$77db22c0$b859f051@dfgrrxsknr4e>
From: "Joris" <joris.at.lebbeke@skynet.be>
To: "Bob Friesenhahn" <bfriesen@simple.dallas.tx.us>,
        "Andy Cave" <andy.cave@hamillroad.com>
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><p05210601bd84fa7e16f3@[153.32.48.223]><010701c4a9ed$048f25d0$0200a8c0@PLATO>
	<Pine.SOC.4.60.0410040900030.2727@blade.simplesystems.org>
Subject: Re: [Tiff] Re: BigTIFF extension issue
Date: Mon, 4 Oct 2004 16:21:31 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Cc: Tiff mailing list <tiff@remotesensing.org>
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: e12f46f39faf95c9b3a18d482985defb

> > I'm curious - can you name some examples please. I'd be interested in
> > hearing
> > about some and seeing exactly what the differences are/were between
> > 'changes'.
>
> The BMP format is an example of a format which has been extended
> without breaking a lot of existing software.  Recently BMP v3 was
> introduced.  This was possible because the additions were made in a
> portion of the file header which can be skipped based on an offset
> value which appears early in the header.  Properly written old readers
> should automatically skip the new stuff (in practice some readers were
> broken).

A very fine example... on how the extension remained unchanged, because it was
still regarded the same file format. A very fine example, too, on how even much
more drastic changes to the format's specification, still do not suffice to
regard the new version as a different format.

I believe the point of view you defend is that the extension should be changed.

If you go back, you'll see that Andy was responding to Chris saying companies do
sometimes change extension when brewing a next version of a format. Thus, he was
asking for examples that involved changing the extension. Possibly, but not
certainly, and I'm not quoting him on this but going a long way interpreting, he
was trying to make the point that most of the proper examples that could be
given involve a single company.


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

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