Ken Varnum

Did you know you that it's easy to add a creative commons license to your RSS and Atom feeds -- not just to your blog's web site? Here are brief instructions for adding your Creative Commons license to RSS and Atom feeds:

RSS 2.0

You need to make two small edits to the RSS 2.0 template your blog software uses.

1. Change the line that reads <rss version = "2.0"> to <rss version="2.0" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule">. This is probably the second line in the RSS file. The addition of the "xmlns..." bit sets up the second item you'll edit, pointing to the web page that defines an extension to the standard RSS 2.0 field set.
2. Then add the URL to the Creative Commons license you've selected at the Creative Commons web site. This bit goes anywhere between the <channel> and the </channel> tags. For example, RSS4Lib has an "attribution non-commercial" license, version 3.0. So I've added this code to my RSS feed: <creativeCommons:license>http://creativecommons.org/licenses/by-nc/3.0/us/</creativeCommons:license>

Atom

It is even easier to add a Creative Commons license to an Atom feed. There's just one line to add to the Atom template. For RSS4Lib, this is: <link rel="license" type="application/rdf+xml" href="http://creativecommons.org/licenses/by-nc/3.0/us/rdf" />. Again, this assumes you've picked an "attribution non-commercial" license. Whatever the Creative Commons license URL, add "rdf" to the end. And that's it.

So What?

I suppose that putting the license on the web site alone is enough, from a strict legal standpoint. However, as we all know, RSS feeds have a habit of wandering off almost on their own power. Adding the license to the feeds themselves gives you an extra bit of protection -- the consumer of the feed cannot say they were unaware the content was licensed.

Copyright and RSS frequently appear to be ill-suited bedfellows. On one side we have the author's desire to have one's content distributed as widely as possible. On the other, we have the publisher's desire to control the way one's content is used -- out of the concern for losing control over one's work, perceived or real financial loss, or simple desire to be properly attributed. Where in traditional media, publisher and author are usually different (and the most common place those two roles intersected was the vanity press), in "new media," the same person frequently takes on both roles. Copyright is often seen as complicated, and for good reason. In the United States, anyway, a work is copyrighted at the moment it is created and may not be reproduced with explicit permission. (The legal concept of "Fair use," in the United States, is at best murky. It's a right that does not readily extend to other legal domains. And, it almost certainly does not apply to the wholesale reproduction of items from an RSS feed. But I'm no lawyer.) At the other extreme, the author can explicitly waive copyright -- a choice that few authors or publishers would opt for. In the middle ground is licensing the use of content for various uses. This is the sensible middle ground, for most bloggers: some uses of my content are fine while others are not. However, the challenge arises in setting the language of that license and defining the kinds of use to allow. Doing so in a legally defensible way is complicated (again, I'm no lawyer). So what should the blogger to do? Use Creative Commons. Creative Commons (CC) is a non-profit foundation that has written legally valid and clearly understandable licenses that anyone may use. By applying one of CC's licenses to blog content, the blogger can state clearly what uses of that content are allowed. Can it be reused wholesale? Reused only if the person using it does not make any money from it? Reused only if attribution is given and no changes are made to the original? There are many permutations. (Unfortunately, there's no standard way to license content in an RSS feed.) RSS4Lib is now licensed under an Attribution-Noncommercial 3.0 United States license. (Look toward the bottom of the sidebar.) If you want to learn more about using content -- including RSS4Lib -- that has a Creative Commons license, I highly recommend CC HowTo #1: How to Attribute a Creative Commons licensed work at my colleague Molly Kleinman's blog. The first in her planned series of posts is excellent, and I look forward to future installments.

