Additional Link Relation Types
draft-snell-additional-link-relations-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-05-01
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
IETF conflict review conflict-review-snell-additional-link-relations
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                                           J. Snell
Internet-Draft                                               May 1, 2012
Intended status: Standards Track
Expires: November 2, 2012

                     Additional Link Relation Types
                draft-snell-additional-link-relations-02

Abstract

   This specification defines a number of additional Link Relation
   Types.

Status of this Memo

   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).  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 November 2, 2012.

Copyright Notice

   Copyright (c) 2012 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 Simplified BSD License.

Snell                   Expires November 2, 2012                [Page 1]
Internet-Draft                 HTTP Prefer                      May 2012

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  "about" . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  "implements"  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   4.  "privacy-policy"  . . . . . . . . . . . . . . . . . . . . . . . 4
   5.  "terms-of-service"  . . . . . . . . . . . . . . . . . . . . . . 5
   6.  "type"  . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
   8.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . . . 7
     9.2.  Informative References  . . . . . . . . . . . . . . . . . . 7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 7

Snell                   Expires November 2, 2012                [Page 2]
Internet-Draft                 HTTP Prefer                      May 2012

1.  Introduction

   This specification defines a number of additional Link Relation Types
   for a variety of common linking scenarios.

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

2.  "about"

   The "about" Link relation can be used to refer to a resource that is
   the subject of the link's context.  Multiple subjects can be
   indicated through the use of multiple "about" link relations.

   For example, if the context resource is a review about a particular
   product, the "about" link can be used to reference the URL of the
   product:

     HTTP/1.1 200 OK
     Content-Type: application/json
     Link: <http://store.example.org/product/abc>; rel="about"

     {...}

3.  "implements"

   The "implements" Link relation can be used to refer to a resource
   that specifies the behavior implemented by the link's context.  Links
   using the "implements" link relation can point either to formal
   specification documents such as RFC's, Internet-Drafts, W3C
   Recommendations, or to informal and possibly vendor specific
   documents that describe implementation details.

   For example, an HTTP client that implements the Atom Publishing
   Protocol [RFC5023] could include an "implements" Link (per [RFC5988])
   within the HTTP Request referencing RFC 5023:

     POST /collection HTTP/1.1
     Host: example.org
     Content-Type: application/atom+xml; type=entry
     Link: <http://tools.ietf.org/html/rfc5023>; rel="implements"

     <entry ...

   Multiple "implements" Links can be used to indicate that multiple

Snell                   Expires November 2, 2012                [Page 3]
Internet-Draft                 HTTP Prefer                      May 2012

   specifications have been implemented.

4.  "privacy-policy"

   The "privacy-policy" Link relation can be used to refer to a resource
Show full document text