Dave Winer wrote:
Mark and Sam, the two applications are not related. Yahoo wants a way to present massive numbers of different feeds. Sam is interested in presenting different flavors of the same feed. Maybe there's a need for the latter, I don't know. Personally I find it's usually far more information than I want, and I don't bother subscribing at all. I do subscribe to Zawodny though. Must've been before he offered all those choices.
That was merely one use case. One that I previously discussed with Jeremy, so I am confused as to how it is now declared to be unrelated.
In any case, here is another use case:http://blogs.law.harvard.edu/myPublicFeeds.opml currently contains a list of 302 feeds. That's a lot of information. When presented as an exhaustive list, I imagine that many people will not bother.
In order to help people make informed choices, what additional information about each blog should be captured in the list, or made available on demand? Examples of such information from Sunday's brainstorming session can be found at:
http://www.intertwingly.net/wiki/fdml/DataModelRequirementsPresuming that it is related, the use case would be that the aggregator could provide a search interface over the data that is provided to allow the user to scope down the list to something more managable. The user would then select the feed(s) to subscribe to from the resulting list.
- Sam Ruby