Note: a later version of this document has been published as RFC 5829.
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”.¶
This Internet-Draft will expire in September 2010.¶
Copyright © 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 BSD License.¶
Please send comments to the Atom Syntax mailing list (<http://www.imc.org/atom-syntax/>).
Note that although discussion takes place on the Atompub working group's mailing list, this is not a working group document.
XML versions, latest edits and the issues list for this document are available from <http://greenbytes.de/tech/webdav/#draft-brown-versioning-link-relations>.
|I auth48 (type: edit, status: closed)|
|firstname.lastname@example.org||2010-03-26||Umbrella issue for changes made during the RFC Editor's AUTH48 period.|
|Associated changes in this document: <#rfc.change.auth48.1>, <#rfc.change.auth48.2>, 1, 2, 2, 2, 3, 3.1, 3.2, 3.2, 3.3, 3.3, 3.4, 3.5, 3.5, 3.5, 3.6, 3.6, 4, 5, 7.1, 7.2, A, A.1, A.1, A.1, A.1, A.1, <#rfc.change.auth48.29>.|
|I edit (type: edit, status: closed)|
|email@example.com||2009-11-19||Umbrella issue for editorial fixes/enhancements.|
|Associated changes in this document: 7.2, del-8.|
This specification defines a set ↑↓
ot 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.¶
Versioned Resource ¶
Version History ¶
Predecessor, Successor ¶
Working Copy ¶
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 should also take care to detect circular references.¶
Care should be applied when versioned resources are subject to differing access policies. In this case, exposing links may leak information even if the linked resource itself is properly secured. In particular, the syntax of the link ↑↓
URI/IRI could expose sensitive information (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.¶
Thanks to the members of Content Management Interoperability Services (CMIS) Technical Committee (TC) at OASIS for the initial proposal, and to Jan Algermissen for feedback during IETF review.¶