Re: Approaches to show/performance schedule information in RSS

Mark Fletcher wrote:

>There are no guarantees about how your data will be displayed. Different 
>aggregators do different things. Bloglines, for example, displays items 
>in date order, and allows the user to decide whether to show newest 
>first or oldest first. When we detect a change in an item, we update the 
>date on that item to when we received the change. One of the ideas of 
>aggregation is to let the user control how they view the content.
>
>
>  
>
Quite.

The best you can do, which probably equates to best practices, is be as 
specific, descriptive and accurate as possible. At this point in time 
that probably means using RSS 1.0 along with extensions as needed. There 
is no guarantee that all end users will support these, but some will, 
and it at least offers the /potential/ for richer feeds with more useful 
information.

Regarding the order, the formats have different interpretations - RSS 
1.0 does provide an explicit order (but doesn't really say what the 
significance of it is) and if I remember correctly the RSS 2.0 spec says 
absolutely nothing about order. So it's hardly surprising that different 
implementations work differently.

The Atom project should get this sorted out more usefully (it's already 
been discussed at length) but it will be a few months at least before 
that will be ready for widespread adoption.

Cheers,
Danny.

>
>  
>


-- 
----
Raw
http://dannyayers.com



 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/syndication/

<*> To unsubscribe from this group, send an email to:
     [email protected]

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/