idnits 2.17.1 draft-snell-more-link-relations-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 1, 2014) is 3555 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC3986' is defined on line 136, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 5988 (Obsoleted by RFC 8288) Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Snell 3 Internet-Draft 4 Intended status: Informational August 1, 2014 5 Expires: February 2, 2015 7 Additional Link Relation Registrations 8 draft-snell-more-link-relations-05 10 Abstract 12 This specification registers a handful of new RFC 5988 Link Relation 13 types. 15 Status of This Memo 17 This Internet-Draft is submitted to IETF in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on February 2, 2015. 32 Copyright Notice 34 Copyright (c) 2014 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. 44 Table of Contents 46 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 47 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 48 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 49 4. Informative References . . . . . . . . . . . . . . . . . . . 3 50 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 52 1. Introduction 54 This specification defines and adds the following additional link 55 relation types to the IANA Registry of Link Relations established by 56 [RFC5988]: to, bto, cc, bcc, from, bfrom, source, scope, generator, 57 provider, location, alias and mentioned-by. 59 Note that this document is a work-in-progress draft specification 60 that does not yet represent a "standard". It is the intention of 61 this specification to propose a few new ideas and openly solicit 62 feedback on their definition and use. While this document might 63 eventually evolve into an RFC the ideas described herein have not yet 64 been broadly implemented and have definitions that may evolve through 65 successive iterations of this draft. 67 2. IANA Considerations 69 The following Link Relations are added to the IANA Registry of Link 70 Relations: 72 +--------------+----------------------------------------------------+ 73 | Name | Description | 74 +--------------+----------------------------------------------------+ 75 | id | Specifies an IRI [RFC3987] or URI | 76 | | [RFC3986]considered to represent the identity of | 77 | | the link context. | 78 | to | Refers to a resource that is considered to be part | 79 | | of the public primary audience of the link's | 80 | | context. | 81 | bto | Refers to a resource that is considered to be part | 82 | | of the private primary audience of the link's | 83 | | context. | 84 | cc | Refers to a resource that is considered to be part | 85 | | of the public secondary audience of the link's | 86 | | context. | 87 | bcc | Refers to a resource that is considered to be part | 88 | | of the private secondary audience of the link's | 89 | | context. | 90 | from | Refers to a resource that is publicly considered | 91 | | to be the originator of the link's context. | 92 | bfrom | Refers to a resource that is privately considered | 93 | | to be the orignator of the link's context. | 94 | scope | Refers to a resource that identifies the total | 95 | | population of entities for which the context is | 96 | | considered relevant. | 97 | source | Refers to the original source of information | 98 | | contained by the context resource. | 99 | provider | Refers to the resource that provided the context | 100 | | resource. Typically, this would be used to | 101 | | identify the entity publishing the resource. | 102 | generator | Refers to the resource that generated the context | 103 | | resource. Typically, this would be used to | 104 | | identify the software application that created the | 105 | | context resource. | 106 | mentioned-by | Refers to a resource that mentions the context | 107 | | resource in some fashion. This, for example, would | 108 | | be used when an article mentions another article, | 109 | | or a social status update mentions a particular | 110 | | user, etc. | 111 | mentions | Refers to a resource mentioned by the context | 112 | | resource in some fashion. This, for example, would | 113 | | be used when an article mentions another article, | 114 | | or a social status update mentions a particular | 115 | | user, etc. | 116 | derived-from | Refers to a resource from which the context | 117 | | resource was derived. | 118 | location | References an IRI or URI representing a physical | 119 | | or logical location with which the context | 120 | | resource is associated. | 121 | card | References an IRI or URI representing a "card" | 122 | | summarizing the context resource. For instance, | 123 | | this may link to a VCard or HTML document that | 124 | | provides summary information about and contact | 125 | | information for a person, organization or | 126 | | community. | 127 +--------------+----------------------------------------------------+ 129 3. Security Considerations 131 There are no additional security concerns introduced by this 132 document. 134 4. Informative References 136 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 137 Resource Identifier (URI): Generic Syntax", STD 66, RFC 138 3986, January 2005. 140 [RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource 141 Identifiers (IRIs)", RFC 3987, January 2005. 143 [RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010. 145 Author's Address 147 James M Snell 149 Email: jasnell@gmail.com