ChristianHJW
26th April 2002, 11:39
robux4 set this link on the MCF dev mailing list and i thought i let you know :
http://www.kuro5hin.org/story/2002/4/25/212840/001
The guy may be right seen from one aspect, but Monty na dhis team need money to be able to go on with development, and i dont believe his ideas of how to do that are feasible :
I am not suggesting that Xiph.Org should not try to make money. However, there are other ways Xiph.Org could make money without creating a conflict of interest. Here are some ideas:
- Sell copies of the specification. This is the approach taken by standards bodies like IEEE, ANSI, and ISO/IEC.
- Dual-license the implementation(s). Commercial examples of this approach include Trolltech, Sleepycat Software, and Sendmail.
Offer a warranty of non-infringement with respect to patents. In a sense, this is like selling insurance.
- Sell support and/or developer subscriptions for the implementation(s). Examples include MSDN and ADC.
- Franchise the Vorbis brand to value-added partners. This is one source of revenue for MySQL AB.
- Perform certifications. This could be applied not only to independent implementations, but to any product which claims to support Vorbis regardless of the implementation. Some kind of certification mark might be useful, like the ones used by Dolby Digital/THX or Linux Journal.
- Offer consulting services. Unexciting, perhaps, but the experience and expertise of Xiph.Org could be worth more than they realize.
- License proprietary implementations after producing a specification. Xiph.Org has the advantage of being known for creating Vorbis, and a quality implementation from them could go a long way. Other examples in industry include Fraunhofer, Adobe, and RSA.
The Consulting services are probably only real alternative from all the listed points here, but i may be wrong.
Any other ideas or comments ?
http://www.kuro5hin.org/story/2002/4/25/212840/001
The guy may be right seen from one aspect, but Monty na dhis team need money to be able to go on with development, and i dont believe his ideas of how to do that are feasible :
I am not suggesting that Xiph.Org should not try to make money. However, there are other ways Xiph.Org could make money without creating a conflict of interest. Here are some ideas:
- Sell copies of the specification. This is the approach taken by standards bodies like IEEE, ANSI, and ISO/IEC.
- Dual-license the implementation(s). Commercial examples of this approach include Trolltech, Sleepycat Software, and Sendmail.
Offer a warranty of non-infringement with respect to patents. In a sense, this is like selling insurance.
- Sell support and/or developer subscriptions for the implementation(s). Examples include MSDN and ADC.
- Franchise the Vorbis brand to value-added partners. This is one source of revenue for MySQL AB.
- Perform certifications. This could be applied not only to independent implementations, but to any product which claims to support Vorbis regardless of the implementation. Some kind of certification mark might be useful, like the ones used by Dolby Digital/THX or Linux Journal.
- Offer consulting services. Unexciting, perhaps, but the experience and expertise of Xiph.Org could be worth more than they realize.
- License proprietary implementations after producing a specification. Xiph.Org has the advantage of being known for creating Vorbis, and a quality implementation from them could go a long way. Other examples in industry include Fraunhofer, Adobe, and RSA.
The Consulting services are probably only real alternative from all the listed points here, but i may be wrong.
Any other ideas or comments ?