Please note: We are in the final stages of migrating the CC Wiki. No edits can be made. We will soon open CC Wiki to edits by users with a CCID -- get yours now!
File Type Information
Supports embedding license URL: supports_license_url::True
Supports embedding web statement: supports_web_statement::True
Supports embedding more permissions: supports_more_permissions::True
Metadata Location: [[Metadata location::{{{metadata_location}}}]] | (unknown) }}
Metadata Format: [[Metadata format::{{{metadata_format}}}]] | (unknown) }}



RSS 2.0 is a syndication (feed) format. A module has been published specifying how to include Creative Commons license information.

The module namespace URI was changed from http://backend.userland.com/creativeCommonsRssModule to http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html in 2003; consumers should be aware of this change.

Examples

Specifying a License

The specification defines a namespace,

   xmlns:creativeCommons="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html"

which can be used to define a license for the feed or individual entry. An example of an RSS 2.0 file with license metadata is available at http://static.userland.com/gems/backend/rssCreativeCommonsExample.xml.

Additional Metadata

A web statement provides additional confidence regarding metadata assertions. morePermissions allows content creators to provide a link to a URL where additional permissions, beyond those provided by the license, may be secured.

The RSS 2.0 specification provides a mechanism for extension; new elements must be in a namespace. Creative Commons recommends using the following two namespace declarations for inclusion of web statement and more permissions metadata:

 <rss version="2.0" 
    xmlns:creativeCommons="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html"
    xmlns:cc="http://creativecommons.org/ns#"
    xmlns:xapRights="http://ns.adobe.com/xap/1.0/rights/"
 >
 ...

The following example demonstrates providing a verification URL (web statement) as well as a URL where users may find information regarding additional permissions.

<item>
  <description>...</description>
  <pubDate>Mon, 16 Dec 2002 12:21:08 GMT</pubDate>
  <guid>http://scriptingnews.userland.com/backissues/2002/12/16#When:4:21:08AM</guid>
  <creativeCommons:license>http://www.creativecommons.org/licenses/by-nc/1.0</creativeCommons:license>

  <cc:morePermissions>http://example.org/pay_me</cc:morePermissions>
  <xapRights:WebStatement>http://example.org/more_info</xap:Rights>
</item>