Atom Link Relations
Last Updated
2009-01-26
This registry is also available in XML and plain text formats.
Registry included below
* Atom Link Relations
Atom Link Relations
Reference
[RFC4287]
Registration Procedures
IESG Approval (via request to IANA)
Registration
Value Description Expected Display Characteristics Security Considerations Reference Date (if
applicable)
alternate [RFC4287]
A URI that,
when
dereferenced, Undefined; this relation can be Automated agents should take care when this
returns a feed used for background processing or relation crosses administrative domains
current document to provide extended functionality (e.g., the URI has a different authority [RFC5005] 2006-02-02
containing the without displaying its value. than the current document).
most recent
entries in the
feed.
The
relationship A
'describedby'
B asserts that
resource B Descriptions of resources may be socially
provides a sensitive, may require processing to be
description of understood and may or may not not be
resource A. accurate. Consumers of descriptive resources
There are no should be aware of the source and chain of
describedby constraints on None custody of the data. Security considerations [Phil_Archer][http://www.w3.org/TR/powder-dr/#assoc-linking] 2009-02-20
the format or for URIs (Section 7 of RFC 3986) and IRIs
representation (Section 8 of RFC 3987 ) apply to the extent
of either A or that describing resources may affect
B, neither are consumers' decisions about how or whether to
there any retrieve those resources.
further
constraints on
either
resource.
An IRI of an
editable
Member Entry.
When appearing
within an
atom:entry, Undefined; this relation can be Automated agents should take care when this
edit the href IRI used for background processing or relation crosses administrative domains [RFC5023] 2007-07-27
can be used to to provide extended functionality (e.g., the URI has a different authority
retrieve, without displaying its value. than the current document).
update and
delete the
Resource
represented by
that Entry.
An IRI of an
editable Media
Resource. When
appearing
within an
atom:entry, Undefined; this relation can be Automated agents should take care when this
the href IRI used for background processing or relation crosses administrative domains
edit-media can be used to to provide extended functionality (e.g., the URI has a different authority [RFC5023] 2007-07-27
retrieve, without displaying its value. than the current document).
update and
delete the
Media Resource
associated
with that
Entry.
enclosure [RFC4287]
A URI that Automated agents should take care when this
refers to the Undefined; this relation can be relation crosses administrative domains
furthest used for background processing or (e.g., the URI has a different authority
first preceding to provide extended functionality than the current document). Such agents [Mark Nottingham, December 2004] 2006-02-02
document in a without displaying its value. should also take care to detect circular
series of references.
documents.
A URI for a
hub that
enables
hub registration [Brett_Slatkin][http://pubsubhubbub.googlecode.com] 2009-11-20
for real-time
updates to the
resource
A URI that Automated agents should take care when this
refers to the Undefined; this relation can be relation crosses administrative domains
furthest used for background processing or (e.g., the URI has a different authority
last following to provide extended functionality than the current document). Such agents [Mark Nottingham, December 2004] 2006-02-02
document in a without displaying its value. should also take care to detect circular
series of references.
documents.
When included
on a versioned
resource, this
link points to
a resource
containing the
latest (e.g.,
current)
version. The Automated agents should take care when these
latest version relations cross administrative domains
is defined by (e.g., the URI has a different authority
the system. than the current document). Such agents
For linear should also take care to detect circular
versioning references. Care should be applied when
systems, this versioned resources are subject to differing
is probably Undefined; this relation can be access policies. In this case, exposing
latest-version the latest used for background processing or links may leak information even if the [RFC-brown-versioning-link-relations-07]
version by to provide extended functionality linked resource itself is properly secured.
timestamp. For without displaying its value. In particular, the syntax of the link
systems that URI/IRI could expose sensitive information
support (see Section 16.2 of [RFC3253] for a similar
branching, consideration in WebDAV Versioning). Note
there will be that this applies to exposing link metadata
multiple in general, not only to links related to
latest versioning.
versions, one
for each
branch in the
version
history. Some
systems may
allow multiple
of these link
relations.
license [RFC4946] 2007-05-14
A URI that Automated agents should take care when this
refers to the Undefined; this relation can be relation crosses administrative domains
immediately used for background processing or (e.g., the URI has a different authority
next following to provide extended functionality than the current document). Such agents [RFC5005] 2006-02-02
document in a without displaying its value. should also take care to detect circular
series of references.
documents.
A URI that
refers to the
next-archive immediately See [RFC5005] 2007-07-13
following [RFC-nottingham-atompub-feed-history-11.txt]
archive
document.
rel="payment"
indicates a
URI where
payment is
accepted. It
is meant as a
general way to
facilitate
acts of
payment, and
thus this
specification
makes no
assumptions on
the type of
payment or
transaction
protocol.
Examples may
include a WWW
page where
donations are
accepted or
where goods
and services End-user software could support
are available rel="payment" by displaying a The link element is subject to tampering and
for purchase. "payment button" along with the observation, as is the linked resource. For
rel="payment" content. Alternatively, content that reason, implementations should clearly
is not aggregators may display a payment signal the level trust and privacy a linked
intended to hyperlink containing the text resource provides. If present, digital
initiate an specified in a corresponding title signatures provide authentication, message
payment automated attribute within the integrity, and non-repudiation with proof of [Joshua_Kinberg][Robert_Sayre] 2006-02-02
transaction. A element, for example: May message integrity provided by the transport
attribute may display either a payment button or used to reach the payment resource.
exist at the a hyperlink containing the text,
feed/channel "give me the loot."
level and/or
the entry/item
level. For
example, a
rel="payment"
link at the
feed/channel
level may
point to a
"tip jar" URI,
whereas an
entry/item
containing a
book review
may include a
rel="payment"
link that
points to the
location where
the book may
be purchased
through an
online
retailer.
When included Automated agents should take care when these
on a versioned relations cross administrative domains
resource, this (e.g., the URI has a different authority
link points to than the current document). Such agents
a resource should also take care to detect circular
containing the references. Care should be applied when
predecessor versioned resources are subject to differing
version in the Undefined; this relation can be access policies. In this case, exposing
predecessor-version version used for background processing or links may leak information even if the [RFC-brown-versioning-link-relations-07]
history. Some to provide extended functionality linked resource itself is properly secured.
systems may without displaying its value. In particular, the syntax of the link
allow multiple URI/IRI could expose sensitive information
of these link (see Section 16.2 of [RFC3253] for a similar
relations in consideration in WebDAV Versioning). Note
the case of a that this applies to exposing link metadata
multiple in general, not only to links related to
branches versioning.
merging.
A URI that
refers to the
prev-archive immediately See [RFC5005] 2007-07-13
preceding [RFC-nottingham-atompub-feed-history-11.txt]
archive
document.
A URI that Automated agents should take care when this
refers to the Undefined; this relation can be relation crosses administrative domains
immediately used for background processing or (e.g., the URI has a different authority
previous preceding to provide extended functionality than the current document). Such agents [RFC5005] 2006-02-02
document in a without displaying its value. should also take care to detect circular
series of references.
documents.
related [RFC4287]
replies [RFC4685] 2006-06-28
self [RFC4287]
rel="service" Support for rel="service" links The link element is subject to tampering and
indicates a will vary across user agent observation, as is the linked resource. For
URI that can implementations. The link relation that reason, implementations should clearly
be used to is intended to provide user agents signal the level trust and privacy a linked
retrieve an with a means of auto-discovering resource provides. If present, digital
service Atom service endpoints so that basic signatures provide authentication, message [James_Snell] 2008-05-20
Publishing configuration actions can be integrity, and non-repudiation with proof of
Protocol performed automatically with origin. Encryption provides data
Service minimal user input. User agents may confidentiality. Implementations should also
Document as or may not present the link to end consider the level of confidentiality and
defined by RFC users. message integrity provided by the transport
5023. used to reach the payment resource.
When included Automated agents should take care when these
on a versioned relations cross administrative domains
resource, this (e.g., the URI has a different authority
link points to than the current document). Such agents
a resource should also take care to detect circular
containing the references. Care should be applied when
successor Undefined; this relation can be versioned resources are subject to differing
version in the used for background processing or access policies. In this case, exposing
successor-version version to provide extended functionality links may leak information even if the [RFC-brown-versioning-link-relations-07]
history. Some without displaying its value. linked resource itself is properly secured.
systems may In particular, the syntax of the link
allow multiple URI/IRI could expose sensitive information
of these link (see Section 16.2 of [RFC3253] for a similar
relations in consideration in WebDAV Versioning). Note
order to that this applies to exposing link metadata
support in general, not only to links related to
branching. versioning.
A URI that Automated agents should take care when this
refers to a Undefined; this relation can be relation crosses administrative domains
up parent used for background processing or (e.g., the URI has a different authority [Noah_Slater] 2009-01-28
document in a to provide extended functionality than the current document). Such agents
hierarchy of without displaying its value. should also take care to detect circular
documents. references.
Automated agents should take care when these
relations cross administrative domains
(e.g., the URI has a different authority
than the current document). Such agents
When included should also take care to detect circular
on a versioned references. Care should be applied when
resource, this Undefined; this relation can be versioned resources are subject to differing
link points to used for background processing or access policies. In this case, exposing
version-history a resource to provide extended functionality links may leak information even if the [RFC-brown-versioning-link-relations-07]
containing the without displaying its value. linked resource itself is properly secured.
version In particular, the syntax of the link
history for URI/IRI could expose sensitive information
this resource. (see Section 16.2 of [RFC3253] for a similar
consideration in WebDAV Versioning). Note
that this applies to exposing link metadata
in general, not only to links related to
versioning.
via [RFC4287]
Automated agents should take care when these
relations cross administrative domains
(e.g., the URI has a different authority
When included than the current document). Such agents
on a versioned should also take care to detect circular
resource, this references. Care should be applied when
link points to Undefined; this relation can be versioned resources are subject to differing
a working copy used for background processing or access policies. In this case, exposing
working-copy for this to provide extended functionality links may leak information even if the [RFC-brown-versioning-link-relations-07]
resource. Some without displaying its value. linked resource itself is properly secured.
systems may In particular, the syntax of the link
allow multiple URI/IRI could expose sensitive information
of these link (see Section 16.2 of [RFC3253] for a similar
relations. consideration in WebDAV Versioning). Note
that this applies to exposing link metadata
in general, not only to links related to
versioning.
Automated agents should take care when these
relations cross administrative domains
(e.g., the URI has a different authority
than the current document). Such agents
When included should also take care to detect circular
on a working references. Care should be applied when
copy, this Undefined; this relation can be versioned resources are subject to differing
link points to used for background processing or access policies. In this case, exposing
working-copy-of the versioned to provide extended functionality links may leak information even if the [RFC-brown-versioning-link-relations-07]
resource from without displaying its value. linked resource itself is properly secured.
which this In particular, the syntax of the link
working copy URI/IRI could expose sensitive information
was obtained. (see Section 16.2 of [RFC3253] for a similar
consideration in WebDAV Versioning). Note
that this applies to exposing link metadata
in general, not only to links related to
versioning.
People
ID Name Contact URI Last Updated
[Brett_Slatkin] Brett Slatkin mailto:bslatkin&google.com 2009-11-20
[James_Snell] James Snell mailto:jasnell&gmail.com 2008-05-20
[Joshua_Kinberg] Joshua Kinberg mailto:jkinberg&gmail.com 2006-02
[Noah_Slater] Noah Slater mailto:nslater&tumbolia.org 2009-01-30
[Phil_Archer] Phil Archer mailto:phil&philarcher.org 2009-02-20
[Robert_Sayre] Robert Sayre mailto:sayrer&gmail.com 2006-02