Antone Roundy wrote:
Indeed, overriding does not work, say I have categories of "Java" and "Gadgets", and another "Geek" which is conceptualy at the higher level than the first two. It's very reasonable to have a "Geek" feed that contains all entries of "Java" and "Gadgets" and even entries of just "Tech".
On Tuesday, November 9, 2004, at 12:54 PM, Zhang Yining wrote:
Does the absence of category construct for entry imply the category of the entry defaults to that of the feed? I guess not. Need to clarify this bit.==== 5.13 The "atom:category" element ====
A Category Construct identifying a category to which the entry is associated. atom:entry elements MAY contain any number of atom:category elements.
My first reaction is that entry/category would need to override feed/category to avoid weirdness when an off-topic entry gets posted. If there's an entry/category, override, otherwise inherit. That could lead to duplication though, if, for example, the feed/category was "programming" and the entry wanted to be about both "programming" and "linux". Perhaps that would be the uglier situation (more common?). So maybe inherit always, and entry/category adds to the category list. Hmm.
For inheritance, what if I would like to subcribe a feed of two categories, "Perl" and "XML", and one entry of category "C#" and "XML", which feed category does this entry inherit from? And I guess we can't really call that inheritance ;-)
Cheers,
Yining
