| XML
About
Home
RSS
OPML
XML-RPC
SOAP
|
|
 |
|
RSS 0.93
Previous topic
|
Next topic
|
|
 RSS 0.93
started 4/20/2001; 9:15:09 AM - last post 3/6/2002; 9:13:49 AM
|
|
Dave Winer - RSS 0.93 
4/20/2001; 9:15:09 AM (reads: 191337, responses: 5)
|
|
Introduction 
RSS 0.93 is open for discussion.
If you have suggestions, ideas, needs, please discuss them here or on the associated mail list .
This format, when finalized, will be upward-compatible with RSS 0.92 and 0.91, meaning that a 0.92 or 0.91 source will also be a valid 0.93 source.
I expect a 60-day discussion period at which time, I will use my best judgement to decide which features are in. Without someone taking responsibility, there is never movement. We've learned this well in previous iterations of RSS. Forking is OK, but please use a different name. Thanks.
I'll take notes here, let's work together, keep RSS simple, but add features that people need to express the content that flows through RSS.
Changes
The 0.93 spec allows multiple <enclosures> per <item>. 0.92 allowed only a single enclosure.
Notes
All dates conform to the Date and Time Specification of RFC 822.
Simon Fell provides a use-case and discussion for <pubDate> and <expirationDate>.
The <source> sub-element of <item> can point to a permanent archive location for the item. This is a common feature of weblogs, allowing each item to be pointed to independently.
<pubDate> sub-element of <item>
<pubDate> is an optional sub-element of <item>.
Its value is a date, indicating when the item will become available.
<expirationDate> sub-element of <item>
<expirationDate> is an optional sub-element of <item>.
Its value is a date, indicating when the item is no longer available.
|
|
Julian Bond - item.link and item.source
5/2/2001; 4:03:46 AM (reads: 29841, responses: 0)
|
|
|
I don't think that this should be required but I think it should be recommended that <link> is included for all items in any RSS feed. It should point at the URL for the web based page of which the item is an abstract. This simply reflects common usage. Sites that don't do this should be encouraged to do it.
<source> should then be used to cite the source that the item was developed from.
eg. I write a story which is a comment about a Wired article. <link> should point at my story, <source> should point at the Wired article.
Going down this route suggests that each <item> should be allowed to have multiple <source> with one for each link in the page at <link>
|
|
Baljit Grewal - Re: RSS 0.93
6/1/2001; 8:38:23 PM (reads: 33606, responses: 0)
|
|
|
Is it possible to make a sub element called Target so that people have a choice to open a Link in a new window or on the same window.
Regards,
Baljit Grewal
|
|
|
|
|
I could use several sub-elements to <item>. I currently use all of these, but some of this will change.
<date_posted> - self explanatory
<who_posted> - my site technically allows more than one person to post a news item
<authorized> - is the poster authorized? this tag may fall away. I'm not sure of its importance in the current version of my site
<urgency> - the urgency or importance of the news item
<top_comments> - users can post comments associated with the news item. These comments show at the top of the page, in the lead in portion of the daily news. Because of this, top_comments are used to call attention to a story than may not otherwise be noticed.
Hope I'm not nuts here.
Best regards,
Richard
http://broznews.com/
|
|
|
|
|
Is it just me, or does RFC 822 seem atrociously ugly compared to ISO 8601?
|
|
|
|
