idnits 2.17.1 draft-snell-more-link-relations-02.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 113: '...dinate", and "superior" NSS values MAY...' RFC 2119 keyword, line 124: '...sted" NSS values MAY include a two-dig...' RFC 2119 keyword, line 132: '..."role" NSS value MUST include one or m...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 22, 2013) is 3810 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 October 22, 2013 5 Expires: April 25, 2014 7 Additional Link Relations and the urn:social Namespace 8 draft-snell-more-link-relations-02 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 April 25, 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 . . . . . . . . . . . . . . . . . . . 4 49 2.2. urn:social:direct . . . . . . . . . . . . . . . . . . . . 4 50 2.3. urn:social:extended . . . . . . . . . . . . . . . . . . . 4 51 2.4. urn:social:peer . . . . . . . . . . . . . . . . . . . . . 4 52 2.5. urn:social:subordinate . . . . . . . . . . . . . . . . . 4 53 2.6. urn:social:superior . . . . . . . . . . . . . . . . . . . 5 54 2.7. urn:social:common . . . . . . . . . . . . . . . . . . . . 5 55 2.8. urn:social:interested . . . . . . . . . . . . . . . . . . 5 56 2.9. urn:social:self . . . . . . . . . . . . . . . . . . . . . 5 57 2.10. urn:social:role:{tokens} . . . . . . . . . . . . . . . . 5 58 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 59 3.1. Relationship of 'to', 'bto', 'cc', 'bcc', 'from', 'bfrom' 60 and 'scope' . . . . . . . . . . . . . . . . . . . . . . . 7 61 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 62 5. Informative References . . . . . . . . . . . . . . . . . . . 7 63 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 7 64 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 66 1. Introduction 68 This specification defines and adds the following additional link 69 relation types to the IANA Registry of Link Relations established by 70 [RFC5988]: to, bto, cc, bcc, from, bfrom, source, generator, 71 provider, location, alias and mentioned-by. Further, this 72 specification proposes a new 'social' URN namespace. 74 Note that this document is a work-in-progress draft specification 75 that does not yet represent a "standard". It is the intention of 76 this specification to propose a few new ideas and openly solicit 77 feedback on their definition and use. While this document might 78 eventually evolve into an RFC the ideas described herein have not yet 79 been broadly implemented and have definitions that may evolve through 80 successive iterations of this draft. 82 2. The 'social' URN Namespace 84 This specification defines the 'social' URN namespace having the 85 following structure: 87 ABNF Grammar: 89 social-url = "urn:social:" social-nss 90 NZDIGIT = %x31-39 91 distance = ":" NZDIGIT 92 confidence = ":" 2DIGIT 93 social-nss = "self" / 94 "everyone" / 95 "direct" / 96 ( "extended" [ distance ] ) / 97 ( "peer" [ distance ] ) / 98 ( "subordinate" [ distance ] ) / 99 ( "superior" [ distance ] ) / 100 ( "common" [ confidence ] ) / 101 ( "interested" [ confidence ] ) / 102 ( "role" ":" TOKEN ) 104 Within any given social networking system, there is an available 105 population of entities. Each NSS term represent specific subsets of 106 this population and are defined in terms of these subsets relative to 107 a fixed context. For example, if the fixed content is a person, the 108 "urn:social:direct" URN identifies the subset of the total population 109 that is directly connected to the context person within the social 110 graph, while the "urn:social:extended" URN identifies the subset that 111 is directly or indirectly connected to the context person. 113 The "extended", "peer", "subordinate", and "superior" NSS values MAY 114 include an additional single digit non-zero "distance" specifier, 115 whose value identifies a "degree of separation" from the link 116 context. For instance, the URN "urn:social:extended:1" would 117 identify members of the context's extended network that are only 1 118 degree of separation from the context (which is equivalent to the 119 "urn:social:direct" URN). The value "urn:social:extended:6" 120 indicates six degrees of separation from the context. If the 121 distance is omitted from the NSS, no limit to the distance is 122 assumed. 124 The "common" and "interested" NSS values MAY include a two-digit 125 "confidence factor" whose value specifies a confidence interval an 126 implementation can apply when determining which members of the total 127 population ought to be considered. The values range from 00-99, 128 corresponding to confidence intervals between 0% to 99%. If the 129 confidence factor is omitted from the NSS, a confidence interval of 130 100% is assumed. 132 The "role" NSS value MUST include one or more semicolon ";" TOKEN 133 delimited segments whose values identify specific named "roles" 134 within the population. For instance, the URN 135 "urn:social:role:editor" identifies all members of the relevant 136 population who are assigned to the "editor" rolel. The URN 137 "urn:social:role:reader;writer" identifes all members of the relevant 138 population who are assigned to both the "reader" and "writer" roles. 140 The 'social' URN namespace is defined to be intentionally ambiguous 141 and highly dependent on context. The specific interpretation of each 142 NSS, including any distance or confidence specifiers, depend entirely 143 on how and where the NSS is being used. 145 2.1. urn:social:everyone 147 The "urn:social:everyone" URN identifies the subset of the total 148 population that is visible to the context. 150 2.2. urn:social:direct 152 The "urn:social:direct" URN identifies the subset of the total 153 population that is both visible to and directly connected to the 154 context. 156 2.3. urn:social:extended 158 The "urn:social:extended" URN identifies the subset of the total 159 population that is visible to and connected either directly or 160 indirectly to the context. 162 2.4. urn:social:peer 164 The "urn:social:peer" URN identifies the subset of the total 165 population that is both visible to the context and considered to be a 166 "peer". 168 Peer relationships exist only within populations in which there 169 exists a hierarchical division of members in the population. An 170 example of such a network would be a company or similarly structured 171 organization. Peers might be directly or indirectly connected to the 172 target resource but are considered to share the same hierarchical 173 position. 175 2.5. urn:social:subordinate 177 The "urn:social:subordinate" URN identifies the subset of the total 178 population that is both visible to the context and considered to be 179 "subordinate" to the context. 181 Subordinate relationships exist only within populations in which 182 there exists a hierarchical division of members in the population. 183 An example of such a network would be a company or similarly 184 structured organization. Subordinates might be directly or 185 indirectly connected to the target resource but are considered to 186 share a lower hierarchical position. 188 2.6. urn:social:superior 190 The "urn:social:superior" URN identifies the subset of the total 191 population that is both visible to the context and considered to be 192 "superior" to the context. 194 Superior relationships exist only within populations in which there 195 exists a hierarchical division of members in the population. An 196 example of such a network would be a company or similarly structured 197 organization. Superiors might be directly or indirectly connected to 198 the target resource but are considered to have a higher hierarchical 199 position. 201 2.7. urn:social:common 203 The "urn:social:common" URN identifies the subset of the total 204 population that is both visible to the context and is determined to 205 share common attributes with the context. 207 Determination of "common attributes" is dependent entirely on the 208 application. For example, an application might choose to use shared 209 interests in a given topic as the "common attribute" binding a 210 particular grouping of members. 212 2.8. urn:social:interested 214 The "urn:social:interested" URN identifies the subset of the total 215 population that is both visible to the context and has an express 216 interest in the context. Examples of members of the "interested" 217 subset are those who have elected to "follow" the activity of the 218 context resource. 220 2.9. urn:social:self 222 The "urn:social:self" URN identifies the context resource itself as a 223 member of the total population. 225 2.10. urn:social:role:{tokens} 227 The "urn:social:role:{token}" URN identifies the subset of the total 228 population that is both visible to the contexst and has been assigned 229 to each of the individual roles identified within by the URN. 231 The values of the role tokens are specific to the context in which 232 they are being used. 234 3. IANA Considerations 236 The following Link Relations are added to the IANA Registry of Link 237 Relations. 239 +-----------------+-------------------------------------------------+ 240 | Name | Description | 241 +-----------------+-------------------------------------------------+ 242 | to | Refers to a resource that is considered to be | 243 | | part of the public primary audience of the | 244 | | link's context. | 245 | bto | Refers to a resource that is considered to be | 246 | | part of the private primary audience of the | 247 | | link's context. | 248 | cc | Refers to a resource that is considered to be | 249 | | part of the public secondary audience of the | 250 | | link's context. | 251 | bcc | Refers to a resource that is considered to be | 252 | | part of the private secondary audience of the | 253 | | link's context. | 254 | from | Refers to a resource that is publicly | 255 | | considered to be the originator of the link's | 256 | | context. | 257 | bfrom | Refers to a resource that is privately | 258 | | considered to be the orignator of the link's | 259 | | context. | 260 | scope | Refers to a resource that identifies the total | 261 | | population of entities to which the context is | 262 | | relevant. | 263 | source | Refers to the original source of information | 264 | | contained by the context resource. | 265 | provider | Refers to the resource that provided the | 266 | | context resource. Typically, this would be | 267 | | used to identify the entity publishing the | 268 | | resource. | 269 | generator | Refers to the resource that generated the | 270 | | context resource. Typically, this would be | 271 | | used to identify the software application that | 272 | | created the context resource. | 273 | mentioned-by | Refers to a resource that mentions the context | 274 | | resource in some fashion. This, for example, | 275 | | would be used when an article mentions another | 276 | | article, or a social status update mentions a | 277 | | particular user, etc. | 278 | location | References a URI/IRI that represents a physical | 279 | | or logical location with which the context | 280 | | resource is associated. | 281 +-----------------+-------------------------------------------------+ 283 3.1. Relationship of 'to', 'bto', 'cc', 'bcc', 'from', 'bfrom' and 284 'scope' 286 The "scope" link relation is closely aligned with the so-called 287 "audience targeting" link relations "to", "bto", "cc", "bcc", "from", 288 and "bfrom" in that "scope" links identify the total population from 289 which the audience is drawn. 291 4. Security Considerations 293 There are no additional security concerns introduced by this 294 document. 296 5. Informative References 298 [RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010. 300 Appendix A. Examples 302 Using targeting link relations and the urn:social namespace: 304 POST /alerts HTTP/1.1 305 Host: example.org 306 Content-Type: text/plain 307 Authorization: Basic {Base64 Credentials} 308 Link: ; rel="to" 309 Link: ; rel="cc" 310 Link: ; rel="bfrom" 311 Link: ; rel="scope" 313 Test message 315 Using the targeting link relations with urn:social:role: 317 POST /alerts HTTP/1.1 318 Host: example.org 319 Content-Type: text/plain 320 Authorization: Basic {Base64 Credentials} 321 Link: ; rel="to" 322 Link: ; rel="cc" 324 Test message 326 Using publication link relations: 328 329 330 ... 331 334 337 340 ... 341 342 ... 343 345 Using the location relation: 347 Link: ; rel="location" 349 Using the mentioned-by relation: 351 LINK /articles/1 HTTP/1.1 352 Host: example.org 353 Link: ; rel="mentioned-by" 355 Author's Address 356 James M Snell 358 Email: jasnell@gmail.com