Tim Bray wrote:
<co-chair-mode>
There are a flurry of Paces, and there is enough camera-ready spec
text supporting all the options that we believe that they are well-
understood by the group.
The following seem like plausible options for introspection:
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 (doesn't support the simple compound XHTML/cat picture use case)
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 (seems like overkill to me, but will get the job done)
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.5 (would also get the job done)