This package was debianized by James Treacy on Sun, 16 Dec 2002 14:37:59 -0500. Upstream Homepage: http://libofx.sourceforge.net/ Author: Benoit Grégoire. Copyright: 2002, 2004 by Benoit Grégoire 2005 by Ace Jones. 2001-2005 by Kasper Peeters. 2007 by Martin Preuss. 1989, 1991-2007 by Free Software Foundation. 1994 by X Consortium. 1997-1999 by Joey Hess. Licensed under the GNU General Public License. Debian GNU/Linux users may find this license in /usr/share/common-licenses/GPL. The file ofx201.dtd is Copyright 1997, 1998, 1999, 2001 by CheckFree Corp., Intiut Inc., and Microsoft Corp. The file ofx160.dtd is Copyright 1997, 1998, 1999 by CheckFree Corp., Intuit Inc., and Microsoft Corp. Both ofx201.dtd and ofx160.dtd are from the Open Financial Exchange standard (more recent versions are at www.ofx.net), and are distributed under the following terms: A royalty-free, worldwide, and perpetual license is hereby granted to any party to use the Open Financial Exchange Specification to make, use, and sell products and services that conform to this Specification. THIS OPEN FINANCIAL EXCHANGE SPECIFICATION IS MADE AVAILABLE "AS IS" WITHOUT WARRANTY OF ANY KIND. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT, INTUIT AND CHECKFREE ("PUBLISHERS") FURTHER DISCLAIM ALL WARRANTIES, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT, ALL OF WHICH ARE HEREBY DISCLAIMED. THE ENTIRE RISK ARISING OUT OF THE USE OF THIS SPECIFICATION REMAINS WITH RECIPIENT. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL THE PUBLISHERS OF THIS SPECIFICATION BE LIABLE FOR ANY CONSEQUENTIAL, INCIDENTAL, DIRECT, INDIRECT, SPECIAL, PUNITIVE, OR OTHER DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR OTHER PECUNIARY LOSS) ARISING OUT OF ANY USE TO WHICH THIS SPECIFICATION IS PUT, EVEN IF THE PUBLISHERS HEREOF HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Further clarification of these terms from the OFX Foundation says that the restriction which appears to only allow things which "conform to this Specification" means specifically that if an implementation claims to conform to OFX but does not then there is a problem, but otherwise there is none: As long as your software doesn't state that it uses OFX (i.e. doesn't mention what it uses), then all should be fine. The bottom line seems to be that it is fine if you use OFX technology as long as you do not represent your own enhanced version (added to or changed) as official "OFX". Your software need not implement the whole DTD. This thus permits the distribution of modifications (a key question), provided that there is no inaccurate claim made about OFX compliance.