Harry van der Wolf <[email protected]> writes: > 2016-11-01 23:23 GMT+01:00 David Taylor <[email protected]>: > >> Is there a license on the obf format its self? If I created my own obf >> reader what license would I be required to comply with?
> In the tools repo you can find this file: > https://github.com/osmandapp/OsmAnd-tools/blob/master/LICENSE > > The main osmand repo contains the license with all relevant sub licenses: > https://github.com/osmandapp/Osmand/blob/master/LICENSE > > So I would say GPLv3 Those are the licenses for the osmand software and osmand tools software. IANAL and TINLA... Generally copyright protects the expression of ideas fixed in a tangible medium, not ideas. So code definitely falls under copyright, and a document describing a file format would be copyrightable. But formats themselves are arguably ideas, not expressions, and I have not observed cases where formats themselves were copyrighted. For example, there are multiple reimplementations for FAT32 and similar filesystems, and generally I hear people worrying about patents, not copyright. So I don't see any obvious reason why you creating a library that parses/writes obf would be a derived work of any osmand code (assuming you don't actually copy any code and write it from scratch). And thus I don't see any obvious reason why you couldn't choose your own license. Note that I said that I don't see any obvious reason; I didn't tell you that it is definitely ok, and I didn't give you legal advice (because I'm not a lawyer and therefore certainly not your lawyer!). I would be surprised if anyone from osmand object to a BSD-licensed (or some such) obf library. But I am surprised from time to time... What license do you want to use? -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
