The 'profile' Link Relation Type
draft-wilde-profile-link-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-03-26
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
IETF conflict review conflict-review-wilde-profile-link
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                                           EMC Corporation
Intended status: Standards Track                          March 26, 2012
Expires: September 27, 2012

                    The 'profile' Link Relation Type
                      draft-wilde-profile-link-00

Abstract

   This specification defines the 'profile' link relation type that
   allows resource representations to indicate that they are following
   one or more profiles.  A profile is defined to not alter the
   semantics of the resource representation itself, but to allow clients
   to learn about additional semantics that are associated with the
   resource in addition to those defined by the media type and possibly
   other mechanisms.

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 September 27, 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

Wilde                  Expires September 27, 2012               [Page 1]
Internet-Draft             "profile" Link Type                March 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 Profiles . . . . . . . . . . . . . . . . . . . . . . . 4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   6.  Change Log  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . . . 5
     7.2.  Informative References  . . . . . . . . . . . . . . . . . . 5
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . . . 5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 5

Wilde                  Expires September 27, 2012               [Page 2]
Internet-Draft             "profile" Link Type                March 2012

1.  Introduction

   One of the foundations of the Internet and Web Architecture is the
   fact that resource representations communicated through protocols
   such as SMTP or HTTP are labeled with a 'media type', which allows a
   client to understand at run time what 'type' of resource
   representation it is handling.  Sometimes, it would be useful for
   servers and clients to include additional information about the
   nature of the resource, so that a client understanding this
   additional information could react in a way specific to that
   specialization of the resource.  HTML 4 [3] has such a mechanism
   built into the language, which is the 'profile' attribute of the
   'head' element.  This mechanism, however, is specific to HTML alone,
   and it seems as if HTML 5 will drop support for this mechanism
   entirely.

   This specification registers a 'profile' link relation type according
   to the rules of RFC 5988 [1].  This link relation type is independent
   of the resource representation it is used in (but the representation
   must support types links for this mechanism to work) and independent
   of the target of the linked URI.  In fact, for the purpose of this
   specification, the URI does not necessarily have to link to a
   dereferencable resource, and clients can treat the occurrence of a
   specific URI in the same sense as a namespace URI and invoke specific
   behavior based on the assumption that a specific profile URI signals
   that a resource follows a specific profile.  Note that at the same
   time, it is possible for profile URIs to use referencable URIs and
Show full document text