Toru,
can zou provide examples of where the current draft is underspecified
(IOW: what *cannot* be done with it)? Examples would help to spot
where people misunderstand the draft or what needs to be fixed.
On Jul 7, 2006, at 7:32 AM, Toru Marumoto wrote:
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,
What do you mean by that?
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.
Jan
