Tim Bray wrote:
<co-chair-mode>
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. Would like to see an evolution of the current workspace model
defined in a separate I-D.
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. See above.
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. The fact that the definition is separated out to a separate draft is
good, but I'm not convinced on the format and don't like the idea of a
normative reference to APPO.
- James
