On Nov 6, 2005, at 6:15 PM, 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. Introspection is an obvious thing where we can easily hit an
80/20 point, and it's a major interoperability value add if an
implementor gets introspection guidance right there in the APP spec
without having to go elsewhere.
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
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, assuming it gets rolled into the APP draft.
I can live with either of these introspection formats; but am unhappy
with punting the problem. -Tim
