Subj : XML To : Jasen Betts From : andrew clarke Date : Sun Jan 12 2003 12:43 am Mon 2003-01-06 16:09, Jasen Betts (3:640/1042) wrote to andrew clarke: ac>> You may as well make BinkP the minimum protocol. > yeah it seem most popular, what sort of software licence is involved? Here it is: ********************************************************************** FTSC FIDONET TECHNICAL STANDARDS COMMITTEE ********************************************************************** Publication: FSP-1011 Revision: 3 Title: Binkp - a protocol for transferring FidoNet mail over reliable connections Authors: Dima Maloff Nick Soveiko Maxim Masiutin Revision Date: 31 July 2000 Expiry Date: 31 July 2002 [...] 8. License ---------- You can implement binkp protocol in your software as long as you agree to the following conditions: 1. The protocol shall be referenced to as binkp and not in any other way. You shall include the author(s) of the protocol in your copyright statement for the software. 2. Binkp shall always be backwards compatible with it's previous versions. Binkp allows development of the new capabilities without compromising interoperability with previous versions. Therefore, it is important that future developments of the protocol are not pursued in different directions by different people. If you have any suggestions regarding future developments of the protocol, make a reasonable effort to contact the author(s), so that the development efforts can coordinated in a way advantageous for everybody. 3. If your implementation is not compatible with past, present or future binkp specifications, you shall reference to it as a "binkp variation" or "binkp derived". Remember that you may use, implement or utilize binkp, it's description or any other associated texts or documentations at your own risk, without any warranty, without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE Binkp author: Dima Maloff. --- Msged/NT 6.1.1 * Origin: Blizzard of Ozz, Mt Eliza, Victoria, Australia (3:633/267.1) .