Link Relation Types for Simple Version Navigation between Web Resources
RFC 5829
| Document | Type |
RFC - Informational
(April 2010; No errata)
Was draft-brown-versioning-link-relations (individual in app area)
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 5829 (Informational) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Lisa Dusseault | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) A. Brown
Request for Comments: 5829 G. Clemm
Category: Informational IBM
ISSN: 2070-1721 J. Reschke, Ed.
greenbytes
April 2010
Link Relation Types for Simple Version Navigation between Web Resources
Abstract
This specification defines a set of link relation types that may be
used on Web resources for navigation between a resource and other
resources related to version control, such as past versions and
working copies.
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
http://www.rfc-editor.org/info/rfc5829.
Copyright Notice
Copyright (c) 2010 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
(http://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.
Brown, et al. Informational [Page 1]
RFC 5829 Version Navigation Link Relations April 2010
Table of Contents
1. Introduction ....................................................3
2. Terminology .....................................................3
3. Link Relations ..................................................4
3.1. 'version-history' ..........................................4
3.2. 'latest-version' ...........................................4
3.3. 'working-copy' .............................................4
3.4. 'working-copy-of' ..........................................4
3.5. 'predecessor-version' ......................................4
3.6. 'successor-version' ........................................5
4. IANA Considerations .............................................5
4.1. 'version-history' Link Relation Registration ...............5
4.2. 'latest-version' Link Relation Registration ................5
4.3. 'working-copy' Link Relation Registration ..................5
4.4. 'working-copy-of' Link Relation Registration ...............6
4.5. 'predecessor-version' Link Relation Registration ...........6
4.6. 'successor-version' Link Relation Registration .............6
5. Security Considerations .........................................6
6. Acknowledgments .................................................7
7. References ......................................................7
7.1. Normative References .......................................7
7.2. Informative References .....................................7
Appendix A. Relationship to Java Content Repository (JCR) and
WebDAV ................................................9
A.1. Example: Use of Link Relations in HTTP Link Header .......10
Brown, et al. Informational [Page 2]
RFC 5829 Version Navigation Link Relations April 2010
1. Introduction
This specification defines a set of link relation types that may be
used on Web resources that exist in a system that supports versioning
to navigate among the different resources available, such as past
versions and working copies.
These link relations are used in the AtomPub ([RFC5023]) bindings of
the "Content Management Interoperability Services" (CMIS). See
Section 3.4.3.3 of [CMIS] for further information.
2. Terminology
Versioned Resource
When a resource is put under version control, it becomes a
"versioned resource". Many servers protect versioned resources
from modifications by considering them "checked in", and by
requiring a "checkout" operation before modification, and a
"checkin" operation to get back to the "checked-in" state. Other
Show full document text