I like this approach since it reuses app:category and enables both fixed inline/outofline and internal/external categories, but have a couple questions.
What is the mime-type of this app:categories document? If it is application/atom+xml then we will have three possible types of documents that all use the same media-type: feeds, entries and categories. Of course, if you don't use application/atom+xml then it will look odd since the document element in is the same namespace. Do we need to define what it means if app:categories appears in an atom feed or entry? -joe On 6/7/06, Tim Bray <[EMAIL PROTECTED]> wrote:
At http://www.intertwingly.net/wiki/pie/PaceAPPCategories Based on PaceCategoryListing2. In an introspection document, you either have an href= or you don't. If not, you contain atom:category elements directly. If you do, it has to point to a Categories document, whose root is <app:categories> with <atom:category> children. The only thing that's not obvious is that <app:categories>, when it's the root of a Categories doc, can have a @scheme attribute to provide a default, if you want a couple of hundred categories and not to provide the [EMAIL PROTECTED] for all of them. This seems to be about the minimum I can think of that would give APP category listing, without trying to stretch too far or solve the whole problem. -Tim
-- Joe Gregorio http://bitworking.org
