On 8/7/06 4:22 AM, "Tim Bray" <[EMAIL PROTECTED]> wrote: > - There really should be a standard way to retrieve a list of > available categories.
In absence of any special magic, I'll be doing this by maintaining a collection whose entries contain one category each within their atom:content elements. Sure, there's overhead, but it does give me all the room I'll need for managing my categories as first class objects. I'll be able to CRUD my collections, as well as maintain housekeeping metadata (eg. mark some categories as draft, establish a hierarchy via James's Threading spec, keep on hand a brief description/summary, identify which of my team created/modified it etc etc). The beauty of it is that I can use the same generalised method for maintaining a list of atom:persons too, or even feeds for that matter. The only bit of invention needed is some way to indicate in the introspection document which feeds contain the categories for a given workspace (as distinct from real atom entries, or even atom:persons for that matter, since app:accept="application/atom+xml" might be a tad confusing). e.
