
More info here.Ī hint for aggregators telling them which hours they can skip. Specifies a text input box that can be displayed with the channel. Specifies a GIF, JPEG or PNG image that can be displayed with the channel. It's a number of minutes that indicates how long a channel can be cached before refreshing from the source. It's for people who might stumble across an RSS file on a Web server 25 years from now and wonder what it is.Īllows processes to register with a cloud to be notified of updates to the channel, implementing a lightweight publish-subscribe protocol for RSS feeds. More info.Ī string indicating the program used to generate the channel.Ī URL that points to the documentation for the format used in the RSS file. Follows the same rules as the -level category element. Specify one or more categories that the channel belongs to.

The last time the content of the channel changed. All date-times in RSS conform to the Date and Time Specification of RFC 822, with the exception that the year may be expressed with two characters or four characters (four preferred). That's when the pubDate of the channel changes. For example, the New York Times publishes on a daily basis, the publication date flips once every 24 hours. The publication date for the content in the channel. You may also use values defined by the W3C.Ĭopyright notice for content in the channel.Ĭopyright 2002, Spartanburg Herald-JournalĮmail address for person responsible for editorial (George Matesky)Įmail address for person responsible for technical issues relating to (Betty Guernsey) A list of allowable values for this element, as provided by Netscape, is here. This allows aggregators to group all Italian language sites, for example, on a single page. Here's a list of optional channel elements. The latest news from, a Spartanburg Herald-Journal Web site. Phrase or sentence describing the channel. The URL to the HTML website corresponding to the channel. If you have an HTML website that contains the same information as your RSS file, the title of your channel should be the same as the title of your website. Here's a list of the required channel elements, each with a brief description, an example, and where available, a pointer to a more complete description. RSS documents can be tested for validity in the RSS Validator.
#Rss reader php class how to
The RSS Profile contains a set of recommendations for how to create RSS documents that work best in the wide and diverse audience of client software that supports the format. The final sections answer frequently asked questions, and provide a roadmap for future evolution, and guidelines for extending RSS. Change notes are here.įirst we document the required and optional sub-elements of and then document the sub-elements of. This document represents the current status of RSS, incorporating all changes and additions starting with the basic spec for RSS 0.91 (June 2000) and follows RSS 0.92 (December 2000), RSS 2.0 (August 2002), and RSS 2.0.1 (July 2003). Maintaining a trail of samples seems like a good idea. The 0.91 sample was created when the 0.91 docs were written. Note that the sample files may point to documents and services that no longer exist. Here are sample files for: RSS 0.91, 0.92 and 2.0.

Subordinate to the element is a single element, which contains information about the channel (metadata) and its contents. If it conforms to this specification, the version attribute must be 2.0. All RSS files must conform to the XML 1.0 specification, as published on the World Wide Web Consortium (W3C) website.Īt the top level, a RSS document is a element, with a mandatory attribute called version, that specifies the version of RSS that the document conforms to. Its name is an acronym for Really Simple Syndication. The current version of the RSS spec will always be available at this link, all changes have been logged and other revisions have been archived. Archivist's Note: This is version 2.0.11 of the RSS 2.0 specification, published by the RSS Advisory Board on March 30, 2009.
