On Jul 6, 2006, at 10:32 PM, Toru Marumoto wrote:
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.
This is an important point. Personally, I am OK with where we are
now: once you've got your collections set up and authorization
infrastructure in place, the APP lets you do CRUD operations on them
in a way that's pretty easy to implement. The APP doesn't touch a
lot of system management & administration tasks, and I'm OK with
that, because we don't have enough industry good-practice consensus
on what's important and I think that if we tried to standardize it
we'd have to invent it first, in advance of experience, and I don't
want to go there.
However, I still do see a couple of missing pieces:
- There really should be a standard way to retrieve a list of
available categories.
- To the extent that we can provide some hints and support around
authentication, that would be a plus, so that a dumb client that can
do HTTPS+basic, *or* next year's best choice, has a chance of
figuring out which the server wants and switching that in automatically.
-Tim
