On 11/6/05, Eric Scheid <[EMAIL PROTECTED]> wrote: > > On 7/11/05 1:15 PM, "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 for now but I have a working pace mentioned below > -1. > > > 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 > -1. > > > 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 > -1. > > 4. Put in the spec just enough to help a client *find* various introspection > documents, without specifying the content/format of those introspection > documents. Discovery, not format. > What if we can just find feeds and feeds tell us what we need to know? rel="feed" or something. Feeds can point to feeds. Then feeds point us to where to post things. Home page +------>Feed +------>Feed +------>Feed +----> Post Media +----> Post Entries I am 80% through writing a big pace that includes this. I am probably stepping on autodisco, though. - Luke
