Linkset: Media Types and a Link Relation Type for Link Sets
draft-wilde-linkset-04

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04

Network Working Group                                           E. Wilde
Internet-Draft
Intended status: Informational                          H. Van de Sompel
Expires: February 29, 2020         Data Archiving and Networked Services
                                                         August 28, 2019

      Linkset: Media Types and a Link Relation Type for Link Sets
                         draft-wilde-linkset-04

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 as used in
   the HTTP Link header, and in the other case in a JSON-based format.
   The link relation type can be used by a resource to point at another
   resource that provides a set of links, including links in which the
   former resource participates.  One typical scenario is when the
   number of links to put in an HTTP Link header becomes too big, and
   thus these links should be provided in another way.

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>).

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 https://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 February 29, 2020.

Wilde & Van de Sompel   Expires February 29, 2020               [Page 1]
Internet-Draft                   Linkset                     August 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.  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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Third-Party Links . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Challenges Writing to HTTP Link Header Field  . . . . . .   4
     3.3.  Large Number of Links . . . . . . . . . . . . . . . . . .   4
   4.  Document Formats for Sets of Links  . . . . . . . . . . . . .   5
     4.1.  HTTP Link Document Format: application/linkset  . . . . .   5
     4.2.  JSON Document Format: application/linkset+json  . . . . .   6
       4.2.1.  Set of Links  . . . . . . . . . . . . . . . . . . . .   6
       4.2.2.  Link Context Object . . . . . . . . . . . . . . . . .   7
       4.2.3.  Link Target Object  . . . . . . . . . . . . . . . . .   7
       4.2.4.  Link Target Attributes  . . . . . . . . . . . . . . .   9
   5.  The "linkset" Relation Type for Linking to a Set of Links . .  13
   6.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  14
     6.1.  Set of Links Provided By Value as application/linkset . .  14
     6.2.  Set of Links Provided By Reference as
           application/linkset+json  . . . . . . . . . . . . . . . .  15
   7.  Implementation Status . . . . . . . . . . . . . . . . . . . .  18
     7.1.  Open Journal Systems (OJS)  . . . . . . . . . . . . . . .  18
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
     8.1.  Link Relation Type: linkset . . . . . . . . . . . . . . .  18
     8.2.  Media Type: application/linkset . . . . . . . . . . . . .  19
       8.2.1.  IANA Considerations . . . . . . . . . . . . . . . . .  19
     8.3.  Media Type: application/linkset+json  . . . . . . . . . .  20
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  21
   10. Normative References  . . . . . . . . . . . . . . . . . . . .  21
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  22
   Appendix B.  JSON-LD Context  . . . . . . . . . . . . . . . . . .  22
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  23