Linkset: Media Types and a Link Relation Type for Link Sets
draft-wilde-linkset-03
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Authors | Erik Wilde , Herbert Van de Sompel | ||
Last updated | 2019-03-25 (Latest revision 2018-09-17) | ||
Replaces | draft-wilde-linkset-link-rel | ||
Replaced by | draft-ietf-httpapi-linkset, RFC 9264 | ||
RFC stream | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This specification defines two media types and a link relation type for sets of links. The media types can be used to represents links in a standalone fashion, in one case in the native format used in the HTTP Link header, and in the other case in a JSON-based format. The link relation can be used to reference these kind of standalone link sets, so that a resource can indicate that additional links putting it into context are available someplace else. One typical scenario is when the number of links to put in an HTTP Link header field becomes too big, and thus these links should be provided by a distinct resource.
Authors
Erik Wilde
Herbert Van de Sompel
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)