Re: AtomAPI Rev 08

[Ken MacLeod <ken@xxxxxxxxxxxxxxxx>]

Steve Jenson <sjenson@xxxxxxxxxx> writes:

> On Tue Dec 02 13:53:06 PST 2003, Dare Obasanjo <kpako@xxxxxxxxx> wrote:
> > PS: What is the process for getting new methods added to the API?
> > I'd like to see a methods for subscription harmonization in the
> > ATOM API.
> 
> I think the process seems to be: 1) Make a case and write a
> proposal, 2) see how many people disagree specifically with the
> proposal. 3) Fix the proposal if possible.

That's the process to-date.

Regarding this specific scope, I'd suggest that "subscription
harmonization" is an "API module" and not something that should go in
the core Atom API.

A little bit of from-the-side-view: If the "Atom API spec" is the
"common practices for using the Web Architecture for accessing
weblogs", then it should always be straightforward what the practice
is for adding a new URI or URI-space (such as a subscription): define
the URIs, define the access to those URIs, define the formats.

Subscription harmonization, in that view, is "just another URI", that
can be PUT/GET/DELETEd, and in a given format.  The doc for that is an
"API module".

Regarding subscription harmonization, very specifically, it seems much
more an aggregator-side feature than the weblog-publisher-side feature
that has been the focus of the Atom API.  Subscription harmonization
is about saving aggregator state on a publicly accessible server, not
about a particular weblog, no?

  -- Ken