Atom Project: W3C Working Group


Mission Statement

The Working Group will be chartered to define Atom, a feed format for representing and a protocol for editing Web resources such as Weblogs, online journals, Wikis, and similar content. The feed format enables syndication; that is, provision of a channel of information by representing multiple resources in a single document. The editing protocol enables agents to interact with resources by nominating a way of using existing Web standards in a pattern.

Scope And Work Items

Architectural Constraints

Atom consists of:

The format must be able to represent:

The editing protocol must enable:

The Working Group will use experience gained with syndication format as the basis for a standards-track document specifying the model, syntax, and feed format. The feed format will be used as the basis of work on a standards-track document specifying the editing protocol. If other submissions are made to the Working Group under terms accepted by the W3C, the working group may consider them as alternatives, inputs or additional materials for the community based upon their merits.

Technical Quality and Interoperability

The Working Group will also take steps to ensure interoperability, by:

The Working Group's primary focus will be on delivering an interoperable syntax and corresponding API; it is expected that all but the most basic, generic metadata and functions will be accommodated through extensions, rather than in the core documents.

Tracking and Maintenance Items

(Not Optional - Björn Höhrmann comment)

(Optional - might be removed)


This group will commence in July 2004 and will terminate in July 2006


The Working Group will follow the W3C Recommendation Track to produce:

Legal Data

This Working Group operates under the W3C Patent Policy (5 February 2004 Version). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis.

Relationship to other forums


Chairs or Co-Chairs

The chair of the group will be @@. (Director's decision) The team contact will be @@.

The Working Group will utilize a public mailing list archived at and mirrored on the W3C Web site at @@@@. The public mailing list, with its wide audience, exists to promote openness and interoperability, and is the preferred channel of communication.

The Working Group will have a home page that records the history of the group, provides access to the archives, meeting minutes, updated schedule of deliverables, and relevant documents and resources. The page will be available to the public and will be maintained by the Chair in collaboration with the W3C Team contact.

In the event that consensus fails, a vote will be taken based on participants in good standing as described in the Process Document.

Member Representatives

Requirements for meeting attendance and timely response are described in the Process document. Participation (meetings, reviewing and writing drafts) is expected to consume time equal to 1 day per week for a period of one year.

Invited Experts

As decided on a case by case basis, chair and team contact decide on the participation of invited experts to the Working Group. For the duration of their participation, invited experts are encouraged to adopt the same requirements for meeting attendance and timely response as are required of W3C Members.

Team Contact

W3C Team will ensure that the mailing lists and Group page are adequately maintained and that public Working Drafts are made available on the Technical Reports page. W3C Team will post minutes of teleconferences to the Group mailing list and to the Group page. W3C Team are expected to adopt the same requirements for meeting attendance and timely response as are required of Working Group members.

Public Participation

Public participation is the norm, and the group will process and respond comments from all participants. The standard will be consensus, as defined in the W3C Process Document.


Karl, I would suggest that XHTML 2.0, i18n, XForms and RDF should also be listed for the purposes of working group coordination in a W3C Charter. -- BryanThompson