I am not against the hierarchical structure (anyway flat structure is hierarchical structure in a special form). However, the question is: How and how much would the server side synidcation service (e.g. bloglines, MyYahoo!) and the desktop aggregators add value with such hierarchy structure information in both feed and entry?
Press further, how do they handle when the feed owner changes the hierarchy structure (by renaming/moving/inserting/removing part of the parth?)
I strongly suggest that we come out a list of use cases and that would make the discussion and decision much easier.
e.g. will the autodiscovery prompts user the available feeds of different categories, or allow user choose which categories to subscribe?
Somehow I feel the tags used by flickr and delicious is good enough.
Yining
Tim Bray wrote:
Somehow, we don't seem to have any category element in the format-draft. Huh? It's in RSS2 and it's widely deployed, although it hasn't been all that useful. Also I note that the protocol design team is worrying about querying and defining categories. I don't see anything wrong with RSS2's category element, so I've proposed something along the same lines: http://www.intertwingly.net/wiki/pie/PaceCategoryElement -Tim
