Alternative Formats If You Require This Document in an Alternative Format, Please Contact: [email protected]
Total Page:16
File Type:pdf, Size:1020Kb
Citation for published version: Kelly, B 2005, 'RSS - More Than Just News Feeds', New review of information networking, vol. 11, no. 2. https://doi.org/10.1080/13614570600573425 DOI: 10.1080/13614570600573425 Publication date: 2005 Link to publication University of Bath Alternative formats If you require this document in an alternative format, please contact: [email protected] General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. Take down policy If you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim. Download date: 25. Sep. 2021 RSS �/ MORE THAN JUST NEWS FEEDS Brian Kelly RSS (Really Simple Syndication/RDF Site Summary) is a simple lightweight format that was originally used for news alerts and content syndication. It is now being used in a wide range of applications. This paper describes the background to RSS and describes the various ways in which RSS can be used. Examples are provided of the ways in which RSS can be viewed and the variety of approaches for creating RSS. The paper argues that, although there is still confusion over the different types of RSS standards, the format is an essential for use in digital library services. Background The roots of the RSS (which, confusingly, can stand for both Really Simple Syndication and RDF Site Summary) format date back to the mid 1990s. Once the Web had demonstrated its rich potential and had moved from its research and academic roots to use by the general public, many organisations began to explore ways in which they could enhance the services they provided. An early innovation was provided by the BBC (British Broadcasting Corporation), which developed an application that made use of ‘push’ technology to send news to a desktop application, which continually displayed the news using a tickertape display, as illustrated in Figure 1. The news content was continually updated, so there was no need for the users to ‘go’ to a particular Web page. This approach proved very popular. It became clear that many users valued this type of interface and the push approach it provided. There was a need for a similar approach to access information provided by other information providers, and not just the BBC. Similarly there was a desire by information providers to deploy similar services. However the BBC’s approach was proprietary, making use of an internal file format developed by the BBC and their own desktop application. There was a need for an open format that could be used to provide access to news feeds. The availability of an open file format would provide benefits of scale and help develop a market for viewers and authoring tools. Netscape’s Contribution In the mid 1990s Netscape was the most popular Web browser. Netscape sought to exploit that position by developing a Web portal that provided access to Web resources. An innovative feature of the Netscape portal was its personalisation capabilities: rather than providing a static list of resources, users of the My.Netscape portal could select the information sources of interest to them. This could include ‘channels’ of local weather reports, information on preferred TV channels, etc. In order to access to the channels Netscape developed a file format known as RSS, which stood for Rich Site Summary. This format could New Review of Information Networking, Vol. 11, No. 2, 2005 ISSN 1361-4576 print/1740-7869 online/0219 �/09 # 2005 Taylor & Francis DOI: 10.1080/13614570600573425 220 BRIAN KELLY FIGURE 1 The BBC News ticker be used by any content provider who wished to allow their content to be accessed through the My.Netscape portal. RSS Wars The approach developed by Netscape proved popular. Unfortunately, around this time, Netscape was suffering from competition from Microsoft and the company was undergoing changes as a result of company mergers and a refocusing of its business activities. As a result of this, Netscape ceased their involvement in RSS development. Netscape also deleted the SGML file that defined the RSS format, which had the unfortunate effect of causing many applications to cease working. However, the functionality provided by RSS had, by this time, proved its worth. The Blogging community, for example, needed a mechanism for providing alerts and syndication of new postings. Similarly the W3C (World Wide Web Consortium) recognised the potential for RSS and wished to use it for providing news feeds for the W3C. Developers closely associated with the W3C’s Semantic Web activities built on Netscape’s initial work and released a new version of RSS based on the W3C’s RDF (Resource Description Framework) standard. In this new version, known as RSS 1.0,1 the RSS abbreviation was changed to stand for RDF Site Summary, in order to differentiate itself from its predecessor. However despite the importance, which W3C gives to RDF and the Semantic Web, in some sectors RDF is felt to be a cumbersome and unwieldy format. Led by David Winer, an alterative format to RSS 1.0 was developed �/ confusingly also known as RSS, which, in RSS 2.02 stands for Really Simple Syndication. From an end user’s perspective these RSS ‘wars’ are confusing: many users will regard RSS 2.0 as a later version to RSS 1.0 and not a different format. In practice, however, most RSS viewers will work with both versions of RSS and there are efforts to bring together the divergent standards. Despite this confusion, the benefits of RSS are widely acknowledged and many RSS tools are available. The confusion over the RSS name should not be regarded as a barrier to making use of RSS. Viewing RSS RSS is sometimes regarded as a mechanism for embedding content from third parties in a Web site. UKOLN’s RSS-xpress3 was an early pioneer in this RSS �/ MORE THAN JUST NEWS FEEDS 221 area. RSS-xpress can be used to display RSS feeds within a Web site. RSS-xpress is a CGI program that can be installed locally, and the interface configured with the local look-and-feel. Use of RSS-xpress requires System Administrator privileges for the software to be installed on a Web server. A simpler approach is to make use of a solution that uses JavaScript to access the RSS file and to convert the content to HTML format. The RSS-xpress Lite4 software illustrates this approach. These two examples illustrate techniques for embedding RSS into Web pages (and similar applications, such as the Higher Education Academy’s RSS Configurator,5 are available). As well as embedding RSS resources within Web pages, many dedicated RSS viewers are available as can be seen from the lists of RSS tools.6 Applications such as Bloglines7 and Awasu,8 illustrated in Figures 2 and 3, provide easy-to-use interfaces for selecting RSS news feeds and for managing alerts. Creating RSS Because RSS is a simple XML format (as can be seen from the example shown in Figure 4) it is possible to create RSS files by hand. However, because such a method is prone to errors, a better approach is to make use of an RSS editor. A number of dedicated RSS editors are available. The RSS-express software, which has been mentioned previously, can be used for creating and editing, in addition to viewing RSS files. As well as use of dedicated RSS editors, there are other approaches to creating RSS files. Content Management Systems (CMSs) may provide the ability FIGURE 2 The Bloglines RSS viewer 222 BRIAN KELLY FIGURE 3 The Awasu Desktop RSS viewer to create RSS files, either through dedicated support for RSS or through the creation of appropriate templates. An alternative approach is to create an RSS file by transforming data from other formats: for example it is possible to transform HTML files to RSS format (or, indeed, RSS to HTML). <channel> <title>BBC News | UK | UK Edition</title> <link>http://news.bbc.co.uk/hi/uk/default.stm</link> <description>BBC UK News updated every minute of every day</description> </channel> <item> <title>Clare Short quits post over Iraq</title> <description>Clare Short quits the cabinet, accusing Tony Blair of breaking his promises over the UN's role in rebuilding Iraq.</description> <link>http://news.bbc.co.uk/hi/uk_politics/3019871.stm</link> </item> FIGURE 4 Example of an RSS file RSS �/ MORE THAN JUST NEWS FEEDS 223 When planning the architecture for creating RSS, it will be necessary to be aware of the strengths and weaknesses of the different approaches. By hand : Experienced Web developers may wish to create RSS files ‘by hand’ �/ i.e. using a simple text editor and inputting the data and the RSS markup elements manually. This approach may be suitable in some cases, but not as a general solution. It should be noted that in cases in which this approach is used, it is important to validate the RSS file in order to ensure that no errors have been made when entering the RSS markup elements. Dedicated RSS editor : Use of a dedicated RSS editor requires no knowledge of the RSS format. A limitation of this approach is that the data has to be entered by hand rather than reusing existing data. This approach can then result in the appearance of minor discrepancies. Use of Backend CMS/Database : A third approach is to create the RSS directly from a backend database or Content Management System (CMS).