>> http://www.intertwingly.net/wiki/pie/PaceCategoryListing2
>
> +0, although I'd be interested in seeing if this could be done with
> without introducing new elements, couldn't you just happen to have a
> collection all of whose entries are atom:categories?
>
Several questions:
1. What's the representation you get back from a GET on the category
collection? What's the representation you get back from a GET on the
category member uri?
If it's an Atom feed,
* what do the entries look like?
* can the feed be paged?
* do the entries have to be ordered by atom:updated or can they
be listed alphabetically (or whatever) by the category term?
2. Would the spec include how to manage the collection of categories?
(e.g., create, update, delete) What if the categorization scheme is
hierarchical?
3. If you have a workspace that contains two entry collections, a media
collection, and a categories collection, can it be assumed that the
categories apply to both of the entry collections and the media
collection? that is, can each collection in a workspace have it's own
categories? If so, how are those represented using the category
collection approach?
4. How does one specify whether or not the categories are a fixed set?
open set (e.g. tags)?
- James
