The arguments continue to rage about the ambiguities in the RSS specifications. But the fact is: RSS is here to stay, and the current defined by the RSS 2.0 specification is likely going to be as good as it will stay. Attempts were made to create "best practices" documents and specification clarifications. We feel that it would be helpful to provide general guidelines for those constructing an RSS 2.0 feed. In General, are the following guidelines to build an RSS feed. It's good to have the habit of validating the RSS feed, or with the software, or with an online validator. Here are some general guidelines for creating RSS Feeds: 1. Offices include only one enclosure per item for maximum compatibility. RSS 2.0 specification does not clearly whether multiple enclosures are allowed or not, but most RSS readers only supports a single Cabinet. Therefore, it is better to conform with the readers and include only a single compartment in each RSS feed item. 2. date formats, date formats can be very complicated; Make sure that all dates are formatted correctly. 3. Encodingencoding is required for certain characters. If you are using software to create the feed, it should handle character encoding for you. HTML 4. while the specification is not explicit, it is generally a good idea to not use HTML code in the context of the channel or Item titles. For maximum feed compatibility, the only place you should use the HTML is the RSS Feed Item description. 5 system.GUID GUID (globally unique identifiers) are not required. However, editors are encouraged to use a unique string in the GUID field. Many RSS readers look for GUID changes to determine if new items are available in an RSS feed. 6. Images if you are including an image with the food, the suggested image size is 88 x 31 (the maximum size allowed is 144 x 400). If you are including an image in the Item's description or enclosure of the RSS feed, there is no limitation in size, but keep in mind that overly large graphics will have a negative impact on the amount of time it takes to load the feed. 7. Favicons some RSS readers and search engines will display the favicon of the hosting domain beside the listing for an RSS feed. In order for your feed to stand out, make sure that you include a favicon in the root directory of your site's domain. 8. URLsuse URLs "absolutes" of images, Web sites and links, instead of "relative" URLs. The intent of RSS is to distribute the content, so that the RSS feed may not always be local to the person viewing the feed. As such, you must use the full path of the web for all images, Web sites and links. In other words, don't use ".../ImageUrl.gif", but instead use the full URL "http://www.mydomain.com/imageurl.gif" when linking to any content. 9. Titlesuse a meaningful title for the feed of the channel and RSS feed items. Most RSS directories and search engines use the words in the title of the channel and Item title to sort the RSS feeds.10. mime typesif you are including a file in the enclosure field of an RSS feed, be sure to correctly set the "file size" and the "mime type" file cabinet. A list of appropriate mime type formats can be found here-http://www.feedforall.com/mime-types.htm. 11. Auto-Discovery include RSS code "auto-discovery" in your HTML page header. This will allow some browsers and RSS feed readers automatically know that an RSS feed is available for specific content. Tool to create auto-detection codehttp://www.feedforall.com/autodiscovery.htm 12. Volume the number of items contained in a feed is important. Establish a history and expand the feed on a regular basis. Prune the RSS channels if it becomes excessively long; This will help speed up the loading of RSS feed. About the author:
Sharon Housley manages marketing for FeedForAll http://www.feedforall.com software to create, edit, publish RSS feeds and podcasts. In addition Sharon manages marketing for recording and editing software, RecordForAll http://www.recordforall.com audio.
没有评论:
发表评论