RSS guidelines
Posted by Alan | Posted in guidelines | Posted on 09:08
The arguments continue to rage over the ambiguities in the RSS specifications. But the fact is: RSS is here to stay, and the currently defined RSS 2.0 specification is likely to be as good as it will have. Have tried to create "best practices" documents and specification clarifications. We thought it would be useful to provide the General guidelines for those constructing an RSS 2.0 feed. In General, the following guidelines for the construction of an RSS feed. It is good to get into a habit to validate the RSS feed, either with the software or with an online validator. Here are some general guidelines for creating RSS Feeds: 1. Sample local includes only one enclosure per item for maximum compatibility. RSS 2.0 specification does not clearly state whether multiple enclosures are allowed or not, but most RSS readers support only a single chassis. It is therefore best to satisfy your readers, and includes only a single enclosure in each item of RSS. 2. date formats, date formats, can be very difficult; Make sure that all dates are formatted correctly. 3. Codingcoding required for specific characters. If you are using software to create the feed, it must handle the character encoding for you. 4. HTML specification is not explicit, it is generally a good idea not to use HTML coding in the channel or item titles. For maximum feed compatibility, is the only place you need to use HTML in RSS Feed item description. 5. GUID GUID (Global Unique IDentifiers) are not required. However, publishers are encouraged to use a unique string in the GUID. Many RSS readers look for GUID changes to determine if new items are available in an RSS feed. 6. Images if you include an image with a feed, the suggested image size is 88 x 31 (the maximum allowable size is 144 x 400). If you include an image in the RSS feed item description or enclosure fields, not size, but keep in mind that excessively large graphics negative effect on the amount of time it takes to load the feed. 7. Favicons some RSS readers and search engines favicon of video hosting services domain beside the list to an RSS feed. To your feed to stand out, make sure that you include a favicon in the root directory of your site's domain. 8. Urlsuse "absolute" URLs for images, home pages and links, instead of "relative" URLs. The intent of RSS is to publish content, so the RSS feed may not always be local to the person who sees the diet. As such, it should be full web path for all images, Web sites and malicious hyperlinks used. In other words, do not use ".../ImageUrl.gif ", but instead use the full URL address" http://www.mydomain.com/imageurl.gif "by linking to content. 9. Titlesuse a meaningful title for the channel feed and RSS feed elements. Most RSS directories and search engines use the words in the channel title and topic title to classify RSS feeds.10. MIME typesif you include a file in the enclosure in an RSS feed, you must remember to properly define "file size" and "MIME-type" of the file enclosure. A list of properly MIME-type formats can be found here-http://www.feedforall.com/mime-types.htm. 11. Auto-Discovery includes RSS feed "auto-discovery" code in the HTML header. This will allow certain browsers and RSS feed readers to automatically know that an RSS feed is available for specific content. Tool to createAutoDiscovery code-http://www.feedforall.com/autodiscovery.htm 12. Volume the number of items in a feed is important. Establish a history and expand the feed on a regular basis. Cropping RSS feed if it becomes too long; This will help to make the RSS feed load faster. About the author:
Sharon Housley manages marketing for FeedForAll http://www.feedforall.com software for creating, editing and publishing RSS feeds and podcasts. In addition Sharon manages marketing for RecordForAll http://www.recordforall.com audio recording and editing software.