Difference between revisions of "RSS 1.0"

From Creative Commons
Jump to: navigation, search
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{incomplete}}
 
 
{{Filetype|
 
{{Filetype|
 
   license_url=True|
 
   license_url=True|
Line 47: Line 46:
  
 
== Additional Metadata ==
 
== Additional Metadata ==
 
{{incomplete}}
 
 
'''Note that this is a draft we are currently working on; this notice will be removed after collecting feedback.'''
 
  
 
A [[WebStatement|web statement]] provides additional confidence regarding metadata assertions.  [[MorePermissions|morePermissions]] allows content creators to provide a link to a URL where additional permissions, beyond those provided by the license, may be secured.   
 
A [[WebStatement|web statement]] provides additional confidence regarding metadata assertions.  [[MorePermissions|morePermissions]] allows content creators to provide a link to a URL where additional permissions, beyond those provided by the license, may be secured.   

Latest revision as of 19:26, 10 October 2007

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 1.0 is a syndication (feed) format. The specification was published December 6, 2000. A module specification has been published for inclusion of licensing information in the feed.

Specifying a License

RSS 1.0 is encoded as RDF/XML. A license may applied to a channel, entry or image by adding an appropriate triple. The predicate should be http://creativecommons.org/ns#license. Older deployments may exist which use http://web.resource.org/cc/ as the root of the Creative Commons namespace.

The following example shows licensing at both the channel and entry levels.


<?xml version="1.0" encoding="utf-8"?> 

<rdf:RDF 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
  xmlns:cc="http://creativecommons.org/ns#"
  xmlns="http://purl.org/rss/1.0/"
> 

  <channel rdf:about="http://meerkat.oreillynet.com/?_fl=rss1.0">
    <title>Meerkat</title>
    <link>http://meerkat.oreillynet.com</link>
    <description>Meerkat: An Open Wire Service</description>
    <cc:license rdf:resource="http://www.creativecommons.org/licenses/example1" />

    <items>
      <rdf:Seq>
        <rdf:li resource="http://c.moreover.com/click/here.pl?r123" />
      </rdf:Seq>
    </items>

  </channel>

  <item rdf:about="http://c.moreover.com/click/here.pl?r123">
    <title>XML: A Disruptive Technology</title> 
    <link>http://c.moreover.com/click/here.pl?r123</link>
    <cc:license rdf:resource="http://www.creativecommons.org/licenses/example2" />
  </item> 
</rdf:RDF>

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.

RSS 1.0 is RDF+XML, which allows additional metadata to be specified for individual objects.

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


  <item rdf:about="http://c.moreover.com/click/here.pl?r123">
    <title>XML: A Disruptive Technology</title> 
    <link>http://c.moreover.com/click/here.pl?r123</link>
    <cc:license rdf:resource="http://www.creativecommons.org/licenses/example2" />

    <cc:morePermissions rdf:resource="http://example.org/pay_me" />
    <xapRights:WebStatement rdf:resource="http://example.org/more_info" />

  </item> 

Note that this example uses an additional namespace, xapRights, which is defined as http://ns.adobe.com/xap/1.0/rights/.

Use with Enclosures

Enclosures (multimedia attachments to a feed) are specified for RSS 1.0 by mod_enclosure. License, verification (web statement) and more permissions metadata can be provided as with entries.

The following example demonstrates including an MP3 as an enclosure, with additional metadata about the MP3 provided.


<rdf:RDF
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:enc="http://purl.oclc.org/net/rss_2.0/enc#"
  xmlns:cc="http://creativecommons.org/ns#"
  xmlns="http://purl.org/rss/1.0/">
  ...
  <item rdf:about="http://foo.bar/baz">
    <title>There's no pleasing some people..</title>
    ...
    <enc:enclosure rdf:resource="http://foo.bar/baz.mp3" enc:type="audio/mpeg" enc:length="65535"/>
  </item>
        
  <enc:Enclosure rdf:about="http://foo.bar/baz.mp3">
    <cc:license rdf:resource="http://creativecommons.org/licenses/by-nc-nd/3.0/" />
    <cc:morePermissions rdf:resource="http://example.org/pay_me" />
    <xapRights:WebStatement rdf:resource="http://example.org/more_info" />
  </enc:Enclosure>

  ...   
</rdf:RDF>