rss 2.0格式
转
1
<?xml version="1.0" ?>
2<rss version="2.0">
3 <channel>
4 <!--Required Elements Begin-->
5 <title>
6 <!--The name of the channel.-->
7 <!--It's how people refer to your service.-->
8 <!--If you have an HTML website that contains the same information as your RSS file, the title of your channel should be the same as the title of your website.-->
9 <!--[Example:GoUpstate.com News Headlines]-->
10 </title>
11 <link>
12 <!--The URL to the HTML website corresponding to the channel.-->
13 <!--[Example:http://www.goupstate.com/]-->
14 </link>
15 <description>
16 <!--Phrase or sentence describing the channel.-->
17 <!--[Example:The latest news from GoUpstate.com, a Spartanburg Herald-Journal Web site.]-->
18 </description>
19 <!--Required Elements End-->
20 <!--Optional Elements Begin-->
21 <language>
22 <!--The language the channel is written in.-->
23 <!--This allows aggregators to group all Italian language sites, for example, on a single page. A list of allowable values for this element, as provided by Netscape, is here.-->
24 <!--You may also use values defined by the W3C.-->
25 <!--[Example:en-us]-->
26 </language>
27 <copyright>
28 <!--Copyright notice for content in the channel.-->
29 <!--[Example:Copyright 2002, Spartanburg Herald-Journal]-->
30 </copyright>
31 <managingEditor>
32 <!--Email address for person responsible for editorial content.-->
33 <!--[Example:geo@herald.com (George Matesky)]-->
34 </managingEditor>
35 <webMaster>
36 <!--Email address for person responsible for technical issues relating to channel.-->
37 <!--[Example:betty@herald.com (Betty Guernsey)]-->
38 </webMaster>
39 <pubDate>
40 <!--The publication date for the content in the channel.-->
41 <!--For example, the New York Times publishes on a daily basis, the publication date flips once every 24 hours.-->
42 <!--That's when the pubDate of the channel changes.-->
43 <!--All date-times in RSS conform to the Date and Time Specification of RFC 822, with the exception that the year may be expressed with two characters or four characters (four preferred).-->
44 <!--[Example:Sat, 07 Sep 2002 00:00:01 GMT]-->
45 </pubDate>
46 <lastBuildDate>
47 <!--The last time the content of the channel changed.-->
48 <!--[Example:Sat, 07 Sep 2002 09:42:31 GMT]-->
49 </lastBuildDate>
50 <category>
51 <!--one or more categories that the channel belongs to.-->
52 <!--Follows the same rules as the <item>-level category element.-->
53 <!--[Example:<category>Newspapers</category>]-->
54 </category>
55 <generator>
56 <!--A string indicating the program used to generate the channel.-->
57 <!--[Example:MightyInHouse Content System v2.3]-->
58 </generator>
59 <docs>
60 <!--A URL that points to the documentation for the format used in the RSS file.-->
61 <!--It's probably a pointer to this page.-->
62 <!--It's for people who might stumble across an RSS file on a Web server 25 years from now and wonder what it is.-->
63 <!--[Example:http://blogs.law.harvard.edu/tech/rss]-->
64 </docs>
65 <cloud>
66 <!--processes to register with a cloud to be notified of updates to the channel, implementing a lightweight publish-subscribe protocol for RSS feeds.-->
67 <!--[Example:<cloud domain="rpc.sys.com" port="80" path="/RPC2" registerProcedure="pingMe" protocol="soap"/>]-->
68 <!--It specifies a web service that supports the rssCloud interface which can be implemented in HTTP-POST, XML-RPC or SOAP 1.1.-->
69 <!--Its purpose is to allow processes to register with a cloud to be notified of updates to the channel, implementing a lightweight publish-subscribe protocol for RSS feeds.-->
70 <!--<cloud domain="rpc.sys.com" port="80" path="/RPC2" registerProcedure="myCloud.rssPleaseNotify" protocol="xml-rpc" />-->
71 <!--In this example, to request notification on the channel it appears in, you would send an XML-RPC message to rpc.sys.com on port 80, with a path of /RPC2. The procedure to call is myCloud.rssPleaseNotify.-->
72 </cloud>
73 <ttl>
74 <!--ttl stands for time to live.-->
75 <!--It's a number of minutes that indicates how long a channel can be cached before refreshing from the source.-->
76 <!--[Example:<ttl>60</ttl>]-->
77 </ttl>
78 <image>
79 <!--Required Elements Of <image> Begin-->
80 <!--a GIF, JPEG or PNG image that can be displayed with the channel.-->
81 <url>
82 <!--is the URL of a GIF, JPEG or PNG image that represents the channel.-->
83 </url>
84 <title>
85 <!--describes the image, it's used in the ALT attribute of the HTML <img> tag when the channel is rendered in HTML.-->
86 </title>
87 <link>
88 <!--is the URL of the site, when the channel is rendered, the image is a link to the site. (Note, in practice the image <title> and <link> should have the same value as the channel's <title> and <link>.-->
89 </link>
90 <!--Required Elements Of <image> End-->
91 <!--Optional Elements Of <image> Begin-->
92 <width>
93 <!--Maximum value for width is 144, default value is 88.-->
94 </width>
95 <height>
96 <!--Maximum value for height is 400, default value is 31.-->
97 </height>
98 <!--Optional Elements Of <image> End-->
99 </image>
100 <rating>
101 <!--The PICS rating for the channel.]-->
102 </rating>
103 <textInput>
104 <!--Specifies a text input box that can be displayed with the channel.-->
105 <!--The purpose of the <textInput> element is something of a mystery.-->
106 <!--You can use it to specify a search engine box. Or to allow a reader to provide feedback.-->
107 <!--Most aggregators ignore it.-->
108 <!--Required Elements Of <textInput> Begin-->
109 <title>
110 <!--The label of the Submit button in the text input area.-->
111 </title>
112 <description>
113 <!--Explains the text input area.-->
114 </description>
115 <name>
116 <!--The name of the text object in the text input area.-->
117 </name>
118 <link>
119 <!--The URL of the CGI script that processes text input requests.-->
120 </link>
121 <!--Required Elements Of <textInput> End-->
122 </textInput>
123 <skipHours>
124 <!--A hint for aggregators telling them which hours they can skip.-->
125 </skipHours>
126 <skipDays>
127 <!--A hint for aggregators telling them which days they can skip.-->
128 </skipDays>
129 <!--Optional Elements End-->
130 <item>
131 <!--Optional Elements Of <item> Begin-->
132 <title>
133 <!--The title of the item.-->
134 <!--[Example:Venice Film Festival Tries to Quit Sinking]-->
135 </title>
136 <link>
137 <!--The URL of the item.-->
138 <!--[Example:http://nytimes.com/2004/12/07FEST.html]-->
139 </link>
140 <description>
141 <!--The item synopsis.-->
142 <!--[Example:Some of the most heated chatter at the Venice Film Festival this week was about the way that the arrival of the stars at the Palazzo del Cinema was being staged.]-->
143 </description>
144 <author>
145 <!--Email address of the author of the item.-->
146 <!--It's the email address of the author of the item.-->
147 <!--For newspapers and magazines syndicating via RSS, the author is the person who wrote the article that the <item> describes.-->
148 <!--For collaborative weblogs, the author of the item might be different from the managing editor or webmaster.-->
149 <!--For a weblog authored by a single individual it would make sense to omit the <author> element.-->
150 <!--<author>lawyer@boyer.net (Lawyer Boyer)</author>-->
151 </author>
152 <category domain="optional, identifies a categorization taxonomy.">
153 <!--Includes the item in one or more categories.-->
154 <!--It has one optional attribute, domain, a string that identifies a categorization taxonomy.-->
155 <!--<category>Grateful Dead</category>-->
156 <!--<category domain="http://www.fool.com/cusips">MSFT</category>-->
157 </category>
158 <comments>
159 <!--URL of a page for comments relating to the item.-->
160 <!--If present, it is the url of the comments page for the item.-->
161 <!--<comments>http://ekzemplo.com/entry/4403/comments</comments>-->
162 </comments>
163 <enclosure url="where the enclosure is located, The url must be an http url." length="how big it is in bytes" type="what its type is, a standard MIME type">
164 <!--Describes a media object that is attached to the item.-->
165 <!--<enclosure url="http://www.scripting.com/mp3s/weatherReportSuite.mp3" length="12216320" type="audio/mpeg" />-->
166 <!--It has three required attributes.-->
167 <!--url says where the enclosure is located,-->
168 <!--length says how big it is in bytes,-->
169 <!--and type says what its type is, a standard MIME type.-->
170 </enclosure>
171 <guid isPermaLink="optional, true(default) or false">
172 <!--A string that uniquely identifies the item.-->
173 <!--guid stands for globally unique identifier.-->
174 <!--It's a string that uniquely identifies the item.-->
175 <!--When present, an aggregator may choose to use this string to determine if an item is new.-->
176 <!--<guid>http://some.server.com/weblogItem3207</guid>-->
177 <!--If the guid element has an attribute named "isPermaLink" with a value of true, the reader may assume that it is a permalink to the item, that is, a url that can be opened in a Web browser, that points to the full item described by the <item> element. An example:-->
178 <!--<guid isPermaLink="true">http://inessential.com/2002/09/01.php#a2</guid>-->
179 </guid>
180 <pubDate>
181 <!--Indicates when the item was published.-->
182 <!--Its value is a date, indicating when the item was published.-->
183 <!--If it's a date in the future, aggregators may choose to not display the item until that date.-->
184 <!--<pubDate>Sun, 19 May 2002 15:21:36 GMT</pubDate>-->
185 </pubDate>
186 <source url="required attribute, url, which links to the XMLization of the source.">
187 <!--The RSS channel that the item came from.-->
188 <!--<source url="http://www.tomalak.org/links2.xml">Tomalak's Realm</source>-->
189 <!--The purpose of this element is to propagate credit for links, to publicize the sources of news items. It can be used in the Post command of an aggregator.-->
190 <!--should be generated automatically when forwarding an item from an aggregator to a weblog authoring tool.-->
191 </source>
192 <!--Optional Elements Of <item> End-->
193 </item>
194 </channel>
195</rss>
196
<?xml version="1.0" ?>2
<rss version="2.0">3
<channel>4
<!--Required Elements Begin-->5
<title>6
<!--The name of the channel.-->7
<!--It's how people refer to your service.-->8
<!--If you have an HTML website that contains the same information as your RSS file, the title of your channel should be the same as the title of your website.-->9
<!--[Example:GoUpstate.com News Headlines]-->10
</title>11
<link>12
<!--The URL to the HTML website corresponding to the channel.-->13
<!--[Example:http://www.goupstate.com/]-->14
</link>15
<description>16
<!--Phrase or sentence describing the channel.-->17
<!--[Example:The latest news from GoUpstate.com, a Spartanburg Herald-Journal Web site.]-->18
</description>19
<!--Required Elements End-->20
<!--Optional Elements Begin-->21
<language>22
<!--The language the channel is written in.-->23
<!--This allows aggregators to group all Italian language sites, for example, on a single page. A list of allowable values for this element, as provided by Netscape, is here.-->24
<!--You may also use values defined by the W3C.-->25
<!--[Example:en-us]-->26
</language>27
<copyright>28
<!--Copyright notice for content in the channel.-->29
<!--[Example:Copyright 2002, Spartanburg Herald-Journal]-->30
</copyright>31
<managingEditor>32
<!--Email address for person responsible for editorial content.-->33
<!--[Example:geo@herald.com (George Matesky)]-->34
</managingEditor>35
<webMaster>36
<!--Email address for person responsible for technical issues relating to channel.-->37
<!--[Example:betty@herald.com (Betty Guernsey)]-->38
</webMaster>39
<pubDate>40
<!--The publication date for the content in the channel.-->41
<!--For example, the New York Times publishes on a daily basis, the publication date flips once every 24 hours.-->42
<!--That's when the pubDate of the channel changes.-->43
<!--All date-times in RSS conform to the Date and Time Specification of RFC 822, with the exception that the year may be expressed with two characters or four characters (four preferred).-->44
<!--[Example:Sat, 07 Sep 2002 00:00:01 GMT]-->45
</pubDate>46
<lastBuildDate>47
<!--The last time the content of the channel changed.-->48
<!--[Example:Sat, 07 Sep 2002 09:42:31 GMT]-->49
</lastBuildDate>50
<category>51
<!--one or more categories that the channel belongs to.-->52
<!--Follows the same rules as the <item>-level category element.-->53
<!--[Example:<category>Newspapers</category>]-->54
</category>55
<generator>56
<!--A string indicating the program used to generate the channel.-->57
<!--[Example:MightyInHouse Content System v2.3]-->58
</generator>59
<docs>60
<!--A URL that points to the documentation for the format used in the RSS file.-->61
<!--It's probably a pointer to this page.-->62
<!--It's for people who might stumble across an RSS file on a Web server 25 years from now and wonder what it is.-->63
<!--[Example:http://blogs.law.harvard.edu/tech/rss]-->64
</docs>65
<cloud>66
<!--processes to register with a cloud to be notified of updates to the channel, implementing a lightweight publish-subscribe protocol for RSS feeds.-->67
<!--[Example:<cloud domain="rpc.sys.com" port="80" path="/RPC2" registerProcedure="pingMe" protocol="soap"/>]-->68
<!--It specifies a web service that supports the rssCloud interface which can be implemented in HTTP-POST, XML-RPC or SOAP 1.1.-->69
<!--Its purpose is to allow processes to register with a cloud to be notified of updates to the channel, implementing a lightweight publish-subscribe protocol for RSS feeds.-->70
<!--<cloud domain="rpc.sys.com" port="80" path="/RPC2" registerProcedure="myCloud.rssPleaseNotify" protocol="xml-rpc" />-->71
<!--In this example, to request notification on the channel it appears in, you would send an XML-RPC message to rpc.sys.com on port 80, with a path of /RPC2. The procedure to call is myCloud.rssPleaseNotify.-->72
</cloud>73
<ttl>74
<!--ttl stands for time to live.-->75
<!--It's a number of minutes that indicates how long a channel can be cached before refreshing from the source.-->76
<!--[Example:<ttl>60</ttl>]-->77
</ttl>78
<image>79
<!--Required Elements Of <image> Begin-->80
<!--a GIF, JPEG or PNG image that can be displayed with the channel.-->81
<url>82
<!--is the URL of a GIF, JPEG or PNG image that represents the channel.-->83
</url>84
<title>85
<!--describes the image, it's used in the ALT attribute of the HTML <img> tag when the channel is rendered in HTML.-->86
</title>87
<link>88
<!--is the URL of the site, when the channel is rendered, the image is a link to the site. (Note, in practice the image <title> and <link> should have the same value as the channel's <title> and <link>.-->89
</link>90
<!--Required Elements Of <image> End-->91
<!--Optional Elements Of <image> Begin-->92
<width>93
<!--Maximum value for width is 144, default value is 88.-->94
</width>95
<height>96
<!--Maximum value for height is 400, default value is 31.-->97
</height>98
<!--Optional Elements Of <image> End-->99
</image>100
<rating>101
<!--The PICS rating for the channel.]-->102
</rating>103
<textInput>104
<!--Specifies a text input box that can be displayed with the channel.-->105
<!--The purpose of the <textInput> element is something of a mystery.-->106
<!--You can use it to specify a search engine box. Or to allow a reader to provide feedback.-->107
<!--Most aggregators ignore it.-->108
<!--Required Elements Of <textInput> Begin-->109
<title>110
<!--The label of the Submit button in the text input area.-->111
</title>112
<description>113
<!--Explains the text input area.-->114
</description>115
<name>116
<!--The name of the text object in the text input area.-->117
</name>118
<link>119
<!--The URL of the CGI script that processes text input requests.-->120
</link>121
<!--Required Elements Of <textInput> End-->122
</textInput>123
<skipHours>124
<!--A hint for aggregators telling them which hours they can skip.-->125
</skipHours>126
<skipDays>127
<!--A hint for aggregators telling them which days they can skip.-->128
</skipDays>129
<!--Optional Elements End-->130
<item>131
<!--Optional Elements Of <item> Begin-->132
<title>133
<!--The title of the item.-->134
<!--[Example:Venice Film Festival Tries to Quit Sinking]-->135
</title>136
<link>137
<!--The URL of the item.-->138
<!--[Example:http://nytimes.com/2004/12/07FEST.html]-->139
</link>140
<description>141
<!--The item synopsis.-->142
<!--[Example:Some of the most heated chatter at the Venice Film Festival this week was about the way that the arrival of the stars at the Palazzo del Cinema was being staged.]-->143
</description>144
<author>145
<!--Email address of the author of the item.-->146
<!--It's the email address of the author of the item.-->147
<!--For newspapers and magazines syndicating via RSS, the author is the person who wrote the article that the <item> describes.-->148
<!--For collaborative weblogs, the author of the item might be different from the managing editor or webmaster.-->149
<!--For a weblog authored by a single individual it would make sense to omit the <author> element.-->150
<!--<author>lawyer@boyer.net (Lawyer Boyer)</author>-->151
</author>152
<category domain="optional, identifies a categorization taxonomy.">153
<!--Includes the item in one or more categories.-->154
<!--It has one optional attribute, domain, a string that identifies a categorization taxonomy.-->155
<!--<category>Grateful Dead</category>-->156
<!--<category domain="http://www.fool.com/cusips">MSFT</category>-->157
</category>158
<comments>159
<!--URL of a page for comments relating to the item.-->160
<!--If present, it is the url of the comments page for the item.-->161
<!--<comments>http://ekzemplo.com/entry/4403/comments</comments>-->162
</comments>163
<enclosure url="where the enclosure is located, The url must be an http url." length="how big it is in bytes" type="what its type is, a standard MIME type">164
<!--Describes a media object that is attached to the item.-->165
<!--<enclosure url="http://www.scripting.com/mp3s/weatherReportSuite.mp3" length="12216320" type="audio/mpeg" />-->166
<!--It has three required attributes.-->167
<!--url says where the enclosure is located,-->168
<!--length says how big it is in bytes,-->169
<!--and type says what its type is, a standard MIME type.-->170
</enclosure>171
<guid isPermaLink="optional, true(default) or false">172
<!--A string that uniquely identifies the item.-->173
<!--guid stands for globally unique identifier.-->174
<!--It's a string that uniquely identifies the item.-->175
<!--When present, an aggregator may choose to use this string to determine if an item is new.-->176
<!--<guid>http://some.server.com/weblogItem3207</guid>-->177
<!--If the guid element has an attribute named "isPermaLink" with a value of true, the reader may assume that it is a permalink to the item, that is, a url that can be opened in a Web browser, that points to the full item described by the <item> element. An example:-->178
<!--<guid isPermaLink="true">http://inessential.com/2002/09/01.php#a2</guid>-->179
</guid>180
<pubDate>181
<!--Indicates when the item was published.-->182
<!--Its value is a date, indicating when the item was published.-->183
<!--If it's a date in the future, aggregators may choose to not display the item until that date.-->184
<!--<pubDate>Sun, 19 May 2002 15:21:36 GMT</pubDate>-->185
</pubDate>186
<source url="required attribute, url, which links to the XMLization of the source.">187
<!--The RSS channel that the item came from.-->188
<!--<source url="http://www.tomalak.org/links2.xml">Tomalak's Realm</source>-->189
<!--The purpose of this element is to propagate credit for links, to publicize the sources of news items. It can be used in the Post command of an aggregator.-->190
<!--should be generated automatically when forwarding an item from an aggregator to a weblog authoring tool.-->191
</source>192
<!--Optional Elements Of <item> End-->193
</item>194
</channel>195
</rss>196
