Create a new, open design team that focuses strictly on the Atom protocol.





There are folks who are interested in helping with the Atom publishing protocol haven't been following the Atom mailing list due to the volume of messages and the dearth of protocol discussion. Creating a design team for just the protocol gives a more focused forum for those folks while letting the main mailing list spend more time on the seemingly-difficult parts of the format document.

Though the capabilities required are accurately listed in the charter, there has been a dearth of debate on many of the goals listed there. Sixapart is moving ahead with work in the protocol area (, but perhaps not in a manner identical to what the WG will choose. This group will focus on issues such as introspection, "categories", URIs that require extension elements, management of templates and users, and recommendations and requirements for implementations that wish to extend the Atom Publishing Protocol.


Create a "design team" for completing the list of all the actions that need to be in the Atom protocol. Note that there is no formal definition of design teams in the IETF, and they can be created under rules chosen by the WG chairs. For this design team, we propose [WWW]a mailing list open to anyone, whose only restriction is that the only initial topic for discussion is the needed actions for the Atom protocol.

The protocol design team will propose to the WG ways of closing all open issues in the Atom protocol document. The document editors will revise the protocol document based on what they hear from the WG.

We have started a ProtocolDataModel page to discuss the entities handled by the Atom protocol.


This group will work with the assumption that the primary interface to the Atom Publishing Protocol is REST with 4 verbs.