On 6/20/06, Michael Wechner <[EMAIL PROTECTED]> wrote:
James M Snell wrote: > We have lots of use cases that don't fit the "post to a blog" model. > Any view that APP is just about blog editing is extremely shortsighted. :-) > well, this is the perception. If APP is really more than just about blog editing, then he perception needs to be changed.
Like a lot of people I've been watching APP develop, hoping it will be a prototype for other kinds of application domains. Introspection, PUT of resources and potential identifier conficts -- the way APP resolves these issues are going to inform future application protocols. But it's good that APP focused on "publishing" and blogs. That's how it scared up the PUT/identifier conflict issue, and media collections/entries, or whatever. (Actually, I haven't really noticed any use cases discussed in this WG that weren't about blogs. "Cat pictures" seems to be the most popular case). So while I would encourage people to think of APP as a good prototype for other application domains it might be that a database protocol is different enough from blog publishing it deserves its own protocol. And after drillling down on issues in that domain we'll figure out the common ancestor protocol for all domains. Hugh
