Hi I'm trying push for companies and government institutions to start using Vorbis as an alternative to MP3 and to some extend AAC so they as a benefit can ignore rigid license schemes and expensive royalty payments. In principle it ought to be a downhill job, but it has turned out to be a lot more difficult than expected. The biggest obstacle for government institutions and to some extend for private companies is in their eyes the lack of a standard. Now you may say that we have the source and some documentation so why do we need Vorbis to be a standard. Well, to answer this you have to understand that these people are not like you and me. These peopele are unable to accept anything that doesn't have the word STANDARD rubberstamped all over. I have even some across Cisco folks saying they can't be allowed to use Vorbis because it is not a standard (and becuase it is proprietary). In my view, we need to get Vorbis standardized somehow to get it more widely used. The question is, how do we do this. We could submit for Vorbis to become a standard under IEEE or ISO, but I don't know how to do it and these orgs are usually slow, expensive and not what we want. A more likely approach would be to push for a RFC under IETF, but writing the document and get it approved would be hard work. To make it worse, probably the only ones with sufficient knowledge to write the RFC are the one writing the code. Anyway, have anyone else experienced the problem ? And what does the Xiph people have to say about it ? --PMM ----------------------------------------------------------- Peter Maersk-Moller ----------------------------------------------------------- Ogg/Vorbis support for MPEG4IP and YUV12, XviD, AVI and MP4 for libmpeg2. See http://www.maersk-moller.net/projects/ ----------------------------------------------------------- --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
--- Peter Maersk-Moller <peter@maersk-moller.net> wrote:> A more likely approach would be to push for a RFC under IETF, > but writing the document and get it approved would be hard work.<p><p>Silvia.Pfeiffer@ csiro.au has taken up the task (at least for Ogg, I think, I didn't look for Vorbis specifics, hm), and several draft revisions have been circling various Xiph.org developer lists for quite awhile now. Check the archives; we've missed the most recent meeting, but the next goal is approaching fairly soon. This shouldn't be a major concern right this second, things are bein' worked out as far as I've skimmed over topics. ~HJ __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus – Powerful. Affordable. Sign up now. http://mailplus.yahoo.com --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> In my view, we need to get Vorbis standardized somehow > to get it more widely used.Your typical ITU, ISO and ECMA standards are defined by the Industry and both private and public research institutions. Vorbis doesn't have a good lobby there. ;( Is Xiph.org member of any standardization bodies? Maybe they should try to become a member in above institutions -- if it is affordable and does not conflict with the Xiph Foundation's interests. Does anyone know about rock solid industry standards that emerged from GNU/FSF and Open Source projects (independent from any specific source code license)? If so, what standardization bodies besides the IETF have set these standards? Christian <p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
On Thu, 21 Nov 2002, Peter Maersk-Moller wrote:> A more likely approach would be to push for a RFC under IETF, > but writing the document and get it approved would be hard work. > To make it worse, probably the only ones with sufficient > knowledge to write the RFC are the one writing the code.Wella. We have RFC drafts for the Ogg encapsulation formats coming up as you see (thanks to excellent work by Silvia), and stand a good chance to have them passed at the next IETF meeting. Agreed that this is not a vorbis RFC, but your company executives, are they also competent enough to know the difference between the carrier format and the content format? My guess is that this document satisfies 9 out of 10 executives' standard compliance policies. :-) Linus --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.