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.

The 0.93 spec allows multiple <enclosures> per <item>. 0.92 allowed only a single enclosure.

• 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> is an optional sub-element of <item>.

Its value is a date, indicating when the item will become available.

<expirationDate> is an optional sub-element of <item>.

Its value is a date, indicating when the item is no longer available.