Network Working GroupA. Brown
Internet-DraftG. Clemm
Intended status: InformationalIBM
Expires: January 14, 2010J. Reschke, Editor
July 13, 2009

Link Relations for Simple Version Navigation


Status of this Memo

This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress”.

The list of current Internet-Drafts can be accessed at

The list of Internet-Draft Shadow Directories can be accessed at

This Internet-Draft will expire on January 14, 2010.

Copyright Notice

Copyright © 2009 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 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.


This specification defines Atom link relations for navigation between a resource and its versions.

Editorial Note (To be removed by RFC Editor before publication)

Please send comments to the Atom Syntax mailing list (<>).

1. Introduction

This specification defines link relations that may be used on a resource that exists in a system that supports versioning to navigate among the different resources available, such as past versions.

2. Terminology

The terms below are borrowed from the Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning) ([RFC3253]).

Version-Controlled Resource, Checked-Out

Checked-Out Resource

Version Resource

Version History Resource

Predecessor, Successor, Ancestor, Descendant

Root Version Resource

Working Resource

3. Link Relations

The following link relations are defined:

When included on a version controlled resource, this link points to a resource containing the version history for this resource.
When included on a version controlled resource, this link points to a resource containing the latest (e.g., current) version. [issue.latest.version: I think "latest" is misleading, as it may not be the "latest" when different branches are involved. JCR 1.0 has "base version", defined as "The base version of a particular node N is the one that will serve as the default immediate predecessor of the next version of N that is created." -- can we adopt that? (see <>). --jre]
When included on a version resource, this link points to a Working Resource.
When included on a version resource, this link points to a resource containing the predecessor version in the version history.
When included on a version resource, this link points to a resource containing the successor version in the version history.

4. Examples

[rfc.comment.1: To Be Done]

5. Security Considerations

Automated agents should take care when these relation crosses administrative domains (e.g., the URI has a different authority than the current document).

6. IANA Considerations

The link relations defined in Section 3 are to be registered by IANA per [RFC4287].

All link relations defined in this document will have the following expected display characteristics:

7. References

7.1 Normative References

Nottingham, M. and R. Sayre, “The Atom Syndication Format”, RFC 4287, December 2005.

7.2 Informative References

Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J. Whitehead, “Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)”, RFC 3253, March 2002.

A. Relationship to JCR and WebDAV

[rfc.comment.2: To Be Done: describe how versioning properties in JCR and in WebDAV/DeltaV map to the newly defined link relations.]

B. Contributors

The content and concepts within are a product of the Content Management Interoperability Services (CMIS) Technical Committee (TC) at OASIS.

All members of the TC have contributed.

C. Change Log (to be removed by RFC Editor before publication)

Authors' Addresses

Al Brown
3565 Harbor Blvd
Costa Mesa, California 92626
Geoffrey Clemm
20 Maguire Road
Lexington, MA 02421
Julian F. Reschke (editor)
greenbytes GmbH
Hafenweg 16
Muenster, NW 48155