Linkset: A Link Relation Type for Link Sets
draft-wilde-linkset-link-rel-01

Document Type Active Internet-Draft (individual)
Last updated 2017-01-03
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           E. Wilde
Internet-Draft                                           CA Technologies
Intended status: Informational                          H. Van de Sompel
Expires: July 6, 2017                     Los Alamos National Laboratory
                                                        January 02, 2017

              Linkset: A Link Relation Type for Link Sets
                    draft-wilde-linkset-link-rel-01

Abstract

   This specification defines the "linkset" link relation type that can
   be used to link to a resource that provides a set of links.

Note to Readers

   Please discuss this draft on the ART mailing list
   (<https://www.ietf.org/mailman/listinfo/art>).

   Online access to all versions and files is available on GitHub
   (<https://github.com/dret/I-D/tree/master/linkset-link-rel>).

Status of This Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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 on July 6, 2017.

Copyright Notice

   Copyright (c) 2017 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

Wilde & Van de Sompel     Expires July 6, 2017                  [Page 1]
Internet-Draft         Linkset Link Relation Type           January 2017

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Link Sets . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Third-Party Links . . . . . . . . . . . . . . . . . . . .   3
     4.2.  Large Number of Links . . . . . . . . . . . . . . . . . .   3
   5.  Link Relation for Linking to Link Sets  . . . . . . . . . . .   3
   6.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Link Set Serialized as application/link-format  . . . . .   4
     6.2.  Link Set Serialized As application/hal+json . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  Link Relation Type: linkset . . . . . . . . . . . . . . .   7
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   A resource typically conveys typed Web Links [RFC5988] as an inherent
   part of the resource's representation [RFC7231], for example, using
   the <link> element for HTML representations or the "Link" header in
   HTTP response headers for representations of any media type.  Cases
   exist in which providing links in a by value manner is impractical or
   impossible.  In these cases, an approach to provide links by
   reference is desired.  This specification defines the "linkset"
   relation type that allows doing so.

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Wilde & Van de Sompel     Expires July 6, 2017                  [Page 2]
Internet-Draft         Linkset Link Relation Type           January 2017
Show full document text