In the category of being so obvious it's a wonder it took this long for someone to do it (with a subcategory of "D'oh! I wish I'd done it first") is Mloovi. Mloovi takes a web page or an RSS feed, runs it through Google's translation tool, and gives you a permalink for the translated output. Mloovi also gets my vote for best Web 2.0 site subtitle: "beta (if it ain't beta it ain't web 2.0)". I think I'll adopt that as my personal motto. So, if you've been dying to read RSS4Lib in French, Russian, Arabic, or Hindi, here's your opportunity. (Mloovi offers translations between any pair of these languages: Arabic, Bulgarian, Chinese (both Simplified and Traditional), Croatian, Czech, Danish, Dutch, English, Finnish, French, German, Greek, Hindi, Italian, Japanese, Korean, Norwegian, Polish, Portuguese, Romanian, Russian, Spanish, and Swedish. This tool will be very handy for me to keep up with the biblioblogging world that doesn't happen to write in a language that I can read. I can also see it useful as a way to get publishers' notifications, etc., where they are offered via RSS but inconveniently not in the language that the bibliographer speaks. Having permanent URLs for the translation, whether for a web page or a feed, is exceptionally handy. The feeds, I should note, have advertisements added as new items, noted with "ADVERT" as a prefix. Mloovi also offers an iframe widget code; however, it only allows a single translation, not a choice for your users -- unless you want to clutter up your interface with lots of buttons. Here, as an example, is the English-to-German translation of RSS4Lib's feed: Oh, and a note about the name: "mloovi" (actually, "mlooví," with a long "í" -- something impossible to render in a domain name) is the Czech 3rd person singular -- he, she, or it speaks. Addendum (12 August 08): Mike from mloovi.com pointed out in the comments that multiple languages can be selected in the widget -- for example:

It was just a matter of time, but Bloglines has added advertisements to their site. When I went to read my feeds this morning, there was an ad for T-Mobile right on the starting page: I've long wondered just where Bloglines was getting revenue to support itself -- it didn't make sense to me that IAC Search & Media, its owner, was keeping Bloglines running to make my blogreading life easier. So far, I haven't noticed advertisements on individual post or folder pages. Could those be far behind? Interestingly, the advertisement I was shown was managed by.... DoubleClick. Which Google acquired in March 2008. Now, it seems, whether you use Google Reader or Bloglines, you're putting advertising dollars into the Big G's pocket.

Not too long ago, I read a fascinating book about international shipping. No, I'm serious: Marc Levinson's The Box: How the Shipping Container Made the World Smaller and the World Economy Bigger, published in 2006 (which happens to have been the 50th anniversary of that ubiquitous part of the global economy, the shipping container).

In a nutshell, the standardized shipping container revolutionized international trade by vastly speeding up the loading and unloading of ships. The cargo that had been brought to the wharf, unloaded from a truck into a pile on the dock, moved piece by piece into cargo netting to be hoisted by crane into the hold of a ship, so that it could be removed the cargo net and then shoved in the corner of a hold, was now as complicated as building a stack of bricks. OK, a bit more complicated, since loading and unloading containers is really an art, the ship needs to be properly balanced, and so forth -- but basically, a crane operator and few others can load a ship. Turnaround times at pier -- when large, expensive, freighters were just sitting there -- were reduced dramatically.

What does this have to do with RSS? Quite a bit, actually. RSS is the box into which any old thing can be packed, for uniform shipping from producer to consumer. A paragraph of text, an audio podcast, a video podcast, a Word document... If you can be put it online, you can shove it a container (the RSS item), give it a bill of lading (the RSS channel), pre-clear it for customs (tags, authors, keywords, etc.), and send it on its merry way on a conveyance (the RSS feed). Nobody has to touch the contents between shipper and receiver -- just once to pack it, once to unpack it.

The feed is empty.... Fill it!

Addendum (10AM 5 August 08): Another similarity pointed out to me (thanks Cindi) is that RSS and shipping containers both lack security and authentication. The ramifications of this problem are a bit more serious for shipping containers than for feeds. Still, not really knowing who might have mucked with a feed between origin and destination, or having any real knowledge of who published it in the first place once the feed items are scattered around the Internet, can be a problem. Feeds, once set free, can have a life of their own.