From: Kevin <ke...@dr...> - 2005-11-28 17:23:04
|
Carlos Kozuszko wrote: >And what about tagging the feeds instead of individual items ? Or > maybe tags for both could be implemented. I thought that's what categories were for. (grouping of feeds) We could support both, but a clear definition of what a tag is and what a category is should be made. Here is my crazy brainstorming of what a tag could be. 1. tag attach to item 2. tag attach to feed 3. tag attach to tag 4. tag attach to category 5. tag attach to search result So, I've partially implemented #1. Which of the others listed really represent what a tag *IS*? I thought about implementing tags as only #5= . Then, the tag is stored as a list of search criteria. The nice thing about doing this is it allows the user create a tag using any of the abov= e criteria, at the same time. Tags could be made this flexible. Do we nee= d them to be? Am I completely off base on what a tag is supposed to accomplish? > I've already found a use for categories, lets say im importing a > opml file (as I actually do), the tree-like structure for the categorie= s > could/should be preserved when adding those feeds to our database. > Likewise, when we export a opml file the categories should be > reflected in that file. How many levels should the category tree support? Can a category contain feeds and other categories at the same time? |