The 'describes' Link Relation Type
draft-wilde-describes-link-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in app area)
Last updated 2012-10-09 (latest revision 2012-09-24)
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
IETF conflict review conflict-review-wilde-describes-link
Stream WG state (None)
Document shepherd None
IESG IESG state Publication Requested
Telechat date
Responsible AD Barry Leiba
Send notices to erik.wilde@emc.com, draft-wilde-describes-link@tools.ietf.org
Network Working Group                                           E. Wilde
Internet-Draft                                           EMC Corporation
Intended status: Standards Track                      September 22, 2012
Expires: March 26, 2013

                   The 'describes' Link Relation Type
                     draft-wilde-describes-link-01

Abstract

   This specification defines the 'describes' link relation type that
   allows resource representations to indicate that they are describing
   another resource.  In contexts where applications want to associate
   described resources and description resources, and want to build
   services based on these associations, the 'describes' link relation
   type provides the opposite direction of the 'describedby' link
   relation type, which already is a registered link relation type.

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 March 26, 2013.

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

Wilde                    Expires March 26, 2013                 [Page 1]
Internet-Draft            "describes" Link Type           September 2012

   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.  Resource Descriptions . . . . . . . . . . . . . . . . . . . . . 3
   4.  Use Case  . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   7.  Change Log  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
     7.1.  From -00 to -01 . . . . . . . . . . . . . . . . . . . . . . 5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . . . 6
     8.2.  Informative References  . . . . . . . . . . . . . . . . . . 6
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . . . 6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 6

Wilde                    Expires March 26, 2013                 [Page 2]
Internet-Draft            "describes" Link Type           September 2012

1.  Introduction

   Resources on the Web can be identified by any (registered) URI scheme
   and can be represented by any (registered) media type.  In many
   cases, applications establish specific (i.e., typed) relations
   between the resources they are concerned with, which can either be
   under their control, or controlled by another authority.  A common
   usage pattern for associating resources is to have resources which
   are descriptions of other resources.  This specification registers
   the 'describes' link relation, which allows applications to represent
   the fact that one resource is a description of another resource.

   RFC 5988 [1] "defines a framework for typed links that isn't specific
   to a particular serialisation or application.  It does so by
   redefining the link relation registry established by Atom to have a
   broader domain, and adding to it the relations that are defined by
   HTML."  This registration request intends to augment the link
   relation registry with a link relation that is the inverse of the
   already registered 'describedby' relation, so that links between
   described resources and describing resources can be represented in
Show full document text