On 11/6/05 6:15 PM, "Tim Bray" <[EMAIL PROTECTED]> wrote: > 1. Do nothing. The APP is limited to talking about how you traverse, > add entries to, and delete from, collections, saying nothing about > how you find them.
-1 > 2. draft-protocol-06 approach: see http://bitworking.org/projects/ > atom/draft-ietf-atompub-protocol-06.html#appdocs - a custom XML > vocabulary that describes collections and their capabilities. -0 because I think it would mostly work even though it seems overly complex and lacks nesting. > 3. PaceAppOutline - another custom XML vocabulary which supports > arbitrary nesting of collections, for which there are a couple of > plausible use cases. See http://www.intertwingly.net/wiki/pie/ > PaceUseAppOutlines +1 because nesting is important (see, for instance, nested categories in WordPress) and because the format is simple. (It's OPML-like, which means lots of people already have code they could apply to this. Which also means people will "get it" quickly, which will help with adoption.) -Brent
