 |
 |
 |
 |
| |
วิธีติด RSS Feeds ไว้ที่หน้าเว็บ
ปกติแล้ว RSS จะมีรูปแบบและโครงสร้างที่ไม่สามารถแสดงเป็นข่าวหรือไม่สามารถอ่านออกโดยผู้ใช้
ทั่วไปได้ หากเว็บของคุณมี RSS ที่สร้างเองหรือจากการคัดลอกมาจากเว็บอื่น อาจเกิดปัญหาในการแสดงข่าวได้
การนำ RSS Feeds ของเราไปติดไว้ที่หน้าเว็บของคุณ จะช่วยทำให้เว็บของคุณสามารถแสดงข่าวจาก RSS ได้
การนำ RSS Feeds ไปติดไว้ที่หน้าเว็บ ก็ทำเช่นเดียวกับการ add RSS ของเว็บไซต์อื่นๆ เช่น Google, Yahoo, MSN แต่การ
add RSS เว็บไซต์เหล่านี้มีข้อจำกัดอยู่ที่ ผู้ใช้ต้องเป็นสมาชิก E-mail ของแต่ละค่ายก่อน แต่การ add RSS ของเรา ผู้ใช้ทั่วไป
ที่เข้ามาดูเว็บของคุณไมจำเป็นต้องเป็นสมาชิกก็สามารถ
ดูข่าวได้
|
|
|
|
 |
 |
 |
