| CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 13:56:50 GMT
content-type: text/plain; charset=utf-8
content-length: 2425
cf-ray: 98be6232e80695be-BLR
last-modified: Fri, 06 Apr 2012 20:40:36 GMT
etag: "1d44-4bd08ab2bb900-gzip"
vary: Accept-Encoding
content-encoding: gzip
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: HIT
expires: Thu, 09 Oct 2025 14:16:50 GMT
cache-control: public, max-age=1200
accept-ranges: bytes
set-cookie: __cf_bm=qPBgF7oRsH2yqQH06TY5LHon8BO5rS.YPoU82ADJeeY-1760018210-1.0.1.1-0Tvj3OCvS50RE.4H_qIktOP2NXf3ZpmuTCLkhYtp2W0SVjI76jflLo6gXVhQ7wzg4x272lBlgqz8Lz7jDVONOt_N9E4dtcNRJAP9NxB9qDU; path=/; expires=Thu, 09-Oct-25 14:26:50 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
alt-svc: h3=":443"; ma=86400
Internet Engineering Task Force (IETF) M. Amundsen
Request for Comments: 6573 April 2012
Category: Informational
ISSN: 2070-1721
The Item and Collection Link Relations
Abstract
RFC 5988 standardized a means of indicating the relationships between
resources on the Web. This specification defines a pair of reciprocal
link relation types that may be used to express the relationship
between a collection and its members.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc6573.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Amundsen Informational [Page 1]
RFC 6573 The Item and Collection Link Relations April 2012
1. Introduction
RFC 5988 standardized a means of indicating the relationships between
resources on the Web. This specification defines a pair of reciprocal
link relation types that may be used to express the relationship
between a collection and its members.
These link relation types can be applied to a wide range of use cases
across multiple media types. For example, the 'collection' and
'item' link relation types are used in these media types:
1. OpenSearch 1.1: see Section 4.5.4.1 of [OpenSearch]
2. Maze+XML: see [Maze]
3. Collection+JSON: see [CollectionJSON]
2. Link Relations
The following link relations are defined.
2.1. 'item'
When included in a resource that represents a collection, the 'item'
link relation identifies a target resource that represents a member
of that collection.
For example, if a resource represents a catalog of products, that
same representation may include one or more links to resources that
represent members of that catalog.
...
.
Amundsen Informational [Page 4]
RFC 6573 The Item and Collection Link Relations April 2012
[Maze] Amundsen, M., "Maze+XML - Format", Web Page ,
December 2010,
.
[OpenSearch] Clinton, D., "Open Search 1.1", Work in Progress ,
March 2011,