Monday, November 7, 2005, 2:15:59 AM, Tim Bray 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 - we need something. Although, if we wanted to split this work off into a separate draft, I'd be ok with that. > 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.5 - The approach is fine. If we decide on a need for nested collections, then I suppose we could add them. > 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 +0 - APPO is a custom format, but not custom for Atom; it is a generic outlining format with no dependencies on Atom. It looks pretty good but I think that we should use a unique MIME type for APPO Atom Introspection documents rather than application/outline+xml, for the same general reasons that we don't just use application/xml for everything. MIME dispatch etc. Fix that, and I'll give it +0.5 - that's about as excited as I can get about the choice of format. -- Dave