| |
วิธีการนำ RSS Feeds ไปติดไว้ที่หน้าเว็บ
เพียงแค่ Save ไฟล์รูป ไปวางไว้ที่เว็บของคุณ แล้วสร้าง Link ดังนี้
http://www.xml-rss.com/rss/add.php?rss=
http://www.pantip.com/tech/rss/xml/basic.xml |
ตัวอักษรสีแดง หมายถึง URL ที่เป็นเอกสารแบบ RSS
ตัวอย่างการ add RSS จากเว็บไซต์ http://www.pantip.com
RSS feeds ของกระทู้กลุ่มต่างๆ และข่าวไอทีใน Technical Exchange |
คอมมือใหม่
|
|
|
|
|
Hardware
|
|
|
|
|
Software |
|
|
|
|
Internet |
|
|
|
|
Games |
|
|
|
|
Developer |
|
|
|
|
Mac/PDA |
|
|
|
|
Com sci &Eng |
|
|
|
|
Electronics |
|
|
|
|
ข่าวไอที |
|
|
|
|
|
| |
|
|
|
|
| RSS is a family of web feed formats used to publish frequently updated digital content, such as blogs, news feeds or podcasts. RSS is analogous to a table of contents. An RSS "feed" provides a table of contents for a site's content for a certain period of time; it does not provide the content itself, but links to the content. RSS is useful because it helps aggregate lots of content into an easily accessible place.
Users of RSS content use software programs called "feed readers" or "feed aggregators". The user subscribes to a feed by entering a link of the feed into the reader program. The reader can then check the user's subscribed feeds to see if any of those feeds have new content since the last time it was checked, and, if so, retrieve that content and present it to the user.
The initials "RSS" are variously used to refer to the following standards:
Really Simple Syndication (RSS 2.0)
Rich Site Summary (RSS 0.91, RSS 1.0)
RDF Site Summary (RSS 0.9 and 1.0)
RSS formats are specified in XML (a generic specification for data formats). RSS delivers its information as an XML file called an "RSS feed," "webfeed," "RSS stream," or "RSS channel".
Action research, article of faith, xe currency.History
Before RSS, several similar formats already existed for syndication, but none achieved widespread popularity or are still in common use today, as most were envisioned to work only with a single service. The basic idea of re-structuring metadata information about web sites has been traced back at least as far as 1995, and the work of Ramanathan V. Guha and others at Apple Computer's (now, Apple Inc.) Advanced Technology Group developing the Meta Content Framework (MCF).[2] Other early work on XML syndication formats, including RDF, took place at Netscape, Userland Software, and Microsoft. For a more detailed discussion of these early developments, see History of web syndication technology.
RDF Site Summary, the first version of RSS, was created by Ramanathan V. Guha of Netscape in March 1999 for use on the My Netscape portal. This version became known as RSS 0.9.[3][verification needed] In July 1999, responding to comments and suggestions, Dan Libby produced a prototype tentatively named RSS 0.91[4] (RSS standing for Rich Site Summary), that simplified the format and incorporated parts of Dave Winer's Scripting News format. [5] This they considered an interim measure, with Libby suggesting an RSS 1.0-like format through the so-called Futures Document.[6]
In April 2001, in the midst of AOL's acquisition and subsequent restructuring of Netscape properties, a re-design of the My Netscape portal removed RSS/XML support. The RSS 0.91 DTD was removed during this re-design, but in response to feedback, Dan Libby was able to restore the DTD, but not the RSS validator previously in place. In response to comments within the RSS community at the time, Lars Marius Garshol, to whom (co?)authorship of the original 0.9 DTD is sometimes attributed, commented, "What I don't understand is all this fuss over Netscape removing the DTD. A well-designed RSS tool, whether it validates or not, would not use the DTD at Netscape's site in any case. There are several mechanisms which can be used to control the dereferencing of references from XML documents to their DTDs. These should be used. If not the result will be as described in the article." [7]
Effectively, this left the format without an owner, just as it was becoming widely used.
A working group and mailing list, RSS-DEV, was set up by various users and XML notables to continue its development. At the same time, Winer unilaterally posted a modified version of the RSS 0.91 specification to the Userland website, since it was already in use in their products. He claimed the RSS 0.91 specification was the property of his company, UserLand Software.[8] Since neither side had any official claim on the name or the format, arguments raged whenever either side claimed RSS as its own, creating what became known as the RSS fork.
The RSS-DEV group went on to produce RSS 1.0 in December 2000.[9] Like RSS 0.9 (but not 0.91) this was based on the RDF specifications, but was more modular, with many of the terms coming from standard metadata vocabularies such as Dublin Core.
Nineteen days later, Winer released by himself RSS 0.92,[10] a minor and supposedly compatible set of changes to RSS 0.91 based on the same proposal. In April 2001, he published a draft of RSS 0.93 which was almost identical to 0.92.[11] A draft RSS 0.94 surfaced in August, reverting the changes made in 0.93, and adding a type attribute to the description element.
In September 2002, Winer released a final successor to RSS 0.92, known as RSS 2.0 and emphasizing "Really Simple Syndication" as the meaning of the three-letter abbreviation. The RSS 2.0 spec removed the type attribute added in RSS 0.94 and allowed people to add extension elements using XML namespaces. Several versions of RSS 2.0 were released, but the version number of the document model was not changed.Action research, article of faith, xe currency.
In November 2002, The New York Times began offering its readers the ability to subscribe to RSS news feeds related to various topics. In January, 2003, Winer called the New York Times' adoption of RSS the "tipping point" in driving the RSS format's becoming a de facto standard.
In July 2003, Winer and Userland Software assigned ownership of the RSS 2.0 specification to his then workplace, Harvard's Berkman Center for the Internet & Society.[12]
In January 2005, Sean B. Palmer, Christopher Schmidt, and Cody Woodard produced a preliminary draft of RSS 1.1.[13] It was intended as a bugfix for 1.0, removing little-used features, simplifying the syntax and improving the specification based on the more recent RDF specifications. As of July 2005, RSS 1.1 had amounted to little more than an academic exercise.
In April 2005, Apple Computer released Safari 2.0 with RSS Feed capabilities built in. Safari delivered the ability to read RSS feeds, and bookmark them, with built-in search features. Safari's RSS button is a blue rounded rectangle with RSS written inside in white, , effectively making the orange square with white radio waves the industry standard for both RSS and related formats such as Atom. Also in February 2006, Opera Software announced they too would add the orange square in their Opera 9 release.
In January 2006, Rogers Cadenhead relaunched the RSS Advisory Board to move the RSS format forward.
In January 2007, as part of a revitalization of Netscape by AOL, the FQDN for my.netscape.com was redirected to a holding page in preparation for an impending relaunch, and as a result some news feeders using RSS 0.91 stopped working. The DTD has again been restored.
Incompatibilities
As noted above, 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:
RSS 0.90 was the original Netscape RSS version. This RSS was called RDF Site Summary, but was based on an early working draft of the RDF standard, and was not compatible with the final RDF Recommendation.
RSS 1.0 is an open format by the RSS-DEV Working Group, again standing for RDF Site Summary. RSS 1.0 is an RDF format like RSS 0.90, but not fully compatible with it, since 1.0 is based on the final RDF 1.0 Recommendation.
RSS 1.1 is also an open format and is intended to update and replace RSS 1.0. The specification is an independent draft not supported or endorsed in any way by the RSS-Dev Working Group or any other organization.
The RSS 2.* branch (initially UserLand, now Harvard) includes the following versions:
RSS 0.91 is the simplified RSS version released by Netscape, and also the version number of the simplified version championed by Dave Winer from Userland Software. The Netscape version was now called Rich Site Summary, this was no longer an RDF format, but was relatively easy to use. It remains the most common RSS variant.
RSS 0.92 through 0.94 are expansions of the RSS 0.91 format, which are mostly compatible with each other and with Winer's version of RSS 0.91, but are not compatible with RSS 0.90. In all Userland RSS 0.9x specifications, RSS was no longer an acronym.
RSS 2.0.1 has the internal version number 2.0. RSS 2.0.1 was proclaimed to be "frozen", but still updated shortly after release without changing the version number. RSS now stood for Really Simple Syndication. The major change in this version is an explicit extension mechanism using XML Namespaces.
For the most part, 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. Mark Pilgrim's article "The Myth of RSS Compatibility" discusses RSS version compatibility in more detail.
The extension mechanisms make it possible for each branch to track 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 mid-2005 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 [1]. 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, including a new proposal from Microsoft for use in Internet Explorer 7.
The most serious compatibility problem is with HTML markup. Userland's RSS readergenerally considered as the reference implementationdid 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 widely expected of readers, to the point of becoming a de facto standard, 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.
Atom
Main article: Atom (standard)
In reaction to recognized issues with RSS (and because RSS 2.0 is frozen), a third group began a new syndication specification, Atom, in June 2003. Their work was later adopted by the Internet Engineering Task Force (IETF) leading to the publication of a specification (RFC 4287) for the Atom Format in 2005. Work on the Atom Publishing Protocol, a standards-based protocol for posting to publishing tools is ongoing.Action research, article of faith, xe currency.
The relative benefits of Atom in comparison to the two RSS branches are a matter of debate within the Web-syndication community. Supporters of Atom claim that it improves on RSS by relying on standard XML features, by specifying a payload container that can handle many different kinds of content unambiguously, and by having a specification maintained by a recognized standards organization. Critics claim that Atom unnecessarily introduces a third branch of syndication specifications, further confusing the marketplace.
Atom aims to define both a syntax and a protocol for updating user blogs and thus goes beyond the simple remit of RSS. While this is appealing to many users, particularly those in the blogging community, it has been met with resistance in the professional community (mainly publishers) due to its lack of extensibility.[15]
For a comparison of Atom 1.0 to RSS 2.0 see Atom Compared to RSS 2.0.
Modules
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:
Ecommerce RSS 2.0 Module [16]
Media RSS 2.0 Module [17]
OpenSearch RSS 2.0 Module [18] Action research, article of faith, xe currency.
BitTorrent and RSS
The peer-to-peer application BitTorrent has also announced support for RSS. Such feeds (also known as Torrent/RSS-es or Torrentcasts) will allow client applications to download files automatically from the moment the rss reader detects them (also known as Broadcatching). Most common BitTorrent clients already offer RSS support.
References
http://www.rssboard.org/rss-mime-type-application.txt
Lash, Alex (1997-10-03). W3C takes first step toward RDF spec. Retrieved on 2007-02-16.
My Netscape Network: Quick Start. Netscape Communications. Archived from the original on 2000-12-08. Retrieved on 2006-10-31.
Libby, Dan (1999-07-10). RSS 0.91 Spec, revision 3. Netscape Communications. Retrieved on 2007-02-14.
Winer, Dave. RSS History.
MNN Future Directions. Netscape Communications. Archived from the original on 2000-12-04. Retrieved on 2006-10-31.
Andrew King (2003-04-13). The Evolution of RSS. Retrieved on 2007-01-17.
Winer, Dave (2000-06-04). RSS 0.91: Copyright and Disclaimer. UserLand Software. Retrieved on 2006-10-31.
RSS-DEV Working Group (2000-12-09). RDF Site Summary (RSS) 1.0. Retrieved on 2006-10-31.
Winer, Dave (2000-12-25). RSS 0.92 Specification. UserLand Software. Retrieved on 2006-10-31.
Winer, Dave (2001-04-20). RSS 0.93 Specification. UserLand Software. Retrieved on 2006-10-31.
RSS 2.0 Specification moves to Berkman. Berkman Center for the Internet & Society (2003-07-15). Retrieved on 2006-10-31.
Palmer, Sean B. and Christopher Schmidt (2005-01-23). RSS 1.1: RDF Site Summary. Retrieved on 2006-10-31.
Simple Sharing Extensions for RSS and OPML. Microsoft (2006-01-12). Retrieved on 2006-10-31.
T. Hammond, T. Hannay, and B. Lund, "The Role of RSS in Science Publishing," D-Lib Magazine, vol. 10, pp. 1082-9873, 2004. Retrieved on 2007-05-01.
Ecommerce RSS Module. Discovery Communications Inc. (2006-10-31). Retrieved on 2006-10-31.
Media RSS Module. Yahoo (2006-10-31). Retrieved on 2006-10-31.
OpenSearch RSS Module. A9.com (2006-10-31). Retrieved on 2006-10-31. Action research, article of faith, xe currency.
See also
Atom
Podcasting
Syndication
RSS Readers
Yahoo! Pipes, a tool for creating mashups of RSS feeds.
Rss tracking
Specifications
RSS 0.90 Specification
RSS 0.91 Spec, revision 3
RSS 1.0 Specifications (RDF Site Summary 1.0) Modules
RSS 2.0 Specification
Draft Microsoft specification for Simple Sharing Extensions to RSS (See Wikipedia article)
Articles
RSS Political Faq (Dave Winer)
History of the RSS Fork (Mark Pilgrim)
Building an RSS feed Tutorial with example. Action research, article of faith, xe currency. |
|