cite-as: A Link Relation to Convey a Preferred URI for Referencing
RFC 8574
| Document | Type |
RFC - Informational
(April 2019; Errata)
Was draft-vandesompel-citeas (individual)
|
|
|---|---|---|---|
| Last updated | 2019-04-19 | ||
| Replaces | draft-vandesompel-identifier | ||
| Stream | ISE | ||
| Formats | plain text pdf html bibtex | ||
| IETF conflict review | conflict-review-vandesompel-citeas | ||
| Stream | ISE state | Published RFC | |
| Consensus Boilerplate | Unknown | ||
| Document shepherd | Adrian Farrel | ||
| Shepherd write-up | Show (last changed 2019-02-06) | ||
| IESG | IESG state | RFC 8574 (Informational) | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | Adrian Farrel <rfc-ise@rfc-editor.org> | ||
| IANA | IANA review state | IANA OK - Actions Needed | |
| IANA action state | RFC-Ed-Ack | ||
Independent Submission H. Van de Sompel
Request for Comments: 8574 Data Archiving and Networked Services
Category: Informational M. Nelson
ISSN: 2070-1721 Old Dominion University
G. Bilder
Crossref
J. Kunze
California Digital Library
S. Warner
Cornell University
April 2019
cite-as: A Link Relation to Convey a Preferred URI for Referencing
Abstract
A web resource is routinely referenced by means of the URI with which
it is directly accessed. But cases exist where referencing a
resource by means of a different URI is preferred. This
specification defines a link relation type that can be used to convey
such a preference.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This is a contribution to the RFC Series, independently of any other
RFC stream. The RFC Editor has chosen to publish this document at
its discretion and makes no statement about its value for
implementation or deployment. Documents approved for publication by
the RFC Editor are not candidates for any level of Internet Standard;
see Section 2 of RFC 7841.
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/rfc8574.
Van de Sompel, et al. Informational [Page 1]
RFC 8574 The "cite-as" Link Relation Type April 2019
Copyright Notice
Copyright (c) 2019 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Persistent Identifiers . . . . . . . . . . . . . . . . . 3
3.2. Version Identifiers . . . . . . . . . . . . . . . . . . . 5
3.3. Preferred Social Identifier . . . . . . . . . . . . . . . 5
3.4. Multi-resource Publications . . . . . . . . . . . . . . . 6
4. The "cite-as" Relation Type for Expressing a Preferred URI
for the Purpose of Referencing . . . . . . . . . . . . . . . 6
5. Distinction with Other Relation Types . . . . . . . . . . . . 8
5.1. The "bookmark" Relation Type . . . . . . . . . . . . . . 9
5.2. The "canonical" Relation Type . . . . . . . . . . . . . . 9
6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.1. Persistent HTTP URI . . . . . . . . . . . . . . . . . . . 11
6.2. Version URIs . . . . . . . . . . . . . . . . . . . . . . 12
6.3. Preferred Profile URI . . . . . . . . . . . . . . . . . . 13
6.4. Multi-resource Publication . . . . . . . . . . . . . . . 13
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . 15
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
Van de Sompel, et al. Informational [Page 2]
RFC 8574 The "cite-as" Link Relation Type April 2019
1. Introduction
A web resource is routinely referenced (e.g., linked or bookmarked)
by means of the URI with which it is directly accessed. But cases
exist where referencing a resource by means of a different URI is
preferred, for example, because the latter URI is intended to be more
persistent over time. Currently, there is no link relation type to
convey such an alternative referencing preference; this specification
addresses this deficit by introducing a link relation type intended
for that purpose.
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text