On 7/6/06, Elias Torres <[EMAIL PROTECTED]> wrote:
[snip]
One of my goals is to show examples of Atom being used for everything but a blogging system. I am certain your main target is to support blogging clients and I am not really sure how many in the core WG are seeing this with their Atom-Pub-is-more-than-just-for-blogs lenses. Although there are many "Legacy applications", I think it would be a short-sided to ignore the next wave of applications that will be built using APP that might need a tiny bit more specified protocol, i.e. collection management, better introspection document, versioning, etc.
IMHO, a lot of stuff is not specified in the current APP spec, even for a blogging. (i.e. a standard error description format, better synchronization, etc) In fact, I'm beginning to think that the APP is just a basic prototype of a protocol or a web api. In order to have a fully functional and interoperable protocol, you need to roll out your own based on the APP, like GData API. So, everything outside of the spec will be depend on some inventions from variety of implementations in the wild. I'm just not sure that's good or not. Most likely, clients will have the burden of getting things work across different implementations. "All the blog providers seems to interpret these APIs a bit different so there kinks we're still working out." says a person at Microsoft. http://blogs.msdn.com/joe_friend/archive/2006/05/12/595963.aspx The more you specify the better functionality and interop. But that also limits the other use cases of APP we might come up in the future. I think WG is working hard to keep thw balance between the two. Well, anyway that was what I felt after hearing lots of 'not in the "core"' and "just an optimization" :-). cheers
Just my 2c. -Elias
marumoto
