Network Working Group J. Snell
Internet-Draft
Intended status: Informational August 1, 2014
Expires: February 2, 2015
Additional Link Relation Registrations
draft-snell-more-link-relations-05
Abstract
This specification registers a handful of new RFC 5988 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 February 2, 2015.
Copyright Notice
Copyright (c) 2014 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.
Snell Expires February 2, 2015 [Page 1]
Internet-Draft More Link Relations August 2014
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2
3. Security Considerations . . . . . . . . . . . . . . . . . . . 3
4. Informative References . . . . . . . . . . . . . . . . . . . 3
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
This specification defines and adds the following additional link
relation types to the IANA Registry of Link Relations established by
[RFC5988]: to, bto, cc, bcc, from, bfrom, source, scope, generator,
provider, location, alias and mentioned-by.
Note that this document is a work-in-progress draft specification
that does not yet represent a "standard". It is the intention of
this specification to propose a few new ideas and openly solicit
feedback on their definition and use. While this document might
eventually evolve into an RFC the ideas described herein have not yet
been broadly implemented and have definitions that may evolve through
successive iterations of this draft.
2. IANA Considerations
The following Link Relations are added to the IANA Registry of Link
Relations:
+--------------+----------------------------------------------------+
| Name | Description |
+--------------+----------------------------------------------------+
| id | Specifies an IRI [RFC3987] or URI |
| | [RFC3986]considered to represent the identity of |
| | the link context. |
| to | Refers to a resource that is considered to be part |
| | of the public primary audience of the link's |
| | context. |
| bto | Refers to a resource that is considered to be part |
| | of the private primary audience of the link's |
| | context. |
| cc | Refers to a resource that is considered to be part |
| | of the public secondary audience of the link's |
| | context. |
| bcc | Refers to a resource that is considered to be part |
| | of the private secondary audience of the link's |
| | context. |
| from | Refers to a resource that is publicly considered |
| | to be the originator of the link's context. |
Snell Expires February 2, 2015 [Page 2]
Internet-Draft More Link Relations August 2014
| bfrom | Refers to a resource that is privately considered |
| | to be the orignator of the link's context. |
| scope | Refers to a resource that identifies the total |
| | population of entities for which the context is |
| | considered relevant. |
| source | Refers to the original source of information |
| | contained by the context resource. |
| provider | Refers to the resource that provided the context |
| | resource. Typically, this would be used to |
| | identify the entity publishing the resource. |
| generator | Refers to the resource that generated the context |
| | resource. Typically, this would be used to |
| | identify the software application that created the |
| | context resource. |
| mentioned-by | Refers to a resource that mentions the context |
| | resource in some fashion. This, for example, would |
| | be used when an article mentions another article, |
| | or a social status update mentions a particular |
| | user, etc. |
| mentions | Refers to a resource mentioned by the context |
| | resource in some fashion. This, for example, would |
| | be used when an article mentions another article, |
| | or a social status update mentions a particular |
| | user, etc. |
| derived-from | Refers to a resource from which the context |
| | resource was derived. |
| location | References an IRI or URI representing a physical |
| | or logical location with which the context |
| | resource is associated. |
| card | References an IRI or URI representing a "card" |
| | summarizing the context resource. For instance, |
| | this may link to a VCard or HTML document that |
| | provides summary information about and contact |
| | information for a person, organization or |
| | community. |
+--------------+----------------------------------------------------+
3. Security Considerations
There are no additional security concerns introduced by this
document.
4. Informative References
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, RFC
3986, January 2005.
Snell Expires February 2, 2015 [Page 3]
Internet-Draft More Link Relations August 2014
[RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource
Identifiers (IRIs)", RFC 3987, January 2005.
[RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010.
Author's Address
James M Snell
Email: jasnell@gmail.com
Snell Expires February 2, 2015 [Page 4]