Creative Commons: Propagate, Respect, and Enforce
Over at FeedBurner we recently announced a service that lets you, the publisher of a feed, associate a Creative Commons license with your feed. Is this a big deal? It’s a HUGE deal! I'd like to take a look at how FeedBurner might propagate, respect, and enforce these licenses both now and in the future. In a subsequent post, I’d like to offer up a "Law of License Propagation" as it applies to syndication feeds.
First off, what's so interesting about Creative Commons? You can go to their excellent site to learn all about it, so I won't repeat everything here. But the "big" idea, at least from our perspective, is that they've formalized the notion of a license around creative works that is human-readable, lawyer-readable, and (most intriguingly) machine-readable. When you choose a license to associate with your creative works, you are specifying what the consumers of that work can "do" with it.
That brings us to what FeedBurner is currently doing with associating CC licenses with feeds. The Attach Creative Commons License service allows the publisher to select a license to "attach" to the items within their feed. We do this by adding an element to the feed that refers to a license URI: a unique identifier that resolves to a license (which is a collection of actions and characteristics). In RSS 1.0 feeds, we use the mod_cc namespace, while in RSS 2.0 and Atom feeds, we use the creativeCommons namespace.
Next, FeedBurner pledges to propagate this license information. What does that mean? That means that no matter what kinds of translations and services we apply to the feed, the license travels with it (this includes converting between feed formats and using the appropriate namespace). Where this becomes interesting is when we talk about feed splicing, or the combining of multiple feeds into a single resultant feed. We’ll make sure that the appropriate license is associated with the appropriate item, even if, for example, a license was specified on the feed (instead of an individual item).
So, what does it mean to "respect" a CC license? Well, FeedBurner may offer a number of different transformation services, including attaching some potentially revenue-generating content to feed items (see the Amazon Services Integration posting for an example of this). If we offer generalized feed splicing, for example, and the publisher is not the creator of one of those "input" feeds, FeedBurner is in a position to check to ensure that the license associated with a particular item permits commercial use. If commercial use is prohibited, then we can respect that license and not attach an ad or revenue-generating link to that item.
Finally, what about "enforce" – what does it mean to enforce a CC license. I think the best example of this might be the "Share Alike" characteristic that can be associated with a license. The definition of the "Share Alike" characteristic is: the licensor permits others to distribute derivative works only under a license identical to the one that governs the licensor's work. If FeedBurner creates a service that transforms or creates some derivative work from a feed item that is governed by this kind of license, we would enforce the Share Alike characteristic and ensure that the resultant item has an identical license.
I hope I've given a sense for how important and innovative this notion of associating, propagating, respecting, and enforcing Creative Commons licenses within feeds will be in the future. We're laying the groundwork for a number of exciting services – both from FeedBurner and from any number of feed conumsers!
