5023
PROPOSED STANDARD
The Atom Publishing Protocol
Authors: J. Gregorio, B. de hOra
Date: October 2007
Area: app
Working Group: atompub
Stream: IETF
Updated by:
RFC 8996
Abstract
The Atom Publishing Protocol (AtomPub) is an application-level protocol for publishing and editing Web resources. The protocol is based on HTTP transfer of Atom-formatted representations. The Atom format is documented in the Atom Syndication Format. [STANDARDS-TRACK]
RFC 5023
PROPOSED STANDARD
Updated by: 8996 Errata Exist
Network Working Group J. Gregorio, Ed.
Request for Comments: 5023 Google
Category: Standards Track B. de hOra, Ed.
NewBay Software
October 2007
<span class="h1">The Atom Publishing Protocol</span>
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Abstract
The Atom Publishing Protocol (AtomPub) is an application-level
protocol for publishing and editing Web resources. The protocol is
based on HTTP transfer of Atom-formatted representations. The Atom
format is documented in the Atom Syndication Format.
<span class="grey">Gregorio & de hOra Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a>
<a href="#section-2">2</a>. Notational Conventions ..........................................<a href="#page-4">4</a>
<a href="#section-2.1">2.1</a>. XML-Related Conventions ....................................<a href="#page-4">4</a>
<a href="#section-2.1.1">2.1.1</a>. Referring to Information Items ......................<a href="#page-4">4</a>
<a href="#section-2.1.2">2.1.2</a>. RELAX NG Schema .....................................<a href="#page-4">4</a>
<a href="#section-2.1.3">2.1.3</a>. Use of "xml:base" and "xml:lang" ....................<a href="#page-5">5</a>
<a href="#section-3">3</a>. Terminology .....................................................<a href="#page-5">5</a>
<a href="#section-4">4</a>. Protocol Model ..................................................<a href="#page-6">6</a>
<a href="#section-4.1">4.1</a>. Identity and Naming ........................................<a href="#page-6">6</a>
<a href="#section-4.2">4.2</a>. Documents and Resource Classification ......................<a href="#page-7">7</a>
<a href="#section-4.3">4.3</a>. Control and Publishing .....................................<a href="#page-8">8</a>
<a href="#section-4.4">4.4</a>. Client Implementation Considerations .......................<a href="#page-9">9</a>
<a href="#section-5">5</a>. Protocol Operations .............................................<a href="#page-9">9</a>
<a href="#section-5.1">5.1</a>. Retrieving a Service Document .............................<a href="#page-10">10</a>
<a href="#section-5.2">5.2</a>. Listing Collection Members ................................<a href="#page-10">10</a>
<a href="#section-5.3">5.3</a>. Creating a Resource .......................................<a href="#page-11">11</a>
<a href="#section-5.4">5.4</a>. Editing a Resource ........................................<a href="#page-11">11</a>
<a href="#section-5.4.1">5.4.1</a>. Retrieving a Resource ..............................<a href="#page-11">11</a>
<a href="#section-5.4.2">5.4.2</a>. Editing a Resource .................................<a href="#page-12">12</a>
<a href="#section-5.4.3">5.4.3</a>. Deleting a Resource ................................<a href="#page-12">12</a>
<a href="#section-5.5">5.5</a>. Use of HTTP Response Codes ................................<a href="#page-12">12</a>
<a href="#section-6">6</a>. Protocol Documents .............................................<a href="#page-13">13</a>
<a href="#section-6.1">6.1</a>. Document Types ............................................<a href="#page-13">13</a>
<a href="#section-6.2">6.2</a>. Document Extensibility ....................................<a href="#page-13">13</a>
<a href="#section-7">7</a>. Category Documents .............................................<a href="#page-14">14</a>
<a href="#section-7.1">7.1</a>. Example ...................................................<a href="#page-14">14</a>
<a href="#section-7.2">7.2</a>. Element Definitions .......................................<a href="#page-14">14</a>
<a href="#section-7.2.1">7.2.1</a>. The "app:categories" Element .......................<a href="#page-14">14</a>
<a href="#section-8">8</a>. Service Documents ..............................................<a href="#page-15">15</a>
<a href="#section-8.1">8.1</a>. Workspaces ................................................<a href="#page-16">16</a>
<a href="#section-8.2">8.2</a>. Example ...................................................<a href="#page-16">16</a>
<a href="#section-8.3">8.3</a>. Element Definitions .......................................<a href="#page-17">17</a>
<a href="#section-8.3.1">8.3.1</a>. The "app:service" Element ..........................<a href="#page-17">17</a>
<a href="#section-8.3.2">8.3.2</a>. The "app:workspace" Element ........................<a href="#page-18">18</a>
<a href="#section-8.3.3">8.3.3</a>. The "app:collection" Element .......................<a href="#page-18">18</a>
<a href="#section-8.3.4">8.3.4</a>. The "app:accept" Element ...........................<a href="#page-19">19</a>
<a href="#section-8.3.5">8.3.5</a>. Usage in Atom Feed Documents .......................<a href="#page-19">19</a>
<a href="#section-8.3.6">8.3.6</a>. The "app:categories" Element .......................<a href="#page-20">20</a>
<a href="#section-9">9</a>. Creating and Editing Resources .................................<a href="#page-20">20</a>
<a href="#section-9.1">9.1</a>. Member URIs ...............................................<a href="#page-20">20</a>
<a href="#section-9.2">9.2</a>. Creating Resources with POST ..............................<a href="#page-20">20</a>
<a href="#section-9.2.1">9.2.1</a>. Example ............................................<a href="#page-21">21</a>
<a href="#section-9.3">9.3</a>. Editing Resources with PUT ................................<a href="#page-22">22</a>
<a href="#section-9.4">9.4</a>. Deleting Resources with DELETE ............................<a href="#page-22">22</a>
<a href="#section-9.5">9.5</a>. Caching and Entity Tags ...................................<a href="#page-22">22</a>
<a href="#section-9.5.1">9.5.1</a>. Example ............................................<a href="#page-23">23</a>
<span class="grey">Gregorio & de hOra Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<a href="#section-9.6">9.6</a>. Media Resources and Media Link Entries ....................<a href="#page-25">25</a>
<a href="#section-9.6.1">9.6.1</a>. Examples ...........................................<a href="#page-26">26</a>
<a href="#section-9.7">9.7</a>. The Slug Header ...........................................<a href="#page-30">30</a>
<a href="#section-9.7.1">9.7.1</a>. Slug Header Syntax .................................<a href="#page-31">31</a>
<a href="#section-9.7.2">9.7.2</a>. Example ............................................<a href="#page-31">31</a>
<a href="#section-10">10</a>. Listing Collections ...........................................<a href="#page-32">32</a>
<a href="#section-10.1">10.1</a>. Collection Partial Lists .................................<a href="#page-32">32</a>
<a href="#section-10.2">10.2</a>. The "app:edited" Element .................................<a href="#page-33">33</a>
<a href="#section-11">11</a>. Atom Format Link Relation Extensions ..........................<a href="#page-34">34</a>
<a href="#section-11.1">11.1</a>. The "edit" Link Relation .................................<a href="#page-34">34</a>
<a href="#section-11.2">11.2</a>. The "edit-media" Link Relation ...........................<a href="#page-34">34</a>
<a href="#section-12">12</a>. The Atom Format Type Parameter ................................<a href="#page-34">34</a>
<a href="#section-12.1">12.1</a>. The "type" parameter .....................................<a href="#page-34">34</a>
<a href="#section-12.1.1">12.1.1</a>. Conformance .......................................<a href="#page-35">35</a>
<a href="#section-13">13</a>. Atom Publishing Controls ......................................<a href="#page-35">35</a>
<a href="#section-13.1">13.1</a>. The "app:control" Element ................................<a href="#page-35">35</a>
<a href="#section-13.1.1">13.1.1</a>. The "app:draft" Element ...........................<a href="#page-36">36</a>
<a href="#section-14">14</a>. Securing the Atom Publishing Protocol .........................<a href="#page-36">36</a>
<a href="#section-15">15</a>. Security Considerations .......................................<a href="#page-37">37</a>
<a href="#section-15.1">15.1</a>. Denial of Service ........................................<a href="#page-37">37</a>
<a href="#section-15.2">15.2</a>. Replay Attacks ...........................................<a href="#page-37">37</a>
<a href="#section-15.3">15.3</a>. Spoofing Attacks .........................................<a href="#page-37">37</a>
<a href="#section-15.4">15.4</a>. Linked Resources .........................................<a href="#page-38">38</a>
<a href="#section-15.5">15.5</a>. Digital Signatures and Encryption ........................<a href="#page-38">38</a>
<a href="#section-15.6">15.6</a>. URIs and IRIs ............................................<a href="#page-38">38</a>
<a href="#section-15.7">15.7</a>. Code Injection and Cross Site Scripting ..................<a href="#page-39">39</a>
<a href="#section-16">16</a>. IANA Considerations ...........................................<a href="#page-39">39</a>
<a href="#section-16.1">16.1</a>. Content-Type Registration for 'application/atomcat+xml' ..39
<a href="#section-16.2">16.2</a>. Content-Type Registration for 'application/atomsvc+xml' ..40
<a href="#section-16.3">16.3</a>. Header Field Registration for 'SLUG' .....................<a href="#page-42">42</a>
<a href="#section-16.4">16.4</a>. The Link Relation Registration "edit" ....................<a href="#page-42">42</a>
<a href="#section-16.5">16.5</a>. The Link Relation Registration "edit-media" ..............<a href="#page-42">42</a>
<a href="#section-16.6">16.6</a>. The Atom Format Media Type Parameter .....................<a href="#page-43">43</a>
<a href="#section-17">17</a>. References ....................................................<a href="#page-43">43</a>
<a href="#section-17.1">17.1</a>. Normative References .....................................<a href="#page-43">43</a>
<a href="#section-17.2">17.2</a>. Informative References ...................................<a href="#page-44">44</a>
<a href="#appendix-A">Appendix A</a>. Contributors ..........................................<a href="#page-46">46</a>
<a href="#appendix-B">Appendix B</a>. RELAX NG Compact Schema ...............................<a href="#page-46">46</a>
<span class="grey">Gregorio & de hOra Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Atom Publishing Protocol is an application-level protocol for
publishing and editing Web Resources using HTTP [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>] and XML 1.0
[<a href="#ref-REC-xml" title=""Extensible Markup Language (XML) 1.0 (Fourth Edition)"">REC-xml</a>]. The protocol supports the creation of Web Resources and
provides facilities for:
o Collections: Sets of Resources, which can be retrieved in whole or
in part.
o Services: Discovery and description of Collections.
o Editing: Creating, editing, and deleting Resources.
The Atom Publishing Protocol is different from many contemporary
protocols in that the server is given wide latitude in processing
requests from clients. See <a href="#section-4.4">Section 4.4</a> for more details.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Notational Conventions</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. XML-Related Conventions</span>
<span class="h4"><a class="selflink" id="section-2.1.1" href="#section-2.1.1">2.1.1</a>. Referring to Information Items</span>
Atom Protocol Document formats are specified in terms of the XML
Information Set [<a href="#ref-REC-xml-infoset">REC-xml-infoset</a>], serialized as XML 1.0 [<a href="#ref-REC-xml" title=""Extensible Markup Language (XML) 1.0 (Fourth Edition)"">REC-xml</a>].
The Infoset terms "Element Information Item" and "Attribute
Information Item" are shortened to "element" and "attribute"
respectively. Therefore, when this specification uses the term
"element", it is referring to an Element Information Item, and when
it uses the term "attribute", it is referring to an Attribute
Information Item.
<span class="h4"><a class="selflink" id="section-2.1.2" href="#section-2.1.2">2.1.2</a>. RELAX NG Schema</span>
Some sections of this specification are illustrated with fragments of
a non-normative RELAX NG Compact schema [<a href="#ref-RNC" title=""RELAX NG Compact Syntax"">RNC</a>]. However, the text of
this specification provides the definition of conformance. Complete
schemas appear in <a href="#appendix-B">Appendix B</a>.
<span class="grey">Gregorio & de hOra Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h4"><a class="selflink" id="section-2.1.3" href="#section-2.1.3">2.1.3</a>. Use of "xml:base" and "xml:lang"</span>
XML elements defined by this specification MAY have an "xml:base"
attribute [<a href="#ref-REC-xmlbase">REC-xmlbase</a>]. When xml:base is used, it serves the
function described in <a href="#section-5.1.1">Section 5.1.1</a> of URI Generic Syntax [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>],
by establishing the base URI (or IRI, Internationalized Resource
Identifier [<a href="./rfc3987" title=""Internationalized Resource Identifiers (IRIs)"">RFC3987</a>]) for resolving relative references found within
the scope of the "xml:base" attribute.
Any element defined by this specification MAY have an "xml:lang"
attribute, whose content indicates the natural language for the
element and its descendants. Requirements regarding the content and
interpretation of "xml:lang" are specified in <a href="#section-2.12">Section 2.12</a> of XML 1.0
[<a href="#ref-REC-xml" title=""Extensible Markup Language (XML) 1.0 (Fourth Edition)"">REC-xml</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Terminology</span>
For convenience, this protocol can be referred to as the "Atom
Protocol" or "AtomPub". The following terminology is used by this
specification:
o URI - A Uniform Resource Identifier as defined in [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>]. In
this specification, the phrase "the URI of a document" is
shorthand for "a URI which, when dereferenced, is expected to
produce that document as a representation".
o IRI - An Internationalized Resource Identifier as defined in
[<a href="./rfc3987" title=""Internationalized Resource Identifiers (IRIs)"">RFC3987</a>]. Before an IRI found in a document is used by HTTP, the
IRI is first converted to a URI. See <a href="#section-4.1">Section 4.1</a>.
o Resource - A network-accessible data object or service identified
by an IRI, as defined in [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>]. See [<a href="#ref-REC-webarch">REC-webarch</a>] for further
discussion on Resources.
o relation (or "relation of") - Refers to the "rel" attribute value
of an atom:link element.
o Representation - An entity included with a request or response as
defined in [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>].
o Collection - A Resource that contains a set of Member Resources.
Collections are represented as Atom Feeds. See <a href="#section-9">Section 9</a>.
<span class="grey">Gregorio & de hOra Standards Track [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
o Member (or Member Resource) - A Resource whose IRI is listed in a
Collection by an atom:link element with a relation of "edit" or
"edit-media". See <a href="#section-9.1">Section 9.1</a>. The protocol defines two kinds of
Members:
* Entry Resource - Members of a Collection that are represented
as Atom Entry Documents, as defined in [<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>].
* Media Resource - Members of a Collection that have
representations other than Atom Entry Documents.
o Media Link Entry - An Entry Resource that contains metadata about
a Media Resource. See <a href="#section-9.6">Section 9.6</a>.
o Workspace - A named group of Collections. See <a href="#section-8.1">Section 8.1</a>.
o Service Document - A document that describes the location and
capabilities of one or more Collections, grouped into Workspaces.
See <a href="#section-8">Section 8</a>.
o Category Document - A document that describes the categories
allowed in a Collection. See <a href="#section-7">Section 7</a>.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Protocol Model</span>
The Atom Protocol specifies operations for publishing and editing
Resources using HTTP. It uses Atom-formatted representations to
describe the state and metadata of those Resources. It defines how
Collections of Resources can be organized, and it specifies formats
to support their discovery, grouping and categorization.
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Identity and Naming</span>
Atom Protocol documents allow the use of IRIs [<a href="./rfc3987" title=""Internationalized Resource Identifiers (IRIs)"">RFC3987</a>] as well as
URIs [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>] to identify Resources. Before an IRI in a document is
used by HTTP, the IRI is first converted to a URI according to the
procedure defined in <a href="./rfc3987#section-3.1">Section 3.1 of [RFC3987]</a>. In accordance with
that specification, the conversion SHOULD be applied as late as
possible. Conversion does not imply Resource creation -- the IRI and
the URI into which it is converted identify the same Resource.
While the Atom Protocol specifies the formats of the representations
that are exchanged and the actions that can be performed on the IRIs
embedded in those representations, it does not constrain the form of
the URIs that are used. HTTP [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>] specifies that the URI space
of each server is controlled by that server, and this protocol
imposes no further constraints on that control.
<span class="grey">Gregorio & de hOra Standards Track [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Documents and Resource Classification</span>
A Resource whose IRI is listed in a Collection is called a Member
Resource. The protocol defines two kinds of Member Resources --
Entry Resources and Media Resources. Entry Resources are represented
as Atom Entry Documents [<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>]. Media Resources can have
representations in any media type. A Media Resource is described
within a Collection using an Entry called a Media Link Entry. This
diagram shows the classification of Resources within the Atom
Protocol:
Member Resources
|
-----------------
| |
Entry Resources Media Resources
|
Media Link Entry
The Atom Protocol defines Collection Resources for managing and
organizing both kinds of Member Resource. A Collection is
represented by an Atom Feed Document. A Collection Feed's Entries
contain the IRIs of, and metadata about, the Collection's Member
Resources. A Collection Feed can contain any number of Entries,
which might represent all the Members of the Collection, or an
ordered subset of them (see <a href="#section-10.1">Section 10.1</a>). In the diagram of a
Collection below, there are two Entries. The first contains the IRI
of an Entry Resource. The second contains the IRIs of both a Media
Resource and a Media Link Entry, which contains the metadata for that
Media Resource:
Collection
|
o- Entry
| |
| o- Member Entry IRI (Entry Resource)
|
o- Entry
|
o- Member Entry IRI (Media Link Entry)
|
o- Media IRI (Media Resource)
The Atom Protocol does not make a distinction between Feeds used for
Collections and other Atom Feeds. The only mechanism that this
specification supplies for indicating that a Feed is a Collection
Feed is the presence of the Feed's IRI in a Service Document.
<span class="grey">Gregorio & de hOra Standards Track [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
Service Documents represent server-defined groups of Collections, and
are used to initialize the process of creating and editing Resources.
These groups of Collections are called Workspaces. Workspaces have
names, but no IRIs, and no specified processing model. The Service
Document can indicate which media types, and which categories, a
Collection will accept. In the diagram below, there are two
Workspaces each describing the IRIs, acceptable media types, and
categories for a Collection:
Service
o- Workspace
| |
| o- Collection
| |
| o- IRI, categories, media types
|
o- Workspace
|
o- Collection
|
o- IRI, categories, media types
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Control and Publishing</span>
The Atom Publishing Protocol uses HTTP methods to author Member
Resources as follows:
o GET is used to retrieve a representation of a known Resource.
o POST is used to create a new, dynamically named, Resource. When
the client submits non-Atom-Entry representations to a Collection
for creation, two Resources are always created -- a Media Entry
for the requested Resource, and a Media Link Entry for metadata
about the Resource that will appear in the Collection.
o PUT is used to edit a known Resource. It is not used for Resource
creation.
o DELETE is used to remove a known Resource.
The Atom Protocol only covers the creating, editing, and deleting of
Entry and Media Resources. Other Resources could be created, edited,
and deleted as the result of manipulating a Collection, but the
number of those Resources, their media types, and effects of Atom
Protocol operations on them are outside the scope of this
specification.
<span class="grey">Gregorio & de hOra Standards Track [Page 8]</span><span id="page-9" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
Since all aspects of client-server interaction are defined in terms
of HTTP, [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>] should be consulted for any areas not covered in
this specification.
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Client Implementation Considerations</span>
The Atom Protocol imposes few restrictions on the actions of servers.
Unless a constraint is specified here, servers can be expected to
vary in behavior, in particular around the manipulation of Atom
Entries sent by clients. For example, although this specification
only defines the expected behavior of Collections with respect to GET
and POST, this does not imply that PUT, DELETE, PROPPATCH, and others
are forbidden on Collection Resources -- only that this specification
does not define what the server's response would be to those methods.
Similarly, while some HTTP status codes are mentioned explicitly,
clients ought to be prepared to handle any status code from a server.
Servers can choose to accept, reject, delay, moderate, censor,
reformat, translate, relocate, or re-categorize the content submitted
to them. Only some of these choices are immediately relayed back to
the client in responses to client requests; other choices may only
become apparent later, in the feed or published entries. The same
series of requests to two different publishing sites can result in a
different series of HTTP responses, different resulting feeds, or
different entry contents.
As a result, client software has to be written flexibly to accept
what the server decides are the results of its submissions. Any
server response or server content modification not explicitly
forbidden by this specification or HTTP [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>] is therefore
allowed.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Protocol Operations</span>
While specific HTTP status codes are shown in the interaction
diagrams below, an AtomPub client should be prepared to handle any
status code. For example, a PUT to a Member URI could result in the
return of a "204 No Content" status code, which still indicates
success.
<span class="grey">Gregorio & de hOra Standards Track [Page 9]</span><span id="page-10" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Retrieving a Service Document</span>
Client Server
| |
| 1.) GET to Service Document URI |
|------------------------------------------>|
| |
| 2.) 200 Ok |
| Service Document |
|<------------------------------------------|
| |
1. The client sends a GET request to the URI of the Service
Document.
2. The server responds with a Service Document enumerating the IRIs
of a group of Collections and the capabilities of those
Collections supported by the server. The content of this
document can vary based on aspects of the client request,
including, but not limited to, authentication credentials.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Listing Collection Members</span>
To list the Members of a Collection, the client sends a GET request
to the URI of a Collection. An Atom Feed Document is returned whose
Entries contain the IRIs of Member Resources. The returned Feed may
describe all, or only a partial list, of the Members in a Collection
(see <a href="#section-10">Section 10</a>).
Client Server
| |
| 1.) GET to Collection URI |
|------------------------------->|
| |
| 2.) 200 Ok |
| Atom Feed Document |
|<-------------------------------|
| |
1. The client sends a GET request to the URI of the Collection.
2. The server responds with an Atom Feed Document containing the
IRIs of the Collection Members.
<span class="grey">Gregorio & de hOra Standards Track [Page 10]</span><span id="page-11" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Creating a Resource</span>
Client Server
| |
| 1.) POST to Collection URI |
| Member Representation |
|------------------------------------------>|
| |
| 2.) 201 Created |
| Location: Member Entry URI |
|<------------------------------------------|
| |
1. The client POSTs a representation of the Member to the URI of the
Collection.
2. If the Member Resource was created successfully, the server
responds with a status code of 201 and a Location header that
contains the IRI of the newly created Entry Resource. Media
Resources could have also been created and their IRIs can be
found through the Entry Resource. See <a href="#section-9.6">Section 9.6</a> for more
details.
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Editing a Resource</span>
Once a Resource has been created and its Member URI is known, that
URI can be used to retrieve, edit, and delete the Resource. <a href="#section-11">Section</a>
<a href="#section-11">11</a> describes extensions to the Atom Syndication Format used in the
Atom Protocol for editing purposes.
<span class="h4"><a class="selflink" id="section-5.4.1" href="#section-5.4.1">5.4.1</a>. Retrieving a Resource</span>
Client Server
| |
| 1.) GET to Member URI |
|------------------------------------------>|
| |
| 2.) 200 Ok |
| Member Representation |
|<------------------------------------------|
| |
1. The client sends a GET request to the URI of a Member Resource to
retrieve its representation.
2. The server responds with the representation of the Member
Resource.
<span class="grey">Gregorio & de hOra Standards Track [Page 11]</span><span id="page-12" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h4"><a class="selflink" id="section-5.4.2" href="#section-5.4.2">5.4.2</a>. Editing a Resource</span>
Client Server
| |
| 1.) PUT to Member URI |
| Member Representation |
|------------------------------------------>|
| |
| 2.) 200 OK |
|<------------------------------------------|
1. The client sends a PUT request to store a representation of a
Member Resource.
2. If the request is successful, the server responds with a status
code of 200.
<span class="h4"><a class="selflink" id="section-5.4.3" href="#section-5.4.3">5.4.3</a>. Deleting a Resource</span>
Client Server
| |
| 1.) DELETE to Member URI |
|------------------------------------------>|
| |
| 2.) 200 OK |
|<------------------------------------------|
| |
1. The client sends a DELETE request to the URI of a Member
Resource.
2. If the deletion is successful, the server responds with a status
code of 200.
A different approach is taken for deleting Media Resources; see
<a href="#section-9.4">Section 9.4</a> for details.
<span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. Use of HTTP Response Codes</span>
The Atom Protocol uses the response status codes defined in HTTP to
indicate the success or failure of an operation. Consult the HTTP
specification [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>] for detailed definitions of each status code.
Implementers are asked to note that according to the HTTP
specification, HTTP 4xx and 5xx response entities SHOULD include a
human-readable explanation of the error.
<span class="grey">Gregorio & de hOra Standards Track [Page 12]</span><span id="page-13" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Protocol Documents</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Document Types</span>
This specification defines two kinds of documents -- Category
Documents and Service Documents.
A Category Document (<a href="#section-7">Section 7</a>) contains lists of categories
specified using the "atom:category" element from the Atom Syndication
Format (see <a href="./rfc4287#section-4.2.2">Section 4.2.2 of [RFC4287]</a>).
A Service Document (<a href="#section-8">Section 8</a>) groups available Collections into
Workspaces.
The namespace name [<a href="#ref-REC-xml-names">REC-xml-names</a>] for either kind of document is:
<a href="http://www.w3.org/2007/app">http://www.w3.org/2007/app</a>
Atom Publishing Protocol XML Documents MUST be "namespace-well-
formed" as specified in Section 7 of [<a href="#ref-REC-xml-names">REC-xml-names</a>].
This specification uses the prefix "app:" for the namespace name.
The prefix "atom:" is used for "<a href="http://www.w3.org/2005/Atom">http://www.w3.org/2005/Atom</a>", the
namespace name of the Atom Syndication Format [<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>]. These
namespace prefixes are not semantically significant.
This specification does not define any DTDs for Atom Protocol
formats, and hence does not require them to be "valid" in the sense
used by [<a href="#ref-REC-xml" title=""Extensible Markup Language (XML) 1.0 (Fourth Edition)"">REC-xml</a>].
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Document Extensibility</span>
Unrecognized markup in an Atom Publishing Protocol document is
considered "foreign markup" as defined in <a href="#section-6">Section 6</a> of the Atom
Syndication Format [<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>]. Foreign markup can be used anywhere
within a Category or Service Document unless it is explicitly
forbidden. Processors that encounter foreign markup MUST NOT stop
processing and MUST NOT signal an error. Clients SHOULD preserve
foreign markup when transmitting such documents.
The namespace name "<a href="http://www.w3.org/2007/app">http://www.w3.org/2007/app</a>" is reserved for
forward-compatible revisions of the Category and Service Document
types. This does not exclude the addition of elements and attributes
that might not be recognized by processors conformant to this
specification. Such unrecognized markup from the
"<a href="http://www.w3.org/2007/app">http://www.w3.org/2007/app</a>" namespace MUST be treated as foreign
markup.
<span class="grey">Gregorio & de hOra Standards Track [Page 13]</span><span id="page-14" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Category Documents</span>
Category Documents contain lists of categories described using the
"atom:category" element from the Atom Syndication Format [<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>].
Categories can also appear in Service Documents, where they indicate
the categories allowed in a Collection (see <a href="#section-8.3.6">Section 8.3.6</a>).
Category Documents are identified with the "application/atomcat+xml"
media type (see <a href="#section-16.1">Section 16.1</a>).
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Example</span>
<?xml version="1.0" ?>
<app:categories
xmlns:app="http://www.w3.org/2007/app"
xmlns:atom="http://www.w3.org/2005/Atom"
fixed="yes" scheme="http://example.com/cats/big3">
<atom:category term="animal" />
<atom:category term="vegetable" />
<atom:category term="mineral" />
</app:categories>
This Category Document contains atom:category elements, with the
terms 'animal', 'vegetable', and 'mineral'. None of the categories
use the "label" attribute defined in [<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>]. They all inherit the
"http://example.com/cats/big3" "scheme" attribute declared on the
app:categories element. Therefore if the 'mineral' category were to
appear in an Atom Entry or Feed Document, it would appear as:
<atom:category scheme="http://example.com/cats/big3" term="mineral"/>
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Element Definitions</span>
<span class="h4"><a class="selflink" id="section-7.2.1" href="#section-7.2.1">7.2.1</a>. The "app:categories" Element</span>
The root of a Category Document is the "app:categories" element. An
app:categories element can contain zero or more atom:category
elements from the Atom Syndication Format [<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>] namespace
("<a href="http://www.w3.org/2005/Atom">http://www.w3.org/2005/Atom</a>").
An atom:category child element that has no "scheme" attribute
inherits the attribute from its app:categories parent. An atom:
category child element with an existing "scheme" attribute does not
inherit the "scheme" value of its app:categories parent element.
<span class="grey">Gregorio & de hOra Standards Track [Page 14]</span><span id="page-15" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
atomCategory =
element atom:category {
atomCommonAttributes,
attribute term { text },
attribute scheme { atomURI }?,
attribute label { text }?,
undefinedContent
}
appInlineCategories =
element app:categories {
attribute fixed { "yes" | "no" }?,
attribute scheme { atomURI }?,
(atomCategory*,
undefinedContent)
}
appOutOfLineCategories =
element app:categories {
attribute href { atomURI },
undefinedContent
}
appCategories = appInlineCategories | appOutOfLineCategories
<span class="h5"><a class="selflink" id="section-7.2.1.1" href="#section-7.2.1.1">7.2.1.1</a>. Attributes of "app:categories"</span>
The app:categories element can contain a "fixed" attribute, with a
value of either "yes" or "no", indicating whether the list of
categories is a fixed or an open set. The absence of the "fixed"
attribute is equivalent to the presence of a "fixed" attribute with a
value of "no".
Alternatively, the app:categories element MAY contain an "href"
attribute, whose value MUST be an IRI reference identifying a
Category Document. If the "href" attribute is provided, the app:
categories element MUST be empty and MUST NOT have the "fixed" or
"scheme" attributes.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Service Documents</span>
For authoring to commence, a client needs to discover the
capabilities and locations of the available Collections. Service
Documents are designed to support this discovery process.
How Service Documents are discovered is not defined in this
specification.
<span class="grey">Gregorio & de hOra Standards Track [Page 15]</span><span id="page-16" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
Service Documents are identified with the "application/atomsvc+xml"
media type (see <a href="#section-16.2">Section 16.2</a>).
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Workspaces</span>
A Service Document groups Collections into Workspaces. Operations on
Workspaces, such as creation or deletion, are not defined by this
specification. This specification assigns no meaning to Workspaces;
that is, a Workspace does not imply any specific processing
assumptions.
There is no requirement that a server support multiple Workspaces.
In addition, a Collection MAY appear in more than one Workspace.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Example</span>
<?xml version="1.0" encoding='utf-8'?>
<service xmlns="http://www.w3.org/2007/app"
xmlns:atom="http://www.w3.org/2005/Atom">
<workspace>
<atom:title>Main Site</atom:title>
<collection
href="http://example.org/blog/main" >
<atom:title>My Blog Entries</atom:title>
<categories
href="http://example.com/cats/forMain.cats" />
</collection>
<collection
href="http://example.org/blog/pic" >
<atom:title>Pictures</atom:title>
<accept>image/png</accept>
<accept>image/jpeg</accept>
<accept>image/gif</accept>
</collection>
</workspace>
<workspace>
<atom:title>Sidebar Blog</atom:title>
<collection
href="http://example.org/sidebar/list" >
<atom:title>Remaindered Links</atom:title>
<accept>application/atom+xml;type=entry</accept>
<categories fixed="yes">
<atom:category
scheme="http://example.org/extra-cats/"
term="joke" />
<atom:category
scheme="http://example.org/extra-cats/"
term="serious" />
<span class="grey">Gregorio & de hOra Standards Track [Page 16]</span><span id="page-17" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
</categories>
</collection>
</workspace>
</service>
The Service Document above describes two Workspaces. The first
Workspace is called "Main Site", and has two Collections called "My
Blog Entries" and "Pictures", whose IRIs are
"http://example.org/blog/main" and "http://example.org/blog/pic"
respectively. The "Pictures" Collection includes three "accept"
elements indicating the types of image files the client can send to
the Collection to create new Media Resources (entries associated with
Media Resources are discussed in <a href="#section-9.6">Section 9.6</a>).
The second Workspace is called "Sidebar Blog" and has a single
Collection called "Remaindered Links" whose IRI is
"http://example.org/sidebar/list". The Collection has an "accept"
element whose content is "application/atom+xml;type=entry",
indicating it will accept Atom Entries from a client.
Within each of the two Entry Collections, the "categories" element
provides a list of available categories for Member Entries. In the
"My Blog Entries" Collection, the list of available categories is
available through the "href" attribute. The "Sidebar Blog"
Collection provides a category list within the Service Document, but
states the list is fixed, signaling a request from the server that
Entries be POSTed using only those two categories.
<span class="h3"><a class="selflink" id="section-8.3" href="#section-8.3">8.3</a>. Element Definitions</span>
<span class="h4"><a class="selflink" id="section-8.3.1" href="#section-8.3.1">8.3.1</a>. The "app:service" Element</span>
The root of a Service Document is the "app:service" element.
The app:service element is the container for service information
associated with one or more Workspaces. An app:service element MUST
contain one or more app:workspace elements.
namespace app = "<a href="http://www.w3.org/2007/app">http://www.w3.org/2007/app</a>"
start = appService
appService =
element app:service {
appCommonAttributes,
( appWorkspace+
& extensionElement* )
}
<span class="grey">Gregorio & de hOra Standards Track [Page 17]</span><span id="page-18" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h4"><a class="selflink" id="section-8.3.2" href="#section-8.3.2">8.3.2</a>. The "app:workspace" Element</span>
Workspaces are server-defined groups of Collections. The "app:
workspace" element contains zero or more app:collection elements
describing the Collections of Resources available for editing.
appWorkspace =
element app:workspace {
appCommonAttributes,
( atomTitle
& appCollection*
& extensionSansTitleElement* )
}
atomTitle = element atom:title { atomTextConstruct }
<span class="h5"><a class="selflink" id="section-8.3.2.1" href="#section-8.3.2.1">8.3.2.1</a>. The "atom:title" Element</span>
The app:workspace element MUST contain one "atom:title" element (as
defined in [<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>]), giving a human-readable title for the
Workspace.
<span class="h4"><a class="selflink" id="section-8.3.3" href="#section-8.3.3">8.3.3</a>. The "app:collection" Element</span>
The "app:collection" element describes a Collection. The app:
collection element MUST contain one atom:title element.
The app:collection element MAY contain any number of app:accept
elements, indicating the types of representations accepted by the
Collection. The order of such elements is not significant.
The app:collection element MAY contain any number of app:categories
elements.
appCollection =
element app:collection {
appCommonAttributes,
attribute href { atomURI },
( atomTitle
& appAccept*
& appCategories*
& extensionSansTitleElement* )
}
<span class="h5"><a class="selflink" id="section-8.3.3.1" href="#section-8.3.3.1">8.3.3.1</a>. The "href" Attribute</span>
The app:collection element MUST contain an "href" attribute, whose
value gives the IRI of the Collection.
<span class="grey">Gregorio & de hOra Standards Track [Page 18]</span><span id="page-19" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h5"><a class="selflink" id="section-8.3.3.2" href="#section-8.3.3.2">8.3.3.2</a>. The "atom:title" Element</span>
The "atom:title" element is defined in [<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>] and gives a human-
readable title for the Collection.
<span class="h4"><a class="selflink" id="section-8.3.4" href="#section-8.3.4">8.3.4</a>. The "app:accept" Element</span>
The content of an "app:accept" element value is a media range as
defined in [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>]. The media range specifies a type of
representation that can be POSTed to a Collection.
The app:accept element is similar to the HTTP Accept request-header
[<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>]. Media type parameters are allowed within app:accept, but
app:accept has no notion of preference -- "accept-params" or "q"
arguments, as specified in <a href="./rfc2616#section-14.1">Section 14.1 of [RFC2616]</a> are not
significant.
White space (as defined in [<a href="#ref-REC-xml" title=""Extensible Markup Language (XML) 1.0 (Fourth Edition)"">REC-xml</a>]) around the app:accept element's
media range is insignificant and MUST be ignored.
A value of "application/atom+xml;type=entry" MAY appear in any app:
accept list of media ranges and indicates that Atom Entry Documents
can be POSTed to the Collection. If no app:accept element is
present, clients SHOULD treat this as equivalent to an app:accept
element with the content "application/atom+xml;type=entry".
If one app:accept element exists and is empty, clients SHOULD assume
that the Collection does not support the creation of new Entries.
appAccept =
element app:accept {
appCommonAttributes,
( text? )
}
<span class="h4"><a class="selflink" id="section-8.3.5" href="#section-8.3.5">8.3.5</a>. Usage in Atom Feed Documents</span>
The app:collection element MAY appear as a child of an atom:feed or
atom:source element in an Atom Feed Document. Its content identifies
a Collection by which new Entries can be added to appear in the feed.
When it appears in an atom:feed or atom:source element, the app:
collection element is considered foreign markup as defined in <a href="./rfc4287#section-6">Section</a>
<a href="./rfc4287#section-6">6 of [RFC4287]</a>.
<span class="grey">Gregorio & de hOra Standards Track [Page 19]</span><span id="page-20" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h4"><a class="selflink" id="section-8.3.6" href="#section-8.3.6">8.3.6</a>. The "app:categories" Element</span>
The "app:categories" element provides a list of the categories that
can be applied to the members of a Collection. See <a href="#section-7.2.1">Section 7.2.1</a> for
the detailed definition of app:categories.
The server MAY reject attempts to create or store members whose
categories are not present in its categories list. A Collection that
indicates the category set is open SHOULD NOT reject otherwise
acceptable members whose categories are not in its categories list.
The absence of an app:categories element means that the category
handling of the Collection is unspecified. A "fixed" category list
that contains zero categories indicates the Collection does not
accept category data.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Creating and Editing Resources</span>
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Member URIs</span>
The Member URI allows clients to retrieve, edit, and delete a Member
Resource using HTTP's GET, PUT, and DELETE methods. Entry Resources
are represented as Atom Entry documents.
Member URIs appear in two places. They are returned in a Location
header after successful Resource creation using POST, as described in
<a href="#section-9.2">Section 9.2</a> below. They can also appear in a Collection Feed's
Entries, as atom:link elements with a link relation of "edit".
A Member Entry SHOULD contain such an atom:link element with a link
relation of "edit", which indicates the Member URI.
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Creating Resources with POST</span>
To add members to a Collection, clients send POST requests to the URI
of the Collection.
Successful member creation is indicated with a 201 ("Created")
response code. When the Collection responds with a status code of
201, it SHOULD also return a response body, which MUST be an Atom
Entry Document representing the newly created Resource. Since the
server is free to alter the POSTed Entry, for example, by changing
the content of the atom:id element, returning the Entry can be useful
to the client, enabling it to correlate the client and server views
of the new Entry.
When a Member Resource is created, its Member Entry URI MUST be
returned in a Location header in the Collection's response.
<span class="grey">Gregorio & de hOra Standards Track [Page 20]</span><span id="page-21" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
If the creation request contained an Atom Entry Document, and the
subsequent response from the server contains a Content-Location
header that matches the Location header character-for-character, then
the client is authorized to interpret the response entity as being a
complete representation of the newly created Entry. Without a
matching Content-Location header, the client MUST NOT assume the
returned entity is a complete representation of the created Resource.
The request body sent with the POST need not be an Atom Entry. For
example, it might be a picture or a movie. Collections MAY return a
response with a status code of 415 ("Unsupported Media Type") to
indicate that the media type of the POSTed entity is not allowed or
supported by the Collection. For a discussion of the issues in
creating such content, see <a href="#section-9.6">Section 9.6</a>.
<span class="h4"><a class="selflink" id="section-9.2.1" href="#section-9.2.1">9.2.1</a>. Example</span>
Below, the client sends a POST request containing an Atom Entry
representation using the URI of the Collection:
POST /edit/ HTTP/1.1
Host: example.org
User-Agent: Thingio/1.0
Authorization: Basic ZGFmZnk6c2VjZXJldA==
Content-Type: application/atom+xml;type=entry
Content-Length: nnn
Slug: First Post
<?xml version="1.0"?>
<entry xmlns="http://www.w3.org/2005/Atom">
<title>Atom-Powered Robots Run Amok</title>
<id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id>
<updated>2003-12-13T18:30:02Z</updated>
<author><name>John Doe</name></author>
<content>Some text.</content>
</entry>
The server signals a successful creation with a status code of 201.
The response includes a Location header indicating the Member Entry
URI of the Atom Entry, and a representation of that Entry in the body
of the response.
HTTP/1.1 201 Created
Date: Fri, 7 Oct 2005 17:17:11 GMT
Content-Length: nnn
Content-Type: application/atom+xml;type=entry;charset="utf-8"
Location: http://example.org/edit/first-post.atom
ETag: "c180de84f991g8"
<span class="grey">Gregorio & de hOra Standards Track [Page 21]</span><span id="page-22" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<?xml version="1.0"?>
<entry xmlns="http://www.w3.org/2005/Atom">
<title>Atom-Powered Robots Run Amok</title>
<id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id>
<updated>2003-12-13T18:30:02Z</updated>
<author><name>John Doe</name></author>
<content>Some text.</content>
<link rel="edit"
href="http://example.org/edit/first-post.atom"/>
</entry>
The Entry created and returned by the Collection might not match the
Entry POSTed by the client. A server MAY change the values of
various elements in the Entry, such as the atom:id, atom:updated, and
atom:author values, and MAY choose to remove or add other elements
and attributes, or change element content and attribute values.
<span class="h3"><a class="selflink" id="section-9.3" href="#section-9.3">9.3</a>. Editing Resources with PUT</span>
To edit a Member Resource, a client sends a PUT request to its Member
URI, as specified in [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>].
To avoid unintentional loss of data when editing Member Entries or
Media Link Entries, an Atom Protocol client SHOULD preserve all
metadata that has not been intentionally modified, including unknown
foreign markup as defined in <a href="./rfc4287#section-6">Section 6 of [RFC4287]</a>.
<span class="h3"><a class="selflink" id="section-9.4" href="#section-9.4">9.4</a>. Deleting Resources with DELETE</span>
To delete a Member Resource, a client sends a DELETE request to its
Member URI, as specified in [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>]. The deletion of a Media Link
Entry SHOULD result in the deletion of the corresponding Media
Resource.
<span class="h3"><a class="selflink" id="section-9.5" href="#section-9.5">9.5</a>. Caching and Entity Tags</span>
Implementers are advised to pay attention to cache controls and to
make use of the mechanisms available in HTTP when editing Resources,
in particular, entity-tags as outlined in [<a href="#ref-NOTE-detect-lost-update">NOTE-detect-lost-update</a>].
Clients are not assured to receive the most recent representations of
Collection Members using GET if the server is authorizing
intermediaries to cache them.
<span class="grey">Gregorio & de hOra Standards Track [Page 22]</span><span id="page-23" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h4"><a class="selflink" id="section-9.5.1" href="#section-9.5.1">9.5.1</a>. Example</span>
Below, the client creates a Member Entry using POST:
POST /myblog/entries HTTP/1.1
Host: example.org
Authorization: Basic ZGFmZnk6c2VjZXJldA==
Content-Type: application/atom+xml;type=entry
Content-Length: nnn
Slug: First Post
<?xml version="1.0" ?>
<entry xmlns="http://www.w3.org/2005/Atom">
<title>Atom-Powered Robots Run Amok</title>
<id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id>
<updated>2007-02-123T17:09:02Z</updated>
<author><name>Captain Lansing</name></author>
<content>It's something moving... solid metal</content>
</entry>
The server signals a successful creation with a status code of 201,
and returns an ETag header in the response. Because, in this case,
the server returned a Content-Location header and Location header
with the same value, the returned Entry representation can be
understood to be a complete representation of the newly created Entry
(see <a href="#section-9.2">Section 9.2</a>).
HTTP/1.1 201 Created
Date: Fri, 23 Feb 2007 21:17:11 GMT
Content-Length: nnn
Content-Type: application/atom+xml;type=entry
Location: http://example.org/edit/first-post.atom
Content-Location: http://example.org/edit/first-post.atom
ETag: "e180ee84f0671b1"
<?xml version="1.0" ?>
<entry xmlns="http://www.w3.org/2005/Atom">
<title>Atom-Powered Robots Run Amok</title>
<id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id>
<updated>2007-02-123T17:09:02Z</updated>
<author><name>Captain Lansing</name></author>
<content>It's something moving... solid metal</content>
</entry>
The client can, if it wishes, use the returned ETag value to later
construct a "Conditional GET" as defined in [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>]. In this case,
prior to editing, the client sends the ETag value for the Member
using the If-None-Match header.
<span class="grey">Gregorio & de hOra Standards Track [Page 23]</span><span id="page-24" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
GET /edit/first-post.atom HTTP/1.1
Host: example.org
Authorization: Basic ZGFmZnk6c2VjZXJldA==
If-None-Match: "e180ee84f0671b1"
If the Entry has not been modified, the response will be a status
code of 304 ("Not Modified"). This allows the client to determine
whether it still has the most recent representation of the Entry at
the time of editing.
HTTP/1.1 304 Not Modified
Date: Sat, 24 Feb 2007 13:17:11 GMT
After editing, the client can PUT the Entry and send the ETag entity
value in an If-Match header, informing the server to accept the entry
on the condition that the entity value sent still matches the
server's.
PUT /edit/first-post.atom HTTP/1.1
Host: example.org
Authorization: Basic ZGFmZnk6c2VjZXJldA==
Content-Type: application/atom+xml;type=entry
Content-Length: nnn
If-Match: "e180ee84f0671b1"
<?xml version="1.0" ?>
<entry xmlns="http://www.w3.org/2005/Atom">
<title>Atom-Powered Robots Run Amok</title>
<id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id>
<updated>2007-02-24T16:34:06Z</updated>
<author><name>Captain Lansing</name></author>
<content>Update: it's a hoax!</content>
</entry>
The server however has since received a more recent copy than the
client's, and it responds with a status code of 412 ("Precondition
Failed").
HTTP/1.1 412 Precondition Failed
Date: Sat, 24 Feb 2007 16:34:11 GMT
This informs the client that the server has a more recent version of
the Entry and will not allow the sent entity to be stored.
<span class="grey">Gregorio & de hOra Standards Track [Page 24]</span><span id="page-25" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h3"><a class="selflink" id="section-9.6" href="#section-9.6">9.6</a>. Media Resources and Media Link Entries</span>
A client can POST Media Resources as well as Entry Resources to a
Collection. If a server accepts such a request, then it MUST create
two new Resources -- one that corresponds to the entity sent in the
request, called the Media Resource, and an associated Member Entry,
called the Media Link Entry. Media Link Entries are represented as
Atom Entries, and appear in the Collection.
The Media Link Entry contains the metadata and IRI of the (perhaps
non-textual) Media Resource. The Media Link Entry thus makes the
metadata about the Media Resource separately available for retrieval
and alteration.
The server can signal the media types it will accept using the app:
accept element in the Service Document, as specified in <a href="#section-8.3.4">Section</a>
<a href="#section-8.3.4">8.3.4</a>.
Successful responses to creation requests MUST include the URI of the
Media Link Entry in the Location header. The Media Link Entry SHOULD
contain an atom:link element with a link relation of "edit-media"
that contains the Media Resource IRI. The Media Link Entry MUST have
an atom:content element with a "src" attribute. The value of the
"src" attribute is an IRI for the newly created Media Resource. It
is OPTIONAL that the IRI of the "src" attribute on the atom:content
element be the same as the Media Resource IRI. For example, the
"src" attribute value might instead be a link into a static cache or
content distribution network and not the Media Resource IRI.
Implementers are asked to note that [<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>] specifies that Atom
Entries MUST contain an atom:summary element. Thus, upon successful
creation of a Media Link Entry, a server MAY choose to populate the
atom:summary element (as well as any other mandatory elements such as
atom:id, atom:author, and atom:title) with content derived from the
POSTed entity or from any other source. A server might not allow a
client to modify the server-selected values for these elements.
For Resource creation, this specification only defines cases where
the POST body has an Atom Entry entity declared as an Atom media type
("application/atom+xml"), or a non-Atom entity declared as a non-Atom
media type. When a client is POSTing an Atom Entry to a Collection,
it may use a media type of either "application/atom+xml" or
"application/atom +xml;type=entry". This specification does not
specify any request semantics or server behavior in the case where
the POSTed media type is "application/atom+xml" but the body is
something other than an Atom Entry. In particular, what happens on
POSTing an Atom Feed Document to a Collection using the "application/
atom+xml" media type is undefined.
<span class="grey">Gregorio & de hOra Standards Track [Page 25]</span><span id="page-26" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
The Atom Protocol does not specify a means to create multiple
representations of the same Resource (for example, a PNG and a JPG of
the same image) either on creation or editing.
<span class="h4"><a class="selflink" id="section-9.6.1" href="#section-9.6.1">9.6.1</a>. Examples</span>
Below, the client sends a POST request containing a PNG image to the
URI of a Collection that accepts PNG images:
POST /edit/ HTTP/1.1
Host: media.example.org
Content-Type: image/png
Slug: The Beach
Authorization: Basic ZGFmZnk6c2VjZXJldA==
Content-Length: nnn
...binary data...
The server signals a successful creation with a status code of 201.
The response includes a Location header indicating the Member URI of
the Media Link Entry and a representation of that entry in the body
of the response. The Media Link Entry includes a content element
with a "src" attribute. It also contains a link with a link relation
of "edit-media", specifying the IRI to be used for modifying the
Media Resource.
HTTP/1.1 201 Created
Date: Fri, 7 Oct 2005 17:17:11 GMT
Content-Length: nnn
Content-Type: application/atom+xml;type=entry;charset="utf-8"
Location: http://example.org/media/edit/the_beach.atom
<?xml version="1.0"?>
<entry xmlns="http://www.w3.org/2005/Atom">
<title>The Beach</title>
<id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id>
<updated>2005-10-07T17:17:08Z</updated>
<author><name>Daffy</name></author>
<summary type="text" />
<content type="image/png"
src="http://media.example.org/the_beach.png"/>
<link rel="edit-media"
href="http://media.example.org/edit/the_beach.png" />
<link rel="edit"
href="http://example.org/media/edit/the_beach.atom" />
</entry>
<span class="grey">Gregorio & de hOra Standards Track [Page 26]</span><span id="page-27" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
Later, the client sends a PUT request containing the new PNG using
the URI indicated in the Media Link Entry's "edit-media" link:
PUT /edit/the_beach.png HTTP/1.1
Host: media.example.org
Content-Type: image/png
Authorization: Basic ZGFmZnk6c2VjZXJldA==
Content-Length: nnn
...binary data...
The server signals a successful edit with a status code of 200.
HTTP/1.1 200 Ok
Date: Fri, 8 Oct 2006 17:17:11 GMT
The client can edit the metadata for the picture. First GET the
Media Link Entry:
GET /media/edit/the_beach.atom HTTP/1.1
Host: example.org
Authorization: Basic ZGFmZnk6c2VjZXJldA==
The Media Link Entry is returned.
HTTP/1.1 200 Ok
Date: Fri, 7 Oct 2005 17:18:11 GMT
Content-Length: nnn
Content-Type: application/atom+xml;type=entry;charset="utf-8"
ETag: "c181bb840673b5"
<?xml version="1.0"?>
<entry xmlns="http://www.w3.org/2005/Atom">
<title>The Beach</title>
<id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id>
<updated>2005-10-07T17:17:08Z</updated>
<author><name>Daffy</name></author>
<summary type="text" />
<content type="image/png"
src="http://media.example.org/the_beach.png"/>
<link rel="edit-media"
href="http://media.example.org/edit/the_beach.png" />
<link rel="edit"
href="http://example.org/media/edit/the_beach.atom" />
</entry>
The metadata can be updated, in this case to add a summary, and then
PUT back to the server.
<span class="grey">Gregorio & de hOra Standards Track [Page 27]</span><span id="page-28" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
PUT /media/edit/the_beach.atom HTTP/1.1
Host: example.org
Authorization: Basic ZGFmZnk6c2VjZXJldA==
Content-Type: application/atom+xml;type=entry
Content-Length: nnn
If-Match: "c181bb840673b5"
<?xml version="1.0"?>
<entry xmlns="http://www.w3.org/2005/Atom">
<title>The Beach</title>
<id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id>
<updated>2005-10-07T17:17:08Z</updated>
<author><name>Daffy</name></author>
<summary type="text">
A nice sunset picture over the water.
</summary>
<content type="image/png"
src="http://media.example.org/the_beach.png"/>
<link rel="edit-media"
href="http://media.example.org/edit/the_beach.png" />
<link rel="edit"
href="http://example.org/media/edit/the_beach.atom" />
</entry>
The update was successful.
HTTP/1.1 200 Ok
Date: Fri, 7 Oct 2005 17:19:11 GMT
Content-Length: 0
Multiple Media Resources can be added to the Collection.
POST /edit/ HTTP/1.1
Host: media.example.org
Content-Type: image/png
Slug: The Pier
Authorization: Basic ZGFmZnk6c2VjZXJldA==
Content-Length: nnn
...binary data...
The Resource is created successfully.
HTTP/1.1 201 Created
Date: Fri, 7 Oct 2005 17:17:11 GMT
Content-Length: nnn
Content-Type: application/atom+xml;type=entry;charset="utf-8"
Location: http://example.org/media/edit/the_pier.atom
<span class="grey">Gregorio & de hOra Standards Track [Page 28]</span><span id="page-29" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<?xml version="1.0"?>
<entry xmlns="http://www.w3.org/2005/Atom">
<title>The Pier</title>
<id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efe6b</id>
<updated>2005-10-07T17:26:43Z</updated>
<author><name>Daffy</name></author>
<summary type="text" />
<content type="image/png"
src="http://media.example.org/the_pier.png"/>
<link rel="edit-media"
href="http://media.example.org/edit/the_pier.png" />
<link rel="edit"
href="http://example.org/media/edit/the_pier.atom" />
</entry>
The client can now create a new Atom Entry in the blog Entry
Collection that references the two newly created Media Resources.
POST /blog/ HTTP/1.1
Host: example.org
Content-Type: application/atom+xml;type=entry
Slug: A day at the beach
Authorization: Basic ZGFmZnk6c2VjZXJldA==
Content-Length: nnn
<?xml version="1.0"?>
<entry xmlns="http://www.w3.org/2005/Atom">
<title>A fun day at the beach</title>
<id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6b</id>
<updated>2005-10-07T17:40:02Z</updated>
<author><name>Daffy</name></author>
<content type="xhtml">
<xhtml:div xmlns:xhtml="http://www.w3.org/1999/xhtml">
<xhtml:p>We had a good day at the beach.
<xhtml:img alt="the beach"
src="http://media.example.org/the_beach.png"/>
</xhtml:p>
<xhtml:p>Later we walked down to the pier.
<xhtml:img alt="the pier"
src="http://media.example.org/the_pier.png"/>
</xhtml:p>
</xhtml:div>
</content>
</entry>
The Resource is created successfully.
<span class="grey">Gregorio & de hOra Standards Track [Page 29]</span><span id="page-30" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
HTTP/1.1 200 Ok
Date: Fri, 7 Oct 2005 17:20:11 GMT
Content-Length: nnn
Content-Type: application/atom+xml;type=entry;charset="utf-8"
Location: http://example.org/blog/atom/a-day-at-the-beach.atom
<?xml version="1.0"?>
<entry xmlns="http://www.w3.org/2005/Atom">
<title>A fun day at the beach</title>
<id>http://example.org/blog/a-day-at-the-beach.xhtml</id>
<updated>2005-10-07T17:43:07Z</updated>
<author><name>Daffy</name></author>
<content type="xhtml">
<xhtml:div xmlns:xhtml="http://www.w3.org/1999/xhtml">
<xhtml:p>We had a good day at the beach.
<xhtml:img alt="the beach"
src="http://media.example.org/the_beach.png"/>
</xhtml:p>
<xhtml:p>Later we walked down to the pier.
<xhtml:img alt="the pier"
src="http://media.example.org/the_pier.png"/>
</xhtml:p>
</xhtml:div>
</content>
<link rel="edit"
href="http://example.org/blog/edit/a-day-at-the-beach.atom"/>
<link rel="alternate" type="text/html"
href="http://example.org/blog/a-day-at-the-beach.html"/>
</entry>
Note that the returned Entry contains a link with a relation of
"alternate" that points to the associated HTML page that was created
-- this is not required by this specification, but is included to
show the kinds of changes a server can make to an Entry.
<span class="h3"><a class="selflink" id="section-9.7" href="#section-9.7">9.7</a>. The Slug Header</span>
Slug is an HTTP entity-header whose presence in a POST to a
Collection constitutes a request by the client to use the header's
value as part of any URIs that would normally be used to retrieve the
to-be-created Entry or Media Resources.
Servers MAY use the value of the Slug header when creating the Member
URI of the newly created Resource, for instance, by using some or all
of the words in the value for the last URI segment. Servers MAY also
use the value when creating the atom:id, or as the title of a Media
Link Entry (see <a href="#section-9.6">Section 9.6</a>).
<span class="grey">Gregorio & de hOra Standards Track [Page 30]</span><span id="page-31" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
Servers MAY choose to ignore the Slug entity-header. Servers MAY
alter the header value before using it. For instance, a server might
filter out some characters or replace accented letters with non-
accented ones, replace spaces with underscores, change case, and so
on.
<span class="h4"><a class="selflink" id="section-9.7.1" href="#section-9.7.1">9.7.1</a>. Slug Header Syntax</span>
The syntax of the Slug header is defined using the augmented BNF
syntax defined in <a href="./rfc2616#section-2.1">Section 2.1 of [RFC2616]</a>:
LWS = <defined in <a href="./rfc2616#section-2.2">Section 2.2 of [RFC2616]</a>>
slugtext = %x20-7E | LWS
Slug = "Slug" ":" *slugtext
The field value is the percent-encoded value of the UTF-8 encoding of
the character sequence to be included (see <a href="./rfc3986#section-2.1">Section 2.1 of [RFC3986]</a>
for the definition of percent encoding, and [<a href="./rfc3629" title=""UTF-8, a transformation format of ISO 10646"">RFC3629</a>] for the
definition of the UTF-8 encoding).
Implementation note: to produce the field value from a character
sequence, first encode it using the UTF-8 encoding, then encode all
octets outside the ranges %20-24 and %26-7E using percent encoding
(%25 is the ASCII encoding of "%", thus it needs to be escaped). To
consume the field value, first reverse the percent encoding, then run
the resulting octet sequence through a UTF-8 decoding process.
<span class="h4"><a class="selflink" id="section-9.7.2" href="#section-9.7.2">9.7.2</a>. Example</span>
Here is an example of the Slug header that uses percent-encoding to
represent the Unicode character U+00E8 (LATIN SMALL LETTER E WITH
GRAVE):
POST /myblog/entries HTTP/1.1
Host: example.org
Content-Type: image/png
Slug: The Beach at S%C3%A8te
Authorization: Basic ZGFmZnk6c2VjZXJldA==
Content-Length: nnn
...binary data...
See <a href="#section-9.2.1">Section 9.2.1</a> for an example of the Slug header applied to the
creation of an Entry Resource.
<span class="grey">Gregorio & de hOra Standards Track [Page 31]</span><span id="page-32" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Listing Collections</span>
Collection Resources MUST provide representations in the form of Atom
Feed Documents whose Entries contain the IRIs of the Members in the
Collection. No distinction is made between Collection Feeds and
other kinds of Feeds -- a Feed might act both as a 'public' feed for
subscription purposes and as a Collection Feed.
Each Entry in the Feed Document SHOULD have an atom:link element with
a relation of "edit" (see <a href="#section-11.1">Section 11.1</a>).
The Entries in the returned Atom Feed SHOULD be ordered by their
"app:edited" property, with the most recently edited Entries coming
first in the document order. The app:edited value is not equivalent
to the HTTP Last-Modified header and cannot be used to determine the
freshness of cached responses.
Clients MUST NOT assume that an Atom Entry returned in the Feed is a
full representation of an Entry Resource and SHOULD perform a GET on
the URI of the Member Entry before editing it. See <a href="#section-9.5">Section 9.5</a> for a
discussion on the implications of cache control directives when
obtaining entries.
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Collection Partial Lists</span>
Collections can contain large numbers of Resources. A client such as
a web spider or web browser might be overwhelmed if the response to a
GET contained every Entry in a Collection -- in turn the server might
also waste bandwidth and processing time on generating a response
that cannot be handled. For this reason, servers MAY respond to
Collection GET requests with a Feed Document containing a partial
list of the Collection's members, and a link to the next partial list
feed, if it exists. The first such partial list returned MUST
contain the most recently edited member Resources and MUST have an
atom:link with a "next" relation whose "href" value is the URI of the
next partial list of the Collection. This next partial list will
contain the next most recently edited set of Member Resources (and an
atom:link to the following partial list if it exists).
In addition to the "next" relation, partial list feeds MAY contain
link elements with "rel" attribute values of "previous", "first", and
"last", that can be used to navigate through the complete set of
entries in the Collection.
For instance, suppose a client is supplied the URI
"http://example.org/entries/go" of a Collection of Member Entries,
where the server as a matter of policy avoids generating Feed
Documents containing more than 10 Entries. The Atom Feed Document
<span class="grey">Gregorio & de hOra Standards Track [Page 32]</span><span id="page-33" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
for the Collection will then represent the first partial list of a
set of 10 linked Feed Documents. The "first" relation references the
initial Feed Document in the set and the "last" relation references
the final Feed Document in the set. Within each document, the
"previous" and "next" link relations reference the preceding and
subsequent documents.
<feed xmlns="http://www.w3.org/2005/Atom">
<link rel="first"
href="http://example.org/entries/go" />
<link rel="next"
href="http://example.org/entries/2" />
<link rel="last"
href="http://example.org/entries/10" />
...
</feed>
The "previous" and "next" link elements for the partial list feed
located at "http://example.org/entries/2" would look like this:
<feed xmlns="http://www.w3.org/2005/Atom">
<link rel="first"
href="http://example.org/entries/go" />
<link rel="previous"
href="http://example.org/entries/go" />
<link rel="next"
href="http://example.org/entries/3" />
<link rel="last"
href="http://example.org/entries/10" />
...
</feed>
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. The "app:edited" Element</span>
The "app:edited" element is a Date construct (as defined by
[<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>]), whose content indicates the last time an Entry was
edited. If the entry has not been edited yet, the content indicates
the time it was created. Atom Entry elements in Collection Documents
SHOULD contain one app:edited element, and MUST NOT contain more than
one.
appEdited = element app:edited ( atomDateConstruct )
The server SHOULD change the value of this element every time an
Entry Resource or an associated Media Resource has been edited.
<span class="grey">Gregorio & de hOra Standards Track [Page 33]</span><span id="page-34" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Atom Format Link Relation Extensions</span>
<span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. The "edit" Link Relation</span>
This specification adds the value "edit" to the Atom Registry of Link
Relations (see <a href="./rfc4287#section-7.1">Section 7.1 of [RFC4287]</a>). The value of "edit"
specifies that the value of the href attribute is the IRI of an
editable Member Entry. When appearing within an atom:entry, the href
IRI can be used to retrieve, update, and delete the Resource
represented by that Entry. An atom:entry MUST NOT contain more than
one "edit" link relation.
<span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. The "edit-media" Link Relation</span>
This specification adds the value "edit-media" to the Atom Registry
of Link Relations (see <a href="./rfc4287#section-7.1">Section 7.1 of [RFC4287]</a>). When appearing
within an atom:entry, the value of the href attribute is an IRI that
can be used to modify a Media Resource associated with that Entry.
An atom:entry element MAY contain zero or more "edit-media" link
relations. An atom:entry MUST NOT contain more than one atom:link
element with a "rel" attribute value of "edit-media" that has the
same "type" and "hreflang" attribute values. All "edit-media" link
relations in the same Entry reference the same Resource. If a client
encounters multiple "edit-media" link relations in an Entry then it
SHOULD choose a link based on the client preferences for "type" and
"hreflang". If a client encounters multiple "edit-media" link
relations in an Entry and has no preference based on the "type" and
"hreflang" attributes then the client SHOULD pick the first "edit-
media" link relation in document order.
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. The Atom Format Type Parameter</span>
The Atom Syndication Format [<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>] defines the "application/
atom+xml" media type to identify both Atom Feed and Atom Entry
Documents. Implementation experience has demonstrated that Atom Feed
and Entry Documents can have different processing models and that
there are situations where they need to be differentiated. This
specification defines a "type" parameter used to differentiate the
two types of Atom documents.
<span class="h3"><a class="selflink" id="section-12.1" href="#section-12.1">12.1</a>. The "type" parameter</span>
This specification defines a new "type" parameter for use with the
"application/atom+xml" media type. The "type" parameter has a value
of "entry" or "feed".
Neither the parameter name nor its value are case sensitive.
<span class="grey">Gregorio & de hOra Standards Track [Page 34]</span><span id="page-35" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
The value "entry" indicates that the media type identifies an Atom
Entry Document. The root element of the document MUST be atom:entry.
The value "feed" indicates that the media type identifies an Atom
Feed Document. The root element of the document MUST be atom:feed.
If not specified, the type is assumed to be unspecified, requiring
Atom processors to examine the root element to determine the type of
Atom document.
<span class="h4"><a class="selflink" id="section-12.1.1" href="#section-12.1.1">12.1.1</a>. Conformance</span>
New specifications MAY require that the "type" parameter be used to
identify the Atom Document type. Producers of Atom Entry Documents
SHOULD use the "type" parameter regardless of whether or not it is
mandatory. Producers of Atom Feed Documents MAY use the parameter.
Atom processors that do not recognize the "type" parameter MUST
ignore its value and examine the root element to determine the
document type.
Atom processors that do recognize the "type" parameter SHOULD detect
and report inconsistencies between the parameter's value and the
actual type of the document's root element.
<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Atom Publishing Controls</span>
This specification defines an Atom Format Structured Extension, as
defined in <a href="./rfc4287#section-6">Section 6 of [RFC4287]</a>, for publishing control within the
"<a href="http://www.w3.org/2007/app">http://www.w3.org/2007/app</a>" namespace.
<span class="h3"><a class="selflink" id="section-13.1" href="#section-13.1">13.1</a>. The "app:control" Element</span>
namespace app = "<a href="http://www.w3.org/2007/app">http://www.w3.org/2007/app</a>"
pubControl =
element app:control {
atomCommonAttributes,
pubDraft?
& extensionElement
}
pubDraft =
element app:draft { "yes" | "no" }
<span class="grey">Gregorio & de hOra Standards Track [Page 35]</span><span id="page-36" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
The "app:control" element MAY appear as a child of an atom:entry that
is being created or updated via the Atom Publishing Protocol. The
app:control element MUST appear only once in an Entry. The app:
control element is considered foreign markup as defined in <a href="./rfc4287#section-6">Section 6
of [RFC4287]</a>.
The app:control element and its child elements MAY be included in
Atom Feed or Entry Documents.
The app:control element can contain an "app:draft" element as defined
below, and it can contain extension elements as defined in <a href="./rfc4287#section-6">Section 6
of [RFC4287]</a>.
<span class="h4"><a class="selflink" id="section-13.1.1" href="#section-13.1.1">13.1.1</a>. The "app:draft" Element</span>
The inclusion of the "app:draft" element represents a request by the
client to control the visibility of a Member Resource. The app:draft
element MAY be ignored by the server.
The number of app:draft elements in app:control MUST be zero or one.
The content of an app:draft element MUST be one of "yes" or "no". If
the element contains "no", this indicates a client request that the
Member Resource be made publicly visible. If the app:draft element
is not present, then servers that support the extension MUST behave
as though an app:draft element containing "no" was sent.
<span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>. Securing the Atom Publishing Protocol</span>
The Atom Publishing Protocol is based on HTTP. Authentication
requirements for HTTP are covered in <a href="./rfc2616#section-11">Section 11 of [RFC2616]</a>.
The use of authentication mechanisms to prevent POSTing or editing by
unknown or unauthorized clients is RECOMMENDED but not required.
When authentication is not used, clients and servers are vulnerable
to trivial spoofing, denial-of-service, and defacement attacks.
However, in some contexts, this is an acceptable risk.
The type of authentication deployed is a local decision made by the
server operator. Clients are likely to face authentication schemes
that vary across server deployments. At a minimum, client and server
implementations MUST be capable of being configured to use HTTP Basic
Authentication [<a href="./rfc2617" title=""HTTP Authentication: Basic and Digest Access Authentication"">RFC2617</a>] in conjunction with a connection made with
TLS 1.0 [<a href="./rfc2246" title=""The TLS Protocol Version 1.0"">RFC2246</a>] or a subsequent standards-track version of TLS
(such as [<a href="./rfc4346" title=""The Transport Layer Security (TLS) Protocol Version 1.1"">RFC4346</a>]), supporting the conventions for using HTTP over
TLS described in [<a href="./rfc2818" title=""HTTP Over TLS"">RFC2818</a>].
<span class="grey">Gregorio & de hOra Standards Track [Page 36]</span><span id="page-37" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
The choice of authentication mechanism will impact interoperability.
The minimum level of security referenced above (Basic Authentication
with TLS) is considered good practice for Internet applications at
the time of publication of this specification and sufficient for
establishing a baseline for interoperability. Implementers are
encouraged to investigate and use alternative mechanisms regarded as
equivalently good or better at the time of deployment. It is
RECOMMENDED that clients be implemented in such a way that new
authentication schemes can be deployed.
Because this protocol uses HTTP response status codes as the primary
means of reporting the result of a request, servers are advised to
respond to unauthorized or unauthenticated requests using an
appropriate 4xx HTTP response code (e.g., 401 "Unauthorized" or 403
"Forbidden") in accordance with [<a href="./rfc2617" title=""HTTP Authentication: Basic and Digest Access Authentication"">RFC2617</a>].
<span class="h2"><a class="selflink" id="section-15" href="#section-15">15</a>. Security Considerations</span>
The Atom Publishing Protocol is based on HTTP and thus subject to the
security considerations found in <a href="./rfc2616#section-15">Section 15 of [RFC2616]</a>.
The threats listed in this section apply to many protocols that run
under HTTP. The Atompub Working Group decided that the protection
afforded by running authenticated HTTP under TLS (as described in
<a href="#section-14">Section 14</a>) was sufficient to mitigate many of the problems presented
by the attacks listed in this section.
<span class="h3"><a class="selflink" id="section-15.1" href="#section-15.1">15.1</a>. Denial of Service</span>
Atom Publishing Protocol server implementations need to take adequate
precautions to ensure malicious clients cannot consume excessive
server resources (CPU, memory, disk, etc.).
<span class="h3"><a class="selflink" id="section-15.2" href="#section-15.2">15.2</a>. Replay Attacks</span>
Atom Publishing Protocol server implementations are susceptible to
replay attacks. Specifically, this specification does not define a
means of detecting duplicate requests. Accidentally sent duplicate
requests are indistinguishable from intentional and malicious replay
attacks.
<span class="h3"><a class="selflink" id="section-15.3" href="#section-15.3">15.3</a>. Spoofing Attacks</span>
Atom Publishing Protocol implementations are susceptible to a variety
of spoofing attacks. Malicious clients might send Atom Entries
containing inaccurate information anywhere in the document.
<span class="grey">Gregorio & de hOra Standards Track [Page 37]</span><span id="page-38" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h3"><a class="selflink" id="section-15.4" href="#section-15.4">15.4</a>. Linked Resources</span>
Atom Feed and Entry Documents can contain XML External Entities as
defined in Section 4.2.2 of [<a href="#ref-REC-xml" title=""Extensible Markup Language (XML) 1.0 (Fourth Edition)"">REC-xml</a>]. Atom implementations are not
required to load external entities. External entities are subject to
the same security concerns as any network operation and can alter the
semantics of an Atom document. The same issues exist for Resources
linked to by Atom elements such as atom:link and atom:content.
<span class="h3"><a class="selflink" id="section-15.5" href="#section-15.5">15.5</a>. Digital Signatures and Encryption</span>
Atom Entry and Feed Documents can contain XML Digital Signatures
[<a href="#ref-REC-xmldsig-core">REC-xmldsig-core</a>] and can be encrypted using XML Encryption
[<a href="#ref-REC-xmlenc-core">REC-xmlenc-core</a>] as specified in <a href="./rfc4287#section-5">Section 5 of [RFC4287]</a>. Handling
of signatures and encrypted elements in Atom documents is discussed
in Sections <a href="#section-5">5</a> and <a href="#section-6.3">6.3</a> of [<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>].
Neither servers nor clients are under any obligation to support
encryption and digital signature of Entries or Feeds, although it is
certainly possible that in some installations, clients or servers
might require signing or encrypting of the documents exchanged in the
Atom Protocol.
Because servers are allowed (and in some cases, expected) to modify
the contents of an Entry Document before publishing it, signatures
within an entry are only likely to be useful to the server to which
the entry is being sent. Clients cannot assume that the signature
will be valid when viewed by a third party, or even that the server
will publish the client's signature.
A server is allowed to strip client-applied signatures, to strip
client-applied signatures and then re-sign with its own public key,
and to oversign an entry with its own public key. The meaning to a
third party of a signature applied by a server is the same as a
signature from anyone, as described in [<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>]. It is RECOMMENDED
that a server that is aware that it has changed any part of an Entry
Document that was signed by the client should strip that signature
before publishing the entry in order to prevent third parties from
trying to interpret a signature that cannot be validated.
<span class="h3"><a class="selflink" id="section-15.6" href="#section-15.6">15.6</a>. URIs and IRIs</span>
Atom Publishing Protocol implementations handle URIs and IRIs. See
<a href="./rfc3986#section-7">Section 7 of [RFC3986]</a> and <a href="./rfc3987#section-8">Section 8 of [RFC3987]</a> for security
considerations related to their handling and use.
<span class="grey">Gregorio & de hOra Standards Track [Page 38]</span><span id="page-39" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
The Atom Publishing Protocol leaves the server in control of minting
URIs. The use of any client-supplied data for creating new URIs is
subject to the same concerns as described in the next section.
<span class="h3"><a class="selflink" id="section-15.7" href="#section-15.7">15.7</a>. Code Injection and Cross Site Scripting</span>
Atom Feed and Entry Documents can contain a broad range of content
types including code that might be executable in some contexts.
Malicious clients could attempt to attack servers or other clients by
injecting code into a Collection Document's Entry or Media Resources.
Server implementations are strongly encouraged to verify that client-
supplied content is safe prior to accepting, processing, or
publishing it. In the case of HTML, experience indicates that
verification based on a white list of acceptable content is more
effective than a black list of forbidden content.
Additional information about XHTML and HTML content safety can be
found in <a href="./rfc4287#section-8.1">Section 8.1 of [RFC4287]</a>.
<span class="h2"><a class="selflink" id="section-16" href="#section-16">16</a>. IANA Considerations</span>
This specification uses two new media types that conform to the
registry mechanism described in [<a href="./rfc4288" title=""Media Type Specifications and Registration Procedures"">RFC4288</a>], a new message header that
conforms to the registry mechanism described in [<a href="./rfc3864" title=""Registration Procedures for Message Header Fields"">RFC3864</a>], and two
new link relations that conform to the registry mechanism described
in [<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>].
<span class="h3"><a class="selflink" id="section-16.1" href="#section-16.1">16.1</a>. Content-Type Registration for 'application/atomcat+xml'</span>
An Atom Publishing Protocol Category Document, when serialized as XML
1.0, can be identified with the following media type:
MIME media type name: application
MIME subtype name: atomcat+xml
Required parameters: None.
Optional parameters:
"charset": This parameter has identical semantics to the charset
parameter of the "application/xml" media type as specified in
[<a href="./rfc3023" title=""XML Media Types"">RFC3023</a>].
Encoding considerations: Identical to those of "application/xml" as
described in <a href="./rfc3023#section-3.2">[RFC3023], Section 3.2</a>.
<span class="grey">Gregorio & de hOra Standards Track [Page 39]</span><span id="page-40" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
Security considerations: As defined in <a href="./rfc5023">RFC 5023</a>.
In addition, as this media type uses the "+xml" convention, it
shares the same security considerations as described in <a href="./rfc3023#section-10">[RFC3023],
Section 10</a>.
Interoperability considerations: There are no known interoperability
issues.
Published specification: <a href="./rfc5023">RFC 5023</a>.
Applications that use this media type: No known applications
currently use this media type.
Additional information:
Magic number(s): As specified for "application/xml" in <a href="./rfc3023#section-3.2">[RFC3023],
Section 3.2</a>.
File extension: .atomcat
Fragment identifiers: As specified for "application/xml" in
<a href="./rfc3023#section-5">[RFC3023], Section 5</a>.
Base URI: As specified in <a href="./rfc3023#section-6">[RFC3023], Section 6</a>.
Macintosh file type code: TEXT
Person & email address to contact for further information:
Joe Gregorio <joe@bitworking.org>
Intended usage: COMMON
Author/Change controller: IETF ([email protected]) Internet Engineering
Task Force
<span class="h3"><a class="selflink" id="section-16.2" href="#section-16.2">16.2</a>. Content-Type Registration for 'application/atomsvc+xml'</span>
An Atom Publishing Protocol Service Document, when serialized as XML
1.0, can be identified with the following media type:
MIME media type name: application
MIME subtype name: atomsvc+xml
Required parameters: None.
<span class="grey">Gregorio & de hOra Standards Track [Page 40]</span><span id="page-41" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
Optional parameters:
"charset": This parameter has identical semantics to the charset
parameter of the "application/xml" media type as specified in
[<a href="./rfc3023" title=""XML Media Types"">RFC3023</a>].
Encoding considerations: Identical to those of "application/xml" as
described in <a href="./rfc3023#section-3.2">[RFC3023], Section 3.2</a>.
Security considerations: As defined in <a href="./rfc5023">RFC 5023</a>.
In addition, as this media type uses the "+xml" convention, it
shares the same security considerations as described in <a href="./rfc3023#section-10">[RFC3023],
Section 10</a>.
Interoperability considerations: There are no known interoperability
issues.
Published specification: <a href="./rfc5023">RFC 5023</a>.
Applications that use this media type: No known applications
currently use this media type.
Additional information:
Magic number(s): As specified for "application/xml" in <a href="./rfc3023#section-3.2">[RFC3023],
Section 3.2</a>.
File extension: .atomsvc
Fragment identifiers: As specified for "application/xml" in
<a href="./rfc3023#section-5">[RFC3023], Section 5</a>.
Base URI: As specified in <a href="./rfc3023#section-6">[RFC3023], Section 6</a>.
Macintosh file type code: TEXT
Person and email address to contact for further information: Joe
Gregorio <joe@bitworking.org>
Intended usage: COMMON
Author/Change controller: IETF ([email protected]) Internet Engineering
Task Force
<span class="grey">Gregorio & de hOra Standards Track [Page 41]</span><span id="page-42" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h3"><a class="selflink" id="section-16.3" href="#section-16.3">16.3</a>. Header Field Registration for 'SLUG'</span>
Header field name: SLUG
Applicable protocol: http [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>]
Status: standard.
Author/Change controller: IETF ([email protected]) Internet Engineering
Task Force
Specification document(s): <a href="./rfc5023">RFC 5023</a>.
Related information: None.
<span class="h3"><a class="selflink" id="section-16.4" href="#section-16.4">16.4</a>. The Link Relation Registration "edit"</span>
Attribute Value: edit
Description: An IRI of an editable Member Entry. When appearing
within an atom:entry, the href IRI can be used to retrieve,
update, and delete the Resource represented by that Entry.
Expected display characteristics: Undefined; this relation can be
used for background processing or to provide extended
functionality without displaying its value.
Security considerations: Automated agents should take care when this
relation crosses administrative domains (e.g., the URI has a
different authority than the current document).
<span class="h3"><a class="selflink" id="section-16.5" href="#section-16.5">16.5</a>. The Link Relation Registration "edit-media"</span>
Attribute Value: edit-media
Description: An IRI of an editable Media Resource. When appearing
within an atom:entry, the href IRI can be used to retrieve,
update, and delete the Media Resource associated with that Entry.
Expected display characteristics: Undefined; this relation can be
used for background processing or to provide extended
functionality without displaying its value.
Security considerations: Automated agents should take care when this
relation crosses administrative domains (e.g., the URI has a
different authority than the current document).
<span class="grey">Gregorio & de hOra Standards Track [Page 42]</span><span id="page-43" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h3"><a class="selflink" id="section-16.6" href="#section-16.6">16.6</a>. The Atom Format Media Type Parameter</span>
IANA has added a reference to this specification in the
'application/atom+xml' media type registration.
<span class="h2"><a class="selflink" id="section-17" href="#section-17">17</a>. References</span>
<span class="h3"><a class="selflink" id="section-17.1" href="#section-17.1">17.1</a>. Normative References</span>
[<a id="ref-REC-xml">REC-xml</a>] Yergeau, F., Paoli, J., Bray, T., Sperberg-McQueen, C.,
and E. Maler, "Extensible Markup Language (XML) 1.0
(Fourth Edition)", World Wide Web Consortium
Recommendation REC-xml-20060816, August 2006,
<<a href="http://www.w3.org/TR/2006/REC-xml-20060816">http://www.w3.org/TR/2006/REC-xml-20060816</a>>.
[<a id="ref-REC-xml-infoset">REC-xml-infoset</a>]
Cowan, J. and R. Tobin, "XML Information Set (Second
Edition)", World Wide Web Consortium Recommendation REC-
xml-infoset-20040204, February 2004,
<<a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204">http://www.w3.org/TR/2004/REC-xml-infoset-20040204</a>>.
[<a id="ref-REC-xml-names">REC-xml-names</a>]
Hollander, D., Bray, T., Tobin, R., and A. Layman,
"Namespaces in XML 1.0 (Second Edition)", World Wide Web
Consortium Recommendation REC-xml-names-20060816, August
2006, <<a href="http://www.w3.org/TR/2006/REC-xml-names-20060816">http://www.w3.org/TR/2006/REC-xml-names-20060816</a>>.
[<a id="ref-REC-xmlbase">REC-xmlbase</a>]
Marsh, J., "XML Base", W3C REC W3C.REC-xmlbase-20010627,
June 2001,
<<a href="http://www.w3.org/TR/2001/REC-xmlbase-20010627">http://www.w3.org/TR/2001/REC-xmlbase-20010627</a>>.
[<a id="ref-REC-xmldsig-core">REC-xmldsig-core</a>]
Solo, D., Reagle, J., and D. Eastlake, "XML-Signature
Syntax and Processing", World Wide Web Consortium
Recommendation REC-xmldsig-core-20020212, February 2002,
<<a href="http://www.w3.org/TR/2002/REC-xmldsig-core-20020212">http://www.w3.org/TR/2002/REC-xmldsig-core-20020212</a>>.
[<a id="ref-REC-xmlenc-core">REC-xmlenc-core</a>]
Eastlake, D. and J. Reagle, "XML Encryption Syntax and
Processing", World Wide Web Consortium Recommendation REC-
xmlenc-core-20021210, December 2002,
<<a href="http://www.w3.org/TR/2002/REC-xmlenc-core-20021210">http://www.w3.org/TR/2002/REC-xmlenc-core-20021210</a>>.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
<span class="grey">Gregorio & de hOra Standards Track [Page 43]</span><span id="page-44" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
[<a id="ref-RFC2246">RFC2246</a>] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0",
<a href="./rfc2246">RFC 2246</a>, January 1999.
[<a id="ref-RFC2616">RFC2616</a>] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", <a href="./rfc2616">RFC 2616</a>, June 1999.
[<a id="ref-RFC2617">RFC2617</a>] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S.,
Leach, P., Luotonen, A., and L. Stewart, "HTTP
Authentication: Basic and Digest Access Authentication",
<a href="./rfc2617">RFC 2617</a>, June 1999.
[<a id="ref-RFC2818">RFC2818</a>] Rescorla, E., "HTTP Over TLS", <a href="./rfc2818">RFC 2818</a>, May 2000.
[<a id="ref-RFC3023">RFC3023</a>] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", <a href="./rfc3023">RFC 3023</a>, January 2001.
[<a id="ref-RFC3629">RFC3629</a>] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, <a href="./rfc3629">RFC 3629</a>, November 2003.
[<a id="ref-RFC3864">RFC3864</a>] Klyne, G., Nottingham, M., and J. Mogul, "Registration
Procedures for Message Header Fields", <a href="https://www.rfc-editor.org/bcp/bcp90">BCP 90</a>, <a href="./rfc3864">RFC 3864</a>,
September 2004.
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, <a href="./rfc3986">RFC</a>
<a href="./rfc3986">3986</a>, January 2005.
[<a id="ref-RFC3987">RFC3987</a>] Duerst, M. and M. Suignard, "Internationalized Resource
Identifiers (IRIs)", <a href="./rfc3987">RFC 3987</a>, January 2005.
[<a id="ref-RFC4287">RFC4287</a>] Nottingham, M. and R. Sayre, "The Atom Syndication
Format", <a href="./rfc4287">RFC 4287</a>, December 2005.
[<a id="ref-RFC4288">RFC4288</a>] Freed, N. and J. Klensin, "Media Type Specifications and
Registration Procedures", <a href="https://www.rfc-editor.org/bcp/bcp13">BCP 13</a>, <a href="./rfc4288">RFC 4288</a>, December 2005.
[<a id="ref-RFC4346">RFC4346</a>] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.1", <a href="./rfc4346">RFC 4346</a>, April 2006.
<span class="h3"><a class="selflink" id="section-17.2" href="#section-17.2">17.2</a>. Informative References</span>
[<a id="ref-NOTE-detect-lost-update">NOTE-detect-lost-update</a>]
Nielsen, H. and D. LaLiberte, "Editing the Web: Detecting
the Lost Update Problem Using Unreserved Checkout", World
Wide Web Consortium NOTE NOTE-detect-lost-update, May
1999, <<a href="http://www.w3.org/1999/04/Editing/">http://www.w3.org/1999/04/Editing/</a>>.
<span class="grey">Gregorio & de hOra Standards Track [Page 44]</span><span id="page-45" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
[<a id="ref-REC-webarch">REC-webarch</a>]
Walsh, N. and I. Jacobs, "Architecture of the World Wide
Web, Volume One", W3C REC REC-webarch-20041215, December
2004, <<a href="http://www.w3.org/TR/2004/REC-webarch-20041215">http://www.w3.org/TR/2004/REC-webarch-20041215</a>>.
[<a id="ref-RNC">RNC</a>] Clark, J., "RELAX NG Compact Syntax", December 2001,
<<a href="http://www.oasis-open.org/committees/relax-ng/compact-20021121.html">http://www.oasis-open.org/committees/relax-ng/</a>
<a href="http://www.oasis-open.org/committees/relax-ng/compact-20021121.html">compact-20021121.html</a>>.
<span class="grey">Gregorio & de hOra Standards Track [Page 45]</span><span id="page-46" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Contributors</span>
The content and concepts within are a product of the Atom community
and the Atompub Working Group.
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. RELAX NG Compact Schema</span>
This appendix is informative.
The Relax NG schema explicitly excludes elements in the Atom Protocol
namespace that are not defined in this revision of the specification.
Requirements for Atom Protocol processors encountering such markup
are given in Sections <a href="#section-6.2">6.2</a> and <a href="#section-6.3">6.3</a> of [<a href="./rfc4287" title=""The Atom Syndication Format"">RFC4287</a>].
The Schema for Service Documents:
# -*- rnc -*- # RELAX NG Compact Syntax Grammar for the Atom Protocol
namespace app = "<a href="http://www.w3.org/2007/app">http://www.w3.org/2007/app</a>"
namespace atom = "<a href="http://www.w3.org/2005/Atom">http://www.w3.org/2005/Atom</a>"
namespace xsd = "<a href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</a>"
namespace xhtml = "<a href="http://www.w3.org/1999/xhtml">http://www.w3.org/1999/xhtml</a>"
namespace local = ""
start = appService
# common:attrs
atomURI = text
appCommonAttributes =
attribute xml:base { atomURI }?,
attribute xml:lang { atomLanguageTag }?,
attribute xml:space {"default"|"preserved"}?,
undefinedAttribute*
atomCommonAttributes = appCommonAttributes
undefinedAttribute = attribute * - (xml:base | xml:space | xml:lang
| local:*) { text }
atomLanguageTag = xsd:string {
pattern = "([A-Za-z]{1,8}(-[A-Za-z0-9]{1,8})*)?"
}
<span class="grey">Gregorio & de hOra Standards Track [Page 46]</span><span id="page-47" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
atomDateConstruct =
appCommonAttributes,
xsd:dateTime
# app:service
appService =
element app:service {
appCommonAttributes,
( appWorkspace+
& extensionElement* )
}
# app:workspace
appWorkspace =
element app:workspace {
appCommonAttributes,
( atomTitle
& appCollection*
& extensionSansTitleElement* )
}
atomTitle = element atom:title { atomTextConstruct }
# app:collection
appCollection =
element app:collection {
appCommonAttributes,
attribute href { atomURI },
( atomTitle
& appAccept*
& appCategories*
& extensionSansTitleElement* )
}
# app:categories
atomCategory =
element atom:category {
atomCommonAttributes,
attribute term { text },
attribute scheme { atomURI }?,
attribute label { text }?,
undefinedContent
}
<span class="grey">Gregorio & de hOra Standards Track [Page 47]</span><span id="page-48" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
appInlineCategories =
element app:categories {
attribute fixed { "yes" | "no" }?,
attribute scheme { atomURI }?,
(atomCategory*,
undefinedContent)
}
appOutOfLineCategories =
element app:categories {
attribute href { atomURI },
undefinedContent
}
appCategories = appInlineCategories | appOutOfLineCategories
# app:accept
appAccept =
element app:accept {
appCommonAttributes,
( text? )
}
# Simple Extension
simpleSansTitleExtensionElement =
element * - (app:*|atom:title) {
text
}
simpleExtensionElement =
element * - (app:*) {
text
}
# Structured Extension
structuredSansTitleExtensionElement =
element * - (app:*|atom:title) {
(attribute * { text }+,
(text|anyElement)*)
| (attribute * { text }*,
(text?, anyElement+, (text|anyElement)*))
}
<span class="grey">Gregorio & de hOra Standards Track [Page 48]</span><span id="page-49" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
structuredExtensionElement =
element * - (app:*) {
(attribute * { text }+,
(text|anyElement)*)
| (attribute * { text }*,
(text?, anyElement+, (text|anyElement)*))
}
# Other Extensibility
extensionSansTitleElement =
simpleSansTitleExtensionElement|structuredSansTitleExtensionElement
extensionElement = simpleExtensionElement |
structuredExtensionElement
undefinedContent = (text|anyForeignElement)*
# Extensions
anyElement =
element * {
(attribute * { text }
| text
| anyElement)*
}
anyForeignElement =
element * - app:* {
(attribute * { text }
| text
| anyElement)*
}
atomPlainTextConstruct =
atomCommonAttributes,
attribute type { "text" | "html" }?,
text
atomXHTMLTextConstruct =
atomCommonAttributes,
attribute type { "xhtml" },
xhtmlDiv
atomTextConstruct = atomPlainTextConstruct | atomXHTMLTextConstruct
<span class="grey">Gregorio & de hOra Standards Track [Page 49]</span><span id="page-50" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
anyXHTML = element xhtml:* {
(attribute * { text }
| text
| anyXHTML)*
}
xhtmlDiv = element xhtml:div {
(attribute * { text }
| text
| anyXHTML)*
}
# EOF
The Schema for Category Documents:
# -*- rnc -*- # RELAX NG Compact Syntax Grammar for the Atom Protocol
namespace app = "<a href="http://www.w3.org/2007/app">http://www.w3.org/2007/app</a>"
namespace atom = "<a href="http://www.w3.org/2005/Atom">http://www.w3.org/2005/Atom</a>"
namespace xsd = "<a href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</a>"
namespace local = ""
start = appCategories
atomCommonAttributes =
attribute xml:base { atomURI }?,
attribute xml:lang { atomLanguageTag }?,
undefinedAttribute*
undefinedAttribute = attribute * - (xml:base | xml:lang | local:*) {
text }
atomURI = text
atomLanguageTag = xsd:string {
pattern = "([A-Za-z]{1,8}(-[A-Za-z0-9]{1,8})*)?"
}
atomCategory =
element atom:category {
atomCommonAttributes,
attribute term { text },
attribute scheme { atomURI }?,
attribute label { text }?,
undefinedContent
}
<span class="grey">Gregorio & de hOra Standards Track [Page 50]</span><span id="page-51" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
appInlineCategories =
element app:categories {
attribute fixed { "yes" | "no" }?,
attribute scheme { atomURI }?,
(atomCategory*,
undefinedContent)
}
appOutOfLineCategories =
element app:categories {
attribute href { atomURI },
(empty)
}
appCategories = appInlineCategories | appOutOfLineCategories
# Extensibility
undefinedContent = (text|anyForeignElement)*
anyElement =
element * {
(attribute * { text }
| text
| anyElement)*
}
anyForeignElement =
element * - atom:* {
(attribute * { text }
| text
| anyElement)*
}
# EOF
<span class="grey">Gregorio & de hOra Standards Track [Page 51]</span><span id="page-52" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
Authors' Addresses
Joe Gregorio (editor)
Google
EMail: [email protected]
URI: <a href="http://bitworking.org/">http://bitworking.org/</a>
Bill de hOra (editor)
NewBay Software
EMail: [email protected]
URI: <a href="http://dehora.net/">http://dehora.net/</a>
<span class="grey">Gregorio & de hOra Standards Track [Page 52]</span><span id="page-53" ></span>
<span class="grey"><a href="./rfc5023">RFC 5023</a> The Atom Publishing Protocol October 2007</span>
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
[email protected].
Gregorio & de hOra Standards Track [Page 53]
Annotations
Select text to annotate