Received: from inav033.isp.belgacom.be (localhost.localdomain [127.0.0.1])
	by inav033.isp.belgacom.be (Postfix) with ESMTP id D1506BEE63
	for <joris.at.lebbeke@skynet.be>; Fri, 24 Nov 2006 23:03:16 +0100 (CET)
Received: from inas009.isp.belgacom.be (inas009.isp.belgacom.be [195.238.4.7])
	by inav033.isp.belgacom.be (Postfix) with ESMTP id C41CEBEE5E
	for <joris.at.lebbeke@skynet.be>; Fri, 24 Nov 2006 23:03:16 +0100 (CET)
Received: from inmx013.isp.belgacom.be (inmx013.isp.belgacom.be [195.238.4.216])
        by inas009.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-AS-2.03) with ESMTP id kAOM36X2009034
        for <joris.at.lebbeke@skynet.be>; Fri, 24 Nov 2006 23:03:07 +0100
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (r153.dmsolutions.ca [209.217.116.153] (may be forged))
        by inmx013.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-2.32) with ESMTP id kAOM31XD020202
        for <joris.at.lebbeke@skynet.be>; Fri, 24 Nov 2006 23:03:02 +0100
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (duke.maptools.org [127.0.0.1])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id kAOLtCXA016772;
	Fri, 24 Nov 2006 16:55:52 -0500
Received: from omta04ps.mx.bigpond.com (omta04ps.mx.bigpond.com
	[144.140.83.156])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id kAOLt714016767
	for <tiff@lists.maptools.org>; Fri, 24 Nov 2006 16:55:09 -0500
Received: from oaamta04ps.mx.bigpond.com ([61.9.204.42])
	by omta04ps.mx.bigpond.com with ESMTP id
	<20061124215440.LQOR295.omta04ps.mx.bigpond.com@oaamta04ps.mx.bigpond.com>;
	Fri, 24 Nov 2006 21:54:40 +0000
Received: from saxicola.cuneata.net ([61.9.204.42])
	by oaamta04ps.mx.bigpond.com with ESMTP id
	<20061124215434.VSLF20265.oaamta04ps.mx.bigpond.com@saxicola.cuneata.net>;
	Fri, 24 Nov 2006 21:54:34 +0000
From: Brad Hards <bradh@frogmouth.net>
To: tiff@lists.maptools.org
Subject: Re: [Tiff] Windows HD Photo - any interest?
Date: Sat, 25 Nov 2006 08:53:20 +1100
User-Agent: KMail/1.9.1
References: <200611242123.29432.bradh@frogmouth.net>
	<20061124160254.GB28777@ak4719.spb.edu>
In-Reply-To: <20061124160254.GB28777@ak4719.spb.edu>
MIME-Version: 1.0
Message-Id: <200611250853.25499.bradh@frogmouth.net>
Cc: 
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0234876701=="
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org
X-UIDL: 000000000023ceae.00001da3
X-MSP-STORE: Fri, 24 Nov 2006 23:03:17 +0100
Status:   

--===============0234876701==
Content-Type: multipart/signed; boundary="nextPart13261964.zL3laQQO1W";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart13261964.zL3laQQO1W
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Saturday 25 November 2006 03:02, Andrey Kiselev wrote:
> But the codec implementation supplied with this Kit is effectively
> non-free. It is not compatible neither with libtiff license terms nor
> with other popular free software licenses. I hope that it is possible to
> use documentation to do  independent implementation:
I would also like to see an independent implementation (and I think there=20
might be enough information to do one given the Bitstream specification in=
=20
the DPK), however I'm not sure why you think the current codec is=20
incompatible with the libtiff license terms. Certainly I would agree it mig=
ht=20
not be compatible with the GPL, but my reading of the libtiff license says=
=20
that as long as the codec is generally released (i.e. no licensing fees) th=
en=20
it could be incorporated into libtiff.

This is not to say I am sure - I think it is ambiguous.

> "1. You may review these Materials only (a) as a reference to assist You
> in planning and designing Your product, service or technology
> ("Product") to interface with a Microsoft product, specification,
> service or technology ("Microsoft Product") as described in these
> Materials; and (b) to provide feedback on these Materials to Microsoft.
> All other rights are retained by Microsoft; this Agreement does not give
> You rights under any Microsoft patents."
I don't think that any of this says that the codec couldn't be used in=20
libtiff. Probably worth a clarification though.

> Though, the patent issue remains.
Certainly this is a bigger issue. I'm always a bit concerned about this kin=
d=20
of stuff from Microsoft.

> Anyway, it is out of scope for libtiff at the moment.
I don't understand this part either. If you consider HD Photo to just be a=
=20
different version of TIFF, how does it differ from BigTIFF? [This really is=
 a=20
question, not an argument to say that it should be in scope - I'm just tryi=
ng=20
to understand your thinking].

Brad

--nextPart13261964.zL3laQQO1W
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBFZ2nVGwwszQ/PZzgRAnTBAJ9nZEf5H9Nlob25P5RK/nGa8pFx0wCcDGvJ
a0j5kvifWkaMB8nPJTEwO6s=
=Na0p
-----END PGP SIGNATURE-----

--nextPart13261964.zL3laQQO1W--

--===============0234876701==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
--===============0234876701==--
