Re: I-D ACTION:draft-ietf-atompub-protocol-14.txt

["A. Pagaltzis" <pagaltzis@xxxxxx>]

* Roy T. Fielding <fielding@xxxxxxxx> [2007-03-18 00:00]:
> It is only when we talk about specific applications of AtomPP,
> such as an authoring interface to a corporate blog, that we can
> say anything about the anticipated state change on the server.
> SUCH INFORMATION DOES NOT NEED TO BE IN THE PROTOCOL
> SPECIFICATION.
>
> Maybe someone needs to write an application guide for
> transparent authoring via Atom, and maybe that guide should be
> very prescriptive in terms of what content needs to be
> preserved on any given PUT in order to be acceptable by users
> who are expecting transparent behavior. Maybe it will be the
> topic of several books. It is not, however, the only
> application of AtomPP, and therefore is not part of the AtomPP
> standard requirements. At best it could be described in an
> appendix.
>
> Hence, no spec changes are necessary, the sky is not falling,
> and AtomPP implementations will interoperate just fine even
> when the purpose of the server was completely unanticipated by
> the person implementing the client. Serendipity, by design.

Thanks. This is precisely my understanding as well.

Regards,
-- 
Aristotle Pagaltzis // <http://plasmasturm.org/>