Commentary

Serdar Yegulalp
 

Radio New Zealand Goes Open With Ogg

Over at Groklaw.net, there's an interview with Richard Hulse of Radio New Zealand, talking about his decision to begin offering some of that station's Internet-based audio in the nonproprietary Ogg Vorbis format. It's a veritable case study in both the etiquette and ethics of adopting open standards.

Over at Groklaw.net, there's an interview with Richard Hulse of Radio New Zealand, talking about his decision to begin offering some of that station's Internet-based audio in the nonproprietary Ogg Vorbis format. It's a veritable case study in both the etiquette and ethics of adopting open standards.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Radio New Zealand used only WMA and MP3 for a long time, but started to adopt Ogg based on feedback provided by a small but growing segment of their population that couldn't play WMA at all (used to serve content-protected streams), and wanted to opt for Ogg over MP3 whenever possible. Hulse cites both reader feedback and a changing mix of clients -- different even from three years ago, he says -- as being two of the biggest reasons for adding Ogg to the format mix.

The ethics -- i.e., why use open standards? -- are the easy part, and have been rehashed endlessly both here and elsewhere. You don't have to pay licensing royalties; repurposing the code used for the standard is a lot easier; clients who can't use proprietary codecs are not locked out (something that Linux users have been discovering, with a great deal of dismay, when they try to access the media streams for the Democratic National Convention), et any number of well-documented ceteras.

What's really interesting to me is how the article also details some suggestions of etiquette vis-a-vis talking to a content provider and asking them to serve up nonproprietary formats. Many important points are made -- that the other party may not understand free-as-in-speech vs. free-as-in-beer; that your choice of words and tone is crucial, and that coming across as emotional or strident does more harm than good; and so on. In fact, the whole set of nine points -- it's at the end of the piece, right before the comments -- could serve nicely as a general set of guidelines for talking to folks about open standards and open source in general.

I'd like to see more of this sort of thing: etiquette guides for those who want to explain the benefits of open standards and open source to others, but also want to avoid scaring off their prospective audience. Too many of the explanatory efforts I've seen in the past, like the MakeTheMove campaign, quickly mire themselves in a welter of terminology (and, it has to be said, ideology). The last thing that's needed here is another excuse to be one's own worst enemy.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links