< draft-amundsen-item-and-collection-link-relations-04.txt		draft-amundsen-item-and-collection-link-relations-05.txt >
	Network Working Group M. Amundsen		Network Working Group M. Amundsen
	Internet-Draft October 9, 2011		Internet-Draft February 5, 2012
	Intended status: Informational		Intended status: Informational
	Expires: April 11, 2012		Expires: August 8, 2012
	The Item and Collection Link Relations		The Item and Collection Link Relations
	draft-amundsen-item-and-collection-link-relations-04		draft-amundsen-item-and-collection-link-relations-05
	Abstract		Abstract
	RFC 5988 [RFC5988] standardized a means of indicating the		RFC 5988 standardized a means of indicating the relationships between
	relationships between resources on the Web. This specification		resources on the Web. This specification defines a pair of reciprocal
	defines a pair of reciprocal link relation types that may be used to		link relation types that may be used to express the relationship
	express the relationship between a collection and its members.		between a collection and its members.
	Editorial Note (To be removed by RFC Editor)		Editorial Note (To be removed by RFC Editor)
	Distribution of this document is unlimited. Comments should be sent		Distribution of this document is unlimited. Comments should be sent
	to the IETF Apps-Discuss mailing list (see		to the IETF Apps-Discuss mailing list (see
	<https://www.ietf.org/mailman/listinfo/apps-discuss>).		<https://www.ietf.org/mailman/listinfo/apps-discuss>).
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF). Note that other groups may also distribute
	other groups may also distribute working documents as Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		This Internet-Draft will expire on August 8, 2012.
	http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on April 11, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 IETF Trust and the persons identified as the		Copyright (c) 2012 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the BSD License.		described in the Simplified BSD License.
	1. Introduction		1. Introduction
	RFC 5988 [RFC5988] standardized a means of indicating the		RFC 5988 standardized a means of indicating the relationships between
	relationships between resources on the Web. This specification		resources on the Web. This specification defines a pair of reciprocal
	defines a pair of reciprocal link relation types that may be used to		link relation types that may be used to express the relationship
	express the relationship between a collection and its members.		between a collection and its members.
	These link relation types can be applied to a wide range of use cases		These link relation types can be applied to a wide range of use cases
	across multiple media types. For example, the 'collection' and		across multiple media types. For example, the 'collection' and
	'item' link relation types are used in these media types:		'item' link relation types are used in these media types:
	1. OpenSearch 1.1: see Section 4.5.4.1 of [OpenSearch]		1. OpenSearch 1.1: see Section 4.5.4.1 of [OpenSearch]
	2. Maze+XML: see Section 3 of [Maze]		2. Maze+XML: see Section 3 of [Maze]
	3. Collection+JSON: see Section 5 of [CollectionJSON]		3. Collection+JSON: see Section 5 of [CollectionJSON]
	skipping to change at page 4, line 5 ¶		skipping to change at page 3, line 38 ¶
	<a href="..." rel="collection">View other widgets</a>		<a href="..." rel="collection">View other widgets</a>
	<a href="..." rel="collection">View all discontinued items</a>		<a href="..." rel="collection">View all discontinued items</a>
	The target resource representation need not be restricted to		The target resource representation need not be restricted to
	representing a list. It may simply be a document that provides		representing a list. It may simply be a document that provides
	details on the collection of which the context resource is a member:		details on the collection of which the context resource is a member:
	Link: <...>; rel="collection";		Link: <...>; rel="collection";
	title="Shakespeare's Collected Works - A History"		title="Shakespeare's Collected Works - A History"
			It should also be noted that that same link might represent an 'item'
			in one collection as well as a 'collection' itself. In this case
			both Link Relation values can be applied to the same link:
			Link: <...>; rel="collection item";
			title="A Review of Issac Asimov's Collected Works - Vol. I"
	3. IANA Considerations		3. IANA Considerations
	IANA is asked to register the 'collection' and 'item' Link Relations		IANA is asked to register the 'collection' and 'item' Link Relations
	below as per [RFC5988].		below as per [RFC5988].
	3.1. 'item' Link Relation Registration		3.1. 'item' Link Relation Registration
	Relation Name:		Relation Name:
	item		item
	skipping to change at page 4, line 42 ¶		skipping to change at page 4, line 37 ¶
	The target IRI points to a resource which represents a collection		The target IRI points to a resource which represents a collection
	of which the context IRI is a member.		of which the context IRI is a member.
	Reference:		Reference:
	See Section 2		See Section 2
	4. Security Considerations		4. Security Considerations
	The two link relation types defined in this document are not believed		The two link relation types defined in this document do not introduce
	to introduce any new security issues to those which are discussed in		any new security issues to those which are discussed in Section 7 of
	Section 7 of RFC5988 [RFC5988].		RFC5988 [RFC5988].
	5. Internationalisation Considerations		5. Internationalisation Considerations
	The 'item' and 'collection' link relation types do not have any		The 'item' and 'collection' link relation types do not have any
	internationalization considerations other than those which are		internationalization considerations other than those which are
	discussed in Section 8 of RFC5988 [RFC5988].		discussed in Section 8 of RFC5988 [RFC5988].
	6. References		6. References
	6.1. Normative References		6.1. Normative References
	[RFC5988] Nottingham, M., "Web Linking", RFC 5988,		[RFC5988] Nottingham, M., "Web Linking", RFC 5988,
	October 2010.		October 2010.
	6.2. Informative References		6.2. Informative References
	[OpenSearch] Clinton, D., "Open Search 1.1", Work in Progress ,		[OpenSearch] Clinton, D., "Open Search 1.1", Work in Progress ,
	March 2011, <http://www.opensearch.org/		March 2011, <http://www.opensearch.org/
	Specifications/OpenSearch/1.1/>.		Specifications/OpenSearch/1.1/>.
End of changes. 13 change blocks.
	27 lines changed or deleted		29 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/