On 11/6/05, 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. I like my format best, and I don't care if it's in the spec. > 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. -1. Known to suck (I've coded against it, and share part of the blame for it). > 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 Also OK. +1 to the pace as written. -- Robert Sayre "I would have written a shorter letter, but I did not have the time."
