idnits 2.17.1 draft-snell-more-link-relations-01.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 : ---------------------------------------------------------------------------- ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 86: '... Specific String (NSS) MUST be one of:...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 23, 2013) is 3868 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 5988 (Obsoleted by RFC 8288) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 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 September 23, 2013 5 Expires: March 27, 2014 7 Additional Link Relations and the urn:social Namespace 8 draft-snell-more-link-relations-01 10 Abstract 12 This specification defines a number of additional Link Relation Types 13 that can used for a variety of purposes.. 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 March 27, 2014. 32 Copyright Notice 34 Copyright (c) 2013 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. The 'social' URN Namespace . . . . . . . . . . . . . . . . . 2 48 2.1. urn:social:everyone . . . . . . . . . . . . . . . . . . . 3 49 2.2. urn:social:direct . . . . . . . . . . . . . . . . . . . . 3 50 2.3. urn:social:extended . . . . . . . . . . . . . . . . . . . 3 51 2.4. urn:social:peer . . . . . . . . . . . . . . . . . . . . . 3 52 2.5. urn:social:subordinate . . . . . . . . . . . . . . . . . 4 53 2.6. urn:social:superior . . . . . . . . . . . . . . . . . . . 4 54 2.7. urn:social:common . . . . . . . . . . . . . . . . . . . . 4 55 2.8. urn:social:interested . . . . . . . . . . . . . . . . . . 5 56 2.9. urn:social:self . . . . . . . . . . . . . . . . . . . . . 5 57 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 58 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 59 5. Informative References . . . . . . . . . . . . . . . . . . . 6 60 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 6 61 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7 63 1. Introduction 65 This specification defines and adds the following additional link 66 relation types to the IANA Registry of Link Relations established by 67 [RFC5988]: to, bto, cc, bcc, from, bfrom, source, generator, 68 provider, location, alias and mentionedBy. Further, this 69 specification proposes a new 'social' URN namespace. 71 Note that this document is a work-in-progress draft specification 72 that does not yet represent a "standard". It is the intention of 73 this specification to propose a few new ideas and openly solicit 74 feedback on their definition and use. While this document might 75 eventually evolve into an RFC the ideas described herein have not yet 76 been broadly implemented and have definitions that may evolve through 77 successive iterations of this draft. 79 2. The 'social' URN Namespace 81 This specification defines the 'social' URN namespace having the 82 following structure: 84 urn:social:{NSS} 86 The Namespace Specific String (NSS) MUST be one of: 88 o everyone 90 o direct 91 o extended 93 o peer 95 o subordinate 97 o superior 99 o common 101 o interested 103 o self 105 Within any given social networking system, there is an available 106 population of entities. Each NSS term represent specific subsets of 107 this population and are defined in terms of these subsets relative to 108 a fixed context. For example, if the fixed content is a person, the 109 "urn:social:direct" URN identifies the subset of the total population 110 that is directly connected to the context person within the social 111 graph, while the "urn:social:extended" URN identifies the subset that 112 is directly or indirectly connected to the context person. 114 The 'social' URN namespace is defined to be intentionally ambiguous 115 and contextually dependent. The specific interpretation of each NSS 116 depends entirely on how and where the NSS is being used. 118 2.1. urn:social:everyone 120 The "urn:social:everyone" URN identifies the subset of the total 121 population that is visible to the context. 123 2.2. urn:social:direct 125 The "urn:social:direct" URN identifies the subset of the total 126 population that is both visible to and directly connected to the 127 context. 129 2.3. urn:social:extended 131 The "urn:social:extended" URN identifies the subset of the total 132 population that is visible to and connected either directly or 133 indirectly to the context. 135 2.4. urn:social:peer 136 The "urn:social:peer" URN identifies the subset of the total 137 population that is both visible to the context and considered to be a 138 "peer". 140 Peer relationships exist only within populations in which there 141 exists a hierarchical division of members in the population. An 142 example of such a network would be a company or similarly structured 143 organization. Peers might be directly or indirectly connected to the 144 target resource but are considered to share the same hierarchical 145 position. 147 2.5. urn:social:subordinate 149 The "urn:social:subordinate" URN identifies the subset of the total 150 population that is both visible to the context and considered to be 151 "subordinate" to the context. 153 Subordinate relationships exist only within populations in which 154 there exists a hierarchical division of members in the population. 155 An example of such a network would be a company or similarly 156 structured organization. Subordinates might be directly or 157 indirectly connected to the target resource but are considered to 158 share a lower hierarchical position. 160 2.6. urn:social:superior 162 The "urn:social:superior" URN identifies the subset of the total 163 population that is both visible to the context and considered to be 164 "superior" to the context. 166 Superior relationships exist only within populations in which there 167 exists a hierarchical division of members in the population. An 168 example of such a network would be a company or similarly structured 169 organization. Superiors might be directly or indirectly connected to 170 the target resource but are considered to have a higher hierarchical 171 position. 173 2.7. urn:social:common 175 The "urn:social:common" URN identifies the subset of the total 176 population that is both visible to the context and is determined to 177 share the same common attributes as the context. 179 Determination of "common attributes" is dependent entirely on the 180 application. For example, an application might choose to use shared 181 interests in a given topic as the "common attribute" binding a 182 particular grouping of members. 184 2.8. urn:social:interested 186 The "urn:social:interested" URN identifies the subset of the total 187 population that is both visible to the context and has an express 188 interest in the context. Examples of members of the "interested" 189 subset are those who have elected to "follow" the activity of the 190 context resource. 192 2.9. urn:social:self 194 The "urn:social:self" URN identifies the context resource itself as a 195 member of the total population. 197 3. IANA Considerations 199 The following Link Relations are added to the IANA Registry of Link 200 Relations. 202 +---------------+---------------------------------------------------+ 203 | Name | Description | 204 +---------------+---------------------------------------------------+ 205 | to | Refers to a resource that is considered to be | 206 | | part of the public primary audience of the link's | 207 | | context. | 208 | bto | Refers to a resource that is considered to be | 209 | | part of the private primary audience of the | 210 | | link's context. | 211 | cc | Refers to a resource that is considered to be | 212 | | part of the public secondary audience of the | 213 | | link's context. | 214 | bcc | Refers to a resource that is considered to be | 215 | | part of the private secondary audience of the | 216 | | link's context. | 217 | from | Refers to a resource that is publicly considered | 218 | | to be the originator of the link's context. | 219 | bfrom | Refers to a resource that is privately considered | 220 | | to be the orignator of the link's context. | 221 | source | Refers to the original source of information | 222 | | contained by the context resource. | 223 | provider | Refers to the resource that provided the context | 224 | | resource. Typically, this would be used to | 225 | | identify the entity publishing the resource. | 226 | generator | Refers to the resource that generated the context | 227 | | resource. Typically, this would be used to | 228 | | identify the software application that created | 229 | | the context resource. | 230 | mentionedBy | Refers to a resource that mentions the context | 231 | | resource in some fashion. This, for example, | 232 | | would be used when an article mentions another | 233 | | article, or a social status update mentions a | 234 | | particular user, etc. | 235 | location | References a URI/IRI that represents a physical | 236 | | or logical location with which the context | 237 | | resource is associated. | 238 +---------------+---------------------------------------------------+ 240 4. Security Considerations 242 There are no additional security concerns introduced by this 243 document. 245 5. Informative References 247 [RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010. 249 Appendix A. Examples 251 Using targeting link relations and the urn:social namespace: 253 POST /alerts HTTP/1.1 254 Host: example.org 255 Content-Type: text/plain 256 Authorization: Basic {Base64 Credentials} 257 Link: ; rel="to" 258 Link: ; rel="cc" 259 Link: ; rel="bfrom" 261 Test message 263 Using publication link relations: 265 266 267 ... 268 271 274 277 ... 278 279 ... 280 282 Using the alias and location relations: 284 Link: ; rel="location" 286 Using the mentionedBy relation: 288 LINK /articles/1 HTTP/1.1 289 Host: example.org 290 Link: ; rel="mentionedBy" 292 Author's Address 294 James M Snell 296 Email: jasnell@gmail.com