When Should File Formats Be Placed in the Public Domain?
wccwcc writes "A lot has been said about file formats and standards creating network effects and huge profits. That said, is there a time when file formats should enter the public domain, or is it ok for companies to sit on them forever. These are some ideas on when and how file formats should enter the public domain, just like trademarks do when they become "generic"."
I think it's helpful to make this distinction because the formats can easily be made public domain, whereas the codecs are usually subject to patents and/or require licensing.
File interchange becomes much simpler if you stop worrying about codecs, and concentrate on supporting formats - Linux tools for video could read & write the AVI format (just interleaved RIFF chunks) but either use a free codec, or none at all, without creating yet another video file standard.
MS Word is a different problem - although RTF is the preferred interchange format anyway. Certainly my partner (who occasionally works as a freelance proof-reader) uses RTF extensively with her clients instead of Word native format. The RTF v1.6 spec. is available in the MSDN, and includes sample reader & writer source code.
Jon.
The very idea of "forcibly placing" ones work into the "public domain by law" is quite distasteful.
Um, that's exactly what a patent is, and does. You document your method in detail for all to see, and in exchange, you can decide who uses the method for a limited amount of time. After the patent expires, potentially everyone benefits from your documentation freely.
[