出典(authority):フリー百科事典『ウィキペディア(Wikipedia)』「2017/05/18 21:44:44」(JST)
ウィキペディアにおけるRSSについては、Help:フィードの利用をご覧ください。 |
この項目では、ウェブサイトの更新情報を提供するデータの形式について説明しています。その他の用法については「RSS (曖昧さ回避)」をご覧ください。 |
拡張子 | .rss, .xml, .rdf |
---|---|
MIMEタイプ | application/rdf+xml, application/xml |
派生元 | XML |
RSSは、ニュースやブログなど各種のウェブサイトの更新情報を簡単にまとめ、配信するための幾つかの文書フォーマットの総称である。
上記の様に「RSS」という語には、名称の異なる複数の規格が存在しており、それぞれ記述方法や用途が異なるために、多少の混乱が見られる。
ブログでの更新情報の配信として用いられている場合が大半を占めているが、ニュース配信サイトでは最新ニュースを、放送局では番組情報を、その他各種企業においてプレスリリースや新製品情報、サポート情報を、RSSを使ったヘッドライン情報として配信する事例も増えている。また、音声データファイルを公開するための方法であるポッドキャスティングにも使われている。
また、RSSに対応しているウェブサイトではRSSに対応していることを明確にするために下記のような表示が使われていることが多い。
RSSはRDFの採用をめぐって現在分裂状態にあり、1.0と2.0の2つの系列に分かれている。当初、0.9はRDFをベースにしたデータ形式を利用していたが、0.91ではシンプル化するためにRDFを利用しなくなった。その後、1.0では0.9の系列を引継ぎ、複雑なRDFを採用することで応用性の高いデータを利用できるようにした。これに対して、2.0は0.91を引継ぎ、コンテンツ配信に特化することで複雑なRDFを排除している。
最初のRSSであるRSS 0.9は、RDF site summary[1][2]として、1999年3月に米国ネットスケープコミュニケーションズが自社のポータルサイト「My Netscape」において、「チャンネル」の詳細を記すために策定したものである。RDF構文を用いたことから、RDF site summaryと呼ばれる。
その後ネットスケープコミュニケーションズはRDF構文の利用を止め、独自のXMLフォーマットを用いて要素を拡張し、よりリッチな情報を提供できるようにしたRSS 0.91を開発した。
rich site summaryと改名されたRSS 0.91は、RSS 0.9に要素を拡張する目的で作られ、1999年7月にこのバージョンがリリースされた。RDFを用いず、独自のXMLで記述される。
ユーザーランド・ソフトウェア社(UserLand Software)の「スクリプティングニュース」(ScriptingNews)から著作権、日付情報などいくつかの要素を取り入れ拡張された。それまでのRSS 0.9より多くの情報を配信できるようになったため、rich site summary[3]と呼ばれ、その後派生したRSS 0.92、RSS 2.0のベースとなっている。
RSS 0.91の登場以降、RSSが持つ「コンテンツ配信」機能に対しての需要がさらに高まった。そのためよりリッチなコンテンツ配信を目指そうとする制作者が、独自の要素をRSSに追加してしまうなど、フォーマットの拡張における混乱がおこることとなった。
こうした混乱のなかで、RSSでよく使われる語彙や使われる要素群を「コア」として定義し、それ以外は拡張する側が独自の語彙を「モジュール」として定義することで、中核語彙と拡張性を保証させようとする提案が RSS-DEV ワーキンググループ内で起こり、その成果として2000年12月にRSS 1.0がリリースされた。
RSS 1.0は0.9時代につかわれていたRDFを再び採用し、RSSが持つ「メタデータ記述」としての側面を主眼に置いたフォーマットとなっている。
また、RSSコアモジュールの他に公式なモジュールとして、Dublin Core
モジュール、Syndication
モジュール及び Content
モジュールが定められた。これにより RSS 0.9の不満であった語彙の乏しさを解消させ、またコンテンツ配信手段としてRSS 1.0を採用する道を残すものとなった。
RSS 1.0 の登場は、(メタデータ記述技術としての)RSSの中核語彙及び拡張性を保証するものとなった。しかしRDFを再び採用したこと、モジュールによるXML名前空間の複雑化はすべてのRSS配信者を満足させず、RSS 0.91 系のフォーマットを拡張する動きが再びみられることとなった。
RSS 1.0の取る道は必ずしも誰もが好むものではなかった、とはいえRSS 0.91以降に起きていたフォーマット拡張の混乱は避ける必要があった。そのため拡張をオプションとして提供し、かつRSS 0.91への互換性を持たせる方法が提案され、それを受けて2000年12月にユーザーランド・ソフトウェア社からRSS 0.92が発表された。
ユーザーランド・ソフトウェア社はその後も互換性を維持したままRSS 0.93、RSS 0.94という拡張を続けたが、2002年8月にRSS 0.91 からRSS 0.94までのすべてのフォーマットに対する互換性を保証したRSS 2.0を策定し、これをreally simple syndication[4]と名付けた。
RSS 2.0はあくまで0.9x系の流れを汲む規格であって、RSS 1.0の後継ではない。それぞれの目指す方向性は同じではないため、場面に応じて使い分けられている。
2003年7月に、RSS 2.0制定の中心人物、デイヴ・ウィナー(Dave Winer)の移籍と併せ、仕様もハーヴァード大学ロースクールのバークマンセンターに移管された。
RSS 1.0 と RSS 2.0 の関係について、バージョンを表す数値の大小関係から、前者が旧規格で後者が後継規格であるという誤解が見受けられるが、これは事実ではない。RSS 2.0 はシンプルさの代償として RSS 1.0 の備える(RDFによる)強力な表現力を放棄したため、RSS 1.0 を置き換えるものではない。従って RSS 1.0 は場面に応じて今後も継続利用されていくと目される。[要出典]
一方、RSS 2.0 に代わるコンテンツ配信技術として、IBMのサム・ルビー(Sam Ruby)などが中心となり、Atom と呼ばれる新しい規格が策定された。Atom にはウェブログ・ツール「ムーバブル・タイプ」(Movable Type)の開発元のシックス・アパート社(Six Apart)やスタンフォード大学法学部のローレンス・レッシグ教授、XML開発者のティム・ブレイ(Tim Bray)などが支持を表明し、またGoogleも自社のサービス
今日において、RSS 1.0、RSS 2.0 そして Atom は、いずれにも集約されることなく各々が広く普及している。RSSリーダーの多くはそれら全てに対応しており、一方のウェブサイト側も、フィード配信のためにそれらのうち複数を利用することも珍しくない。
RSSの取得・購読にはRSSリーダー(フィードリーダーとも)と呼ばれるソフトウェアを使う。また、RSSを作成・追加するためのソフトウェアもあるが、比較的シンプルなXML形式なので手作業でも可能である。
情報を扱う専門機関としての図書館においてもRSSの活用サービス例は増えている。お知らせの配信などはもっとも活用されている例である。京都大学図書館機構などでは、学生や研究者向けにRSSについての概要や活用方法などをまとめている。また、農林水産研究情報センターでは、新着雑誌、新着図書情報などもRSSによって配信している。
Filename extension | .rss, .xml |
---|---|
Internet media type | application/rss+xml (registration not finished)[1] |
Type of format | Web syndication |
Extended from | XML |
RSS (Rich Site Summary; originally RDF Site Summary; often called Really Simple Syndication) is a type of web feed[2] which allows users to access updates to online content in a standardized, computer-readable format. These feeds can, for example, allow a user to keep track of many different websites in a single news aggregator. The news aggregator will automatically check the RSS feed for new content, allowing the content to be automatically passed from website to website or from website to user. This passing of content is called web syndication. Websites usually use RSS feeds to publish frequently updated information, such as blog entries, news headlines, audio, video. An RSS document (called "feed", "web feed",[3] or "channel") includes full or summarized text, and metadata, like publishing date and author's name.
A standard XML file format ensures compatibility with many different machines/programs. RSS feeds also benefit users who want to receive timely updates from favourite websites or to aggregate data from many sites.
Subscribing to a website RSS removes the need for the user to manually check the website for new content. Instead, their browser constantly monitors the site and informs the user of any updates. The browser can also be commanded to automatically download the new data for the user.
RSS feed data is presented to users using software called a news aggregator. This aggregator can be built into a website, installed on a desktop computer, or installed on a mobile device. Users subscribe to feeds either by entering a feed's URI into the reader or by clicking on the browser's feed icon. The RSS reader checks the user's feeds regularly for new information and can automatically download it, if that function is enabled. The reader also provides a user interface.
This section needs to be updated. Please update this article to reflect recent events or newly available information. (October 2013) |
The RSS formats were preceded by several attempts at web syndication that did not achieve widespread popularity. The basic idea of restructuring information about websites goes back to as early as 1995, when Ramanathan V. Guha and others in Apple Computer's Advanced Technology Group developed the Meta Content Framework.[4]
RDF Site Summary, the first version of RSS, was created by Dan Libby and Ramanathan V. Guha at Netscape. It was released in March 1999 for use on the My.Netscape.Com portal.[5] This version became known as RSS 0.9.[6] In July 1999, Dan Libby of Netscape produced a new version, RSS 0.91,[2] which simplified the format by removing RDF elements and incorporating elements from Dave Winer's news syndication format.[7] Libby also renamed the format from RDF to RSS Rich Site Summary and outlined further development of the format in a "futures document".[8]
This would be Netscape's last participation in RSS development for eight years. As RSS was being embraced by web publishers who wanted their feeds to be used on My.Netscape.Com and other early RSS portals, Netscape dropped RSS support from My.Netscape.Com in April 2001 during new owner AOL's restructuring of the company, also removing documentation and tools that supported the format.[9]
Two parties emerged to fill the void, with neither Netscape's help nor approval: The RSS-DEV Working Group and Dave Winer, whose UserLand Software had published some of the first publishing tools outside Netscape that could read and write RSS.
Winer published a modified version of the RSS 0.91 specification on the UserLand website, covering how it was being used in his company's products, and claimed copyright to the document.[10] A few months later, UserLand filed a U.S. trademark registration for RSS, but failed to respond to a USPTO trademark examiner's request and the request was rejected in December 2001.[11]
The RSS-DEV Working Group, a project whose members included Guha and representatives of O'Reilly Media and Moreover, produced RSS 1.0 in December 2000.[12] This new version, which reclaimed the name RDF Site Summary from RSS 0.9, reintroduced support for RDF and added XML namespaces support, adopting elements from standard metadata vocabularies such as Dublin Core.
In December 2000, Winer released RSS 0.92[13] a minor set of changes aside from the introduction of the enclosure element, which permitted audio files to be carried in RSS feeds and helped spark podcasting. He also released drafts of RSS 0.93 and RSS 0.94 that were subsequently withdrawn.[14]
In September 2002, Winer released a major new version of the format, RSS 2.0, that redubbed its initials Really Simple Syndication. RSS 2.0 removed the type attribute added in the RSS 0.94 draft and added support for namespaces. To preserve backward compatibility with RSS 0.92, namespace support applies only to other content included within an RSS 2.0 feed, not the RSS 2.0 elements themselves.[15] (Although other standards such as Atom attempt to correct this limitation, RSS feeds are not aggregated with other content often enough to shift the popularity from RSS to other formats having full namespace support.)
Because neither Winer nor the RSS-DEV Working Group had Netscape's involvement, they could not make an official claim on the RSS name or format. This has fueled ongoing controversy[specify] in the syndication development community as to which entity was the proper publisher of RSS.
One product of that contentious debate was the creation of an alternative syndication format, Atom, that began in June 2003.[16] The Atom syndication format, whose creation was in part motivated by a desire to get a clean start free of the issues surrounding RSS, has been adopted as IETF Proposed Standard RFC 4287.
In July 2003, Winer and UserLand Software assigned the copyright of the RSS 2.0 specification to Harvard's Berkman Center for Internet & Society, where he had just begun a term as a visiting fellow.[17] At the same time, Winer launched the RSS Advisory Board with Brent Simmons and Jon Udell, a group whose purpose was to maintain and publish the specification and answer questions about the format.[18]
In September 2004, Stephen Horlander created the now ubiquitous RSS icon () for use in the Mozilla Firefox browser.[19]
In December 2005, the Microsoft Internet Explorer team[20] and Microsoft Outlook team[21] announced on their blogs that they were adopting Firefox's RSS icon. In February 2006, Opera Software followed suit.[22] This effectively made the orange square with white radio waves the industry standard for RSS and Atom feeds, replacing the large variety of icons and text that had been used previously to identify syndication data.
In January 2006, Rogers Cadenhead relaunched the RSS Advisory Board without Dave Winer's participation, with a stated desire to continue the development of the RSS format and resolve ambiguities. In June 2007, the board revised their version of the specification to confirm that namespaces may extend core elements with namespace attributes, as Microsoft has done in Internet Explorer 7. According to their view, a difference of interpretation left publishers unsure of whether this was permitted or forbidden.
RSS is XML formatted plain text. The RSS format itself is relatively easy to read both by automated processes and by humans alike. An example feed could have contents such as the following:
<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
<channel>
<title>RSS Title</title>
<description>This is an example of an RSS feed</description>
<link>http://www.example.com/main.html</link>
<lastBuildDate>Mon, 06 Sep 2010 00:01:00 +0000 </lastBuildDate>
<pubDate>Sun, 06 Sep 2009 16:20:00 +0000</pubDate>
<ttl>1800</ttl>
<item>
<title>Example entry</title>
<description>Here is some text containing an interesting description.</description>
<link>http://www.example.com/blog/post/1</link>
<guid isPermaLink="true">7bd204c6-1655-4c27-aeee-53f933c5395f</guid>
<pubDate>Sun, 06 Sep 2009 16:20:00 +0000</pubDate>
</item>
</channel>
</rss>
When retrieved, reading software could use the XML structure to present a neat display to the end users.
There are several different versions of RSS, falling into two major branches (RDF and 2.*).
The RDF (or RSS 1.*) branch includes the following versions:
The RSS 2.* branch (initially UserLand, now Harvard) includes the following versions:
Later versions in each branch are backward-compatible with earlier versions (aside from non-conformant RDF syntax in 0.90), and both versions include properly documented extension mechanisms using XML Namespaces, either directly (in the 2.* branch) or through RDF (in the 1.* branch). Most syndication software supports both branches. "The Myth of RSS Compatibility", an article written in 2004 by RSS critic and Atom advocate Mark Pilgrim, discusses RSS version compatibility issues in more detail.
The extension mechanisms make it possible for each branch to copy innovations in the other. For example, the RSS 2.* branch was the first to support enclosures, making it the current leading choice for podcasting, and as of 2005[update] is the format supported for that use by iTunes and other podcasting software; however, an enclosure extension is now available for the RSS 1.* branch, mod_enclosure. Likewise, the RSS 2.* core specification does not support providing full-text in addition to a synopsis, but the RSS 1.* markup can be (and often is) used as an extension. There are also several common outside extension packages available, e.g. one from Microsoft for use in Internet Explorer 7.
The most serious compatibility problem is with HTML markup. Userland's RSS reader—generally considered as the reference implementation—did not originally filter out HTML markup from feeds. As a result, publishers began placing HTML markup into the titles and descriptions of items in their RSS feeds. This behavior has become expected of readers, to the point of becoming a de facto standard,[citation needed] though there is still some inconsistency in how software handles this markup, particularly in titles. The RSS 2.0 specification was later updated to include examples of entity-encoded HTML; however, all prior plain text usages remain valid.
As of January 2007[update], tracking data from www.syndic8.com indicates that the three main versions of RSS in current use are 0.91, 1.0, and 2.0, constituting 13%, 17%, and 67% of worldwide RSS usage, respectively.[24] These figures, however, do not include usage of the rival web feed format Atom. As of August 2008[update], the syndic8.com website is indexing 546,069 total feeds, of which 86,496 (16%) were some dialect of Atom and 438,102 were some dialect of RSS.[25]
The primary objective of all RSS modules is to extend the basic XML schema established for more robust syndication of content. This inherently allows for more diverse, yet standardized, transactions without modifying the core RSS specification.
To accomplish this extension, a tightly controlled vocabulary (in the RSS world, "module"; in the XML world, "schema") is declared through an XML namespace to give names to concepts and relationships between those concepts.
Some RSS 2.0 modules with established namespaces are:
Although the number of items in an RSS channel is theoretically unlimited, some news aggregators do not support RSS files larger than 150KB. For example, applications that rely on the Common Feed List of Windows might handle such files as if they were corrupt, and not open them. Interoperability can be maximized by keeping the file size under this limit.
Some BitTorrent clients support RSS. RSS feeds which provide links to .torrent files allow users to subscribe and automatically download content as soon as it is published.
Some services deliver RSS to email inbox, sending updates from user's personal selection and schedules.[26][27] Conversely, some services deliver email to RSS readers.[28]
Both RSS and Atom are widely supported and are compatible with all major consumer feed readers. RSS gained wider use because of early feed reader support. Technically, Atom has several advantages: less restrictive licensing, IANA-registered MIME type, XML namespace, URI support, Relax NG support.[29]
The following table shows RSS elements alongside Atom elements where they are equivalent.
Note: the asterisk character (*) indicates that an element must be provided (Atom elements "author" and "link" are only required under certain conditions).
RSS 2.0 | Atom 1.0 |
---|---|
author |
author * |
category |
category |
channel |
feed |
copyright |
rights |
- |
subtitle |
description * |
summary and/or content |
generator |
generator |
guid |
id * |
image |
logo |
item |
entry |
lastBuildDate (in channel ) |
updated * |
link * |
link * |
managingEditor |
author or contributor |
pubDate |
published (subelement of entry ) |
title * |
title * |
ttl |
- |
Several major sites such as Facebook and Twitter previously offered RSS feeds but have reduced or removed support. Additionally, widely used readers such as Shiira, FeedDemon, and Google Reader have been discontinued having cited declining popularity in RSS.[30] RSS support was removed in OS X Mountain Lion's versions of Mail and Safari, although the features were partially restored in Safari 8.[31][32] As of August 2015, Mozilla Firefox and Internet Explorer include RSS support by default, while Google Chrome and Microsoft Edge do not. Additionally, reader services such as Feedly provide synchronization between desktop RSS readers and mobile devices.
The conflict centers on something called Really Simple Syndication (RSS), a technology widely used to syndicate blogs and other Web content. The dispute pits Harvard Law School fellow Dave Winer, the blogging pioneer who is the key gatekeeper of RSS, against advocates of a different format.
Wikimedia Commons has media related to RSS. |
Web syndication
|
|||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||||||
Types |
|
||||||||||||||||||||||||||
Technology |
|
||||||||||||||||||||||||||
Form |
|
||||||||||||||||||||||||||
Media |
|
News aggregators
|
|||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Client software |
|
||||||||||||||
Web-based software and |
|
||||||||||||||
Media aggregators |
|
||||||||||||||
Related articles |
|
||||||||||||||
Italics indicate discontinued software.
|
Data exchange formats
|
|
---|---|
Human readable formats |
|
Binary formats |
|
Authority control |
|
---|
全文を閲覧するには購読必要です。 To read the full text you will need to subscribe.
リンク元 | 「免疫不全症候群」「ラッセル・シルヴァー症候群」「再構成シグナル配列」 |
拡張検索 | 「RSSE」 |
関連記事 | 「R」「RS」 |
.