Debian Codegraph @

rfc5988.html

raw
1 <pre>Internet Engineering Task Force (IETF) M. Nottingham
2 Request for Comments: 5988 October 2010
3 Updates: <a href="./rfc4287">4287</a>
4 Category: Standards Track
5 ISSN: 2070-1721
6
7
8 <span class="h1">Web Linking</span>
9
10 Abstract
11
12 This document specifies relation types for Web links, and defines a
13 registry for them. It also defines the use of such links in HTTP
14 headers with the Link header field.
15
16 Status of This Memo
17
18 This is an Internet Standards Track document.
19
20 This document is a product of the Internet Engineering Task Force
21 (IETF). It represents the consensus of the IETF community. It has
22 received public review and has been approved for publication by the
23 Internet Engineering Steering Group (IESG). Further information on
24 Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
25
26 Information about the current status of this document, any errata,
27 and how to provide feedback on it may be obtained at
28 <a href="http://www.rfc-editor.org/info/rfc5988">http://www.rfc-editor.org/info/rfc5988</a>.
29
30 Copyright Notice
31
32 Copyright (c) 2010 IETF Trust and the persons identified as the
33 document authors. All rights reserved.
34
35 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
36 Provisions Relating to IETF Documents
37 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
38 publication of this document. Please review these documents
39 carefully, as they describe your rights and restrictions with respect
40 to this document. Code Components extracted from this document must
41 include Simplified BSD License text as described in Section 4.e of
42 the Trust Legal Provisions and are provided without warranty as
43 described in the Simplified BSD License.
44
45
46
47
48
49
50
51
52 <span class="grey">Nottingham Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
55
56
57 This document may contain material from IETF Documents or IETF
58 Contributions published or made publicly available before November
59 10, 2008. The person(s) controlling the copyright in some of this
60 material may not have granted the IETF Trust the right to allow
61 modifications of such material outside the IETF Standards Process.
62 Without obtaining an adequate license from the person(s) controlling
63 the copyright in such materials, this document may not be modified
64 outside the IETF Standards Process, and derivative works of it may
65 not be created outside the IETF Standards Process, except to format
66 it for publication as an RFC or to translate it into languages other
67 than English.
68
69 Table of Contents
70
71 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
72 <a href="#section-2">2</a>. Notational Conventions ..........................................<a href="#page-3">3</a>
73 <a href="#section-3">3</a>. Links ...........................................................<a href="#page-4">4</a>
74 <a href="#section-4">4</a>. Link Relation Types .............................................<a href="#page-5">5</a>
75 <a href="#section-4.1">4.1</a>. Registered Relation Types ..................................<a href="#page-5">5</a>
76 <a href="#section-4.2">4.2</a>. Extension Relation Types ...................................<a href="#page-6">6</a>
77 <a href="#section-5">5</a>. The Link Header Field ...........................................<a href="#page-6">6</a>
78 <a href="#section-5.1">5.1</a>. Target IRI .................................................<a href="#page-7">7</a>
79 <a href="#section-5.2">5.2</a>. Context IRI ................................................<a href="#page-7">7</a>
80 <a href="#section-5.3">5.3</a>. Relation Type ..............................................<a href="#page-8">8</a>
81 <a href="#section-5.4">5.4</a>. Target Attributes ..........................................<a href="#page-8">8</a>
82 <a href="#section-5.5">5.5</a>. Examples ...................................................<a href="#page-9">9</a>
83 <a href="#section-6">6</a>. IANA Considerations ............................................<a href="#page-10">10</a>
84 <a href="#section-6.1">6.1</a>. Link HTTP Header Registration .............................<a href="#page-10">10</a>
85 <a href="#section-6.2">6.2</a>. Link Relation Type Registry ...............................<a href="#page-10">10</a>
86 <a href="#section-6.2.1">6.2.1</a>. Registering New Link Relation Types ................<a href="#page-11">11</a>
87 <a href="#section-6.2.2">6.2.2</a>. Initial Registry Contents ..........................<a href="#page-12">12</a>
88 <a href="#section-6.3">6.3</a>. Link Relation Application Data Registry ...................<a href="#page-16">16</a>
89 <a href="#section-7">7</a>. Security Considerations ........................................<a href="#page-17">17</a>
90 <a href="#section-8">8</a>. Internationalisation Considerations ............................<a href="#page-18">18</a>
91 <a href="#section-9">9</a>. References .....................................................<a href="#page-18">18</a>
92 <a href="#section-9.1">9.1</a>. Normative References ......................................<a href="#page-18">18</a>
93 <a href="#section-9.2">9.2</a>. Informative References ....................................<a href="#page-19">19</a>
94 <a href="#appendix-A">Appendix A</a>. Notes on Using the Link Header with the HTML4
95 Format ...............................................<a href="#page-21">21</a>
96 <a href="#appendix-B">Appendix B</a>. Notes on Using the Link Header with the Atom
97 Format ...............................................<a href="#page-22">22</a>
98 <a href="#appendix-C">Appendix C</a>. Acknowledgements .....................................<a href="#page-23">23</a>
99
100
101
102
103
104
105
106
107
108 <span class="grey">Nottingham Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 A means of indicating the relationships between resources on the Web,
116 as well as indicating the type of those relationships, has been
117 available for some time in HTML [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>], and more
118 recently in Atom [<a href="./rfc4287" title="&quot;The Atom Syndication Format&quot;">RFC4287</a>]. These mechanisms, although conceptually
119 similar, are separately specified. However, links between resources
120 need not be format specific; it can be useful to have typed links
121 that are independent of their serialisation, especially when a
122 resource has representations in multiple formats.
123
124 To this end, this document defines a framework for typed links that
125 isn't specific to a particular serialisation or application. It does
126 so by redefining the link relation registry established by Atom to
127 have a broader domain, and adding to it the relations that are
128 defined by HTML.
129
130 Furthermore, an HTTP header field for conveying typed links was
131 defined in <a href="./rfc2068#section-19.6.2.4">Section&nbsp;19.6.2.4 of [RFC2068]</a>, but removed from [<a href="./rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>],
132 due to a lack of implementation experience. Since then, it has been
133 implemented in some User Agents (e.g., for stylesheets), and several
134 additional use cases have surfaced.
135
136 Because it was removed, the status of the Link header is unclear,
137 leading some to consider minting new application-specific HTTP
138 headers instead of reusing it. This document addresses this by re-
139 specifying the Link header as one such serialisation, with updated
140 but backwards-compatible syntax.
141
142 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Notational Conventions</span>
143
144 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
145 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
146 document are to be interpreted as described in <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>], as
147 scoped to those conformance targets.
148
149 This document uses the Augmented Backus-Naur Form (ABNF) notation of
150 [<a href="./rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>], and explicitly includes the following rules from it:
151 quoted-string, token, SP (space), LOALPHA, DIGIT.
152
153 Additionally, the following rules are included from [<a href="./rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>]: URI
154 and URI-Reference; from [<a href="./rfc4288" title="&quot;Media Type Specifications and Registration Procedures&quot;">RFC4288</a>]: type-name and subtype-name; from
155 [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]: MediaDesc; from [<a href="./rfc5646" title="&quot;Tags for Identifying Languages&quot;">RFC5646</a>]: Language-Tag;
156 and from [<a href="./rfc5987" title="&quot;Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters&quot;">RFC5987</a>], ext-value and parmname.
157
158
159
160
161
162
163
164 <span class="grey">Nottingham Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
167
168
169 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Links</span>
170
171 In this specification, a link is a typed connection between two
172 resources that are identified by Internationalised Resource
173 Identifiers (IRIs) [<a href="./rfc3987" title="&quot;Internationalized Resource Identifiers (IRIs)&quot;">RFC3987</a>], and is comprised of:
174
175 o A context IRI,
176
177 o a link relation type (<a href="#section-4">Section 4</a>),
178
179 o a target IRI, and
180
181 o optionally, target attributes.
182
183 A link can be viewed as a statement of the form "{context IRI} has a
184 {relation type} resource at {target IRI}, which has {target
185 attributes}".
186
187 Note that in the common case, the context IRI will also be a URI
188 [<a href="./rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>], because many protocols (such as HTTP) do not support
189 dereferencing IRIs. Likewise, the target IRI will be converted to a
190 URI (see <a href="./rfc3987#section-3.1">[RFC3987], Section&nbsp;3.1</a>) in serialisations that do not
191 support IRIs (e.g., the Link header).
192
193 This specification does not place restrictions on the cardinality of
194 links; there can be multiple links to and from a particular IRI, and
195 multiple links of different types between two given IRIs. Likewise,
196 the relative ordering of links in any particular serialisation, or
197 between serialisations (e.g., the Link header and in-content links)
198 is not specified or significant in this specification; applications
199 that wish to consider ordering significant can do so.
200
201 Target attributes are a set of key/value pairs that describe the link
202 or its target; for example, a media type hint. This specification
203 does not attempt to coordinate their names or use, but does provide
204 common target attributes for use in the Link HTTP header.
205
206 Finally, this specification does not define a general syntax for
207 expressing links, nor does it mandate a specific context for any
208 given link; it is expected that serialisations of links will specify
209 both aspects. One such serialisation is communication of links
210 through HTTP headers, specified in <a href="#section-5">Section 5</a>.
211
212
213
214
215
216
217
218
219
220 <span class="grey">Nottingham Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
223
224
225 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Link Relation Types</span>
226
227 In the simplest case, a link relation type identifies the semantics
228 of a link. For example, a link with the relation type "copyright"
229 indicates that the resource identified by the target IRI is a
230 statement of the copyright terms applying to the current context IRI.
231
232 Link relation types can also be used to indicate that the target
233 resource has particular attributes, or exhibits particular
234 behaviours; for example, a "service" link implies that the identified
235 resource is part of a defined protocol (in this case, a service
236 description).
237
238 Relation types are not to be confused with media types [<a href="./rfc4288" title="&quot;Media Type Specifications and Registration Procedures&quot;">RFC4288</a>];
239 they do not identify the format of the representation that results
240 when the link is dereferenced. Rather, they only describe how the
241 current context is related to another resource.
242
243 Relation types SHOULD NOT infer any additional semantics based upon
244 the presence or absence of another link relation type, or its own
245 cardinality of occurrence. An exception to this is the combination
246 of the "alternate" and "stylesheet" registered relation types, which
247 has special meaning in HTML4 for historical reasons.
248
249 There are two kinds of relation types: registered and extension.
250
251 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Registered Relation Types</span>
252
253 Well-defined relation types can be registered as tokens for
254 convenience and/or to promote reuse by other applications. This
255 specification establishes an IANA registry of such relation types;
256 see <a href="#section-6.2">Section 6.2</a>.
257
258 Registered relation type names MUST conform to the reg-rel-type rule,
259 and MUST be compared character-by-character in a case-insensitive
260 fashion. They SHOULD be appropriate to the specificity of the
261 relation type; i.e., if the semantics are highly specific to a
262 particular application, the name should reflect that, so that more
263 general names are available for less specific use.
264
265 Registered relation types MUST NOT constrain the media type of the
266 context IRI, and MUST NOT constrain the available representation
267 media types of the target IRI. However, they can specify the
268 behaviours and properties of the target resource (e.g., allowable
269 HTTP methods, request and response media types that must be
270 supported).
271
272
273
274
275
276 <span class="grey">Nottingham Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
279
280
281 Additionally, specific applications of linking may require additional
282 data to be included in the registry. For example, Web browsers might
283 want to know what kinds of links should be downloaded when they
284 archive a Web page; if this application-specific information is in
285 the registry, new link relation types can control this behaviour
286 without unnecessary coordination.
287
288 To accommodate this, per-entry application data can be added to the
289 Link Relation Type registry, by registering it in the Link Relation
290 Application Data registry (<a href="#section-6.3">Section 6.3</a>).
291
292 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Extension Relation Types</span>
293
294 Applications that don't wish to register a relation type can use an
295 extension relation type, which is a URI [<a href="./rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>] that uniquely
296 identifies the relation type. Although the URI can point to a
297 resource that contains a definition of the semantics of the relation
298 type, clients SHOULD NOT automatically access that resource to avoid
299 overburdening its server.
300
301 When extension relation types are compared, they MUST be compared as
302 strings (after converting to URIs if serialised in a different
303 format, such as a Curie [<a href="#ref-W3C.CR-curie-20090116">W3C.CR-curie-20090116</a>]) in a case-
304 insensitive fashion, character-by-character. Because of this, all-
305 lowercase URIs SHOULD be used for extension relations.
306
307 Note that while extension relation types are required to be URIs, a
308 serialisation of links can specify that they are expressed in another
309 form, as long as they can be converted to URIs.
310
311 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. The Link Header Field</span>
312
313 The Link entity-header field provides a means for serialising one or
314 more links in HTTP headers. It is semantically equivalent to the
315 &lt;LINK&gt; element in HTML, as well as the atom:link feed-level element
316 in Atom [<a href="./rfc4287" title="&quot;The Atom Syndication Format&quot;">RFC4287</a>].
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332 <span class="grey">Nottingham Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
335
336
337 Link = "Link" ":" #link-value
338 link-value = "&lt;" URI-Reference "&gt;" *( ";" link-param )
339 link-param = ( ( "rel" "=" relation-types )
340 | ( "anchor" "=" &lt;"&gt; URI-Reference &lt;"&gt; )
341 | ( "rev" "=" relation-types )
342 | ( "hreflang" "=" Language-Tag )
343 | ( "media" "=" ( MediaDesc | ( &lt;"&gt; MediaDesc &lt;"&gt; ) ) )
344 | ( "title" "=" quoted-string )
345 | ( "title*" "=" ext-value )
346 | ( "type" "=" ( media-type | quoted-mt ) )
347 | ( link-extension ) )
348 link-extension = ( parmname [ "=" ( ptoken | quoted-string ) ] )
349 | ( ext-name-star "=" ext-value )
350 ext-name-star = parmname "*" ; reserved for <a href="./rfc2231">RFC2231</a>-profiled
351 ; extensions. Whitespace NOT
352 ; allowed in between.
353 ptoken = 1*ptokenchar
354 ptokenchar = "!" | "#" | "$" | "%" | "&amp;" | "'" | "("
355 | ")" | "*" | "+" | "-" | "." | "/" | DIGIT
356 | ":" | "&lt;" | "=" | "&gt;" | "?" | "@" | ALPHA
357 | "[" | "]" | "^" | "_" | "`" | "{" | "|"
358 | "}" | "~"
359 media-type = type-name "/" subtype-name
360 quoted-mt = &lt;"&gt; media-type &lt;"&gt;
361 relation-types = relation-type
362 | &lt;"&gt; relation-type *( 1*SP relation-type ) &lt;"&gt;
363 relation-type = reg-rel-type | ext-rel-type
364 reg-rel-type = LOALPHA *( LOALPHA | DIGIT | "." | "-" )
365 ext-rel-type = URI
366
367 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Target IRI</span>
368
369 Each link-value conveys one target IRI as a URI-Reference (after
370 conversion to one, if necessary; see <a href="./rfc3987#section-3.1">[RFC3987], Section&nbsp;3.1</a>) inside
371 angle brackets ("&lt;&gt;"). If the URI-Reference is relative, parsers
372 MUST resolve it as per <a href="./rfc3986#section-5">[RFC3986], Section&nbsp;5</a>. Note that any base IRI
373 from the message's content is not applied.
374
375 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Context IRI</span>
376
377 By default, the context of a link conveyed in the Link header field
378 is the IRI of the requested resource.
379
380 When present, the anchor parameter overrides this with another URI,
381 such as a fragment of this resource, or a third resource (i.e., when
382 the anchor value is an absolute URI). If the anchor parameter's
383
384
385
386
387
388 <span class="grey">Nottingham Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
391
392
393 value is a relative URI, parsers MUST resolve it as per <a href="./rfc3986#section-5">[RFC3986],
394 Section&nbsp;5</a>. Note that any base URI from the body's content is not
395 applied.
396
397 Consuming implementations can choose to ignore links with an anchor
398 parameter. For example, the application in use may not allow the
399 context IRI to be assigned to a different resource. In such cases,
400 the entire link is to be ignored; consuming implementations MUST NOT
401 process the link without applying the anchor.
402
403 Note that depending on HTTP status code and response headers, the
404 context IRI might be "anonymous" (i.e., no context IRI is available).
405 For instance, this is the case on a 404 response to a GET request.
406
407 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Relation Type</span>
408
409 The relation type of a link is conveyed in the "rel" parameter's
410 value. The "rel" parameter MUST NOT appear more than once in a given
411 link-value; occurrences after the first MUST be ignored by parsers.
412
413 The "rev" parameter has been used in the past to indicate that the
414 semantics of the relationship are in the reverse direction. That is,
415 a link from A to B with REL="X" expresses the same relationship as a
416 link from B to A with REV="X". "rev" is deprecated by this
417 specification because it often confuses authors and readers; in most
418 cases, using a separate relation type is preferable.
419
420 Note that extension relation types are REQUIRED to be absolute URIs
421 in Link headers, and MUST be quoted if they contain a semicolon (";")
422 or comma (",") (as these characters are used as delimiters in the
423 header itself).
424
425 <span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Target Attributes</span>
426
427 The "hreflang", "media", "title", "title*", "type", and any link-
428 extension link-params are considered to be target attributes for the
429 link.
430
431 The "hreflang" parameter, when present, is a hint indicating what the
432 language of the result of dereferencing the link should be. Note
433 that this is only a hint; for example, it does not override the
434 Content-Language header of a HTTP response obtained by actually
435 following the link. Multiple "hreflang" parameters on a single link-
436 value indicate that multiple languages are available from the
437 indicated resource.
438
439
440
441
442
443
444 <span class="grey">Nottingham Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
447
448
449 The "media" parameter, when present, is used to indicate intended
450 destination medium or media for style information (see
451 [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>], Section 6.13). Note that this may be
452 updated by [<a href="#ref-W3C.CR-css3-mediaqueries-20090915">W3C.CR-css3-mediaqueries-20090915</a>]). Its value MUST be
453 quoted if it contains a semicolon (";") or comma (","), and there
454 MUST NOT be more than one "media" parameter in a link-value.
455
456 The "title" parameter, when present, is used to label the destination
457 of a link such that it can be used as a human-readable identifier
458 (e.g., a menu entry) in the language indicated by the Content-
459 Language header (if present). The "title" parameter MUST NOT appear
460 more than once in a given link-value; occurrences after the first
461 MUST be ignored by parsers.
462
463 The "title*" parameter can be used to encode this label in a
464 different character set, and/or contain language information as per
465 [<a href="./rfc5987" title="&quot;Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters&quot;">RFC5987</a>]. The "title*" parameter MUST NOT appear more than once in
466 a given link-value; occurrences after the first MUST be ignored by
467 parsers. If the parameter does not contain language information, its
468 language is indicated by the Content-Language header (when present).
469
470 If both the "title" and "title*" parameters appear in a link-value,
471 processors SHOULD use the "title*" parameter's value.
472
473 The "type" parameter, when present, is a hint indicating what the
474 media type of the result of dereferencing the link should be. Note
475 that this is only a hint; for example, it does not override the
476 Content-Type header of a HTTP response obtained by actually following
477 the link. There MUST NOT be more than one type parameter in a link-
478 value.
479
480 <span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. Examples</span>
481
482 For example:
483
484 Link: &lt;http://example.com/TheBook/chapter2&gt;; rel="previous";
485 title="previous chapter"
486
487 indicates that "chapter2" is previous to this resource in a logical
488 navigation path.
489
490 Similarly,
491
492 Link: &lt;/&gt;; rel="http://example.net/foo"
493
494 indicates that the root resource ("/") is related to this resource
495 with the extension relation type "http://example.net/foo".
496
497
498
499
500 <span class="grey">Nottingham Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
503
504
505 The example below shows an instance of the Link header encoding
506 multiple links, and also the use of <a href="./rfc2231">RFC 2231</a> encoding to encode both
507 non-ASCII characters and language information.
508
509 Link: &lt;/TheBook/chapter2&gt;;
510 rel="previous"; title*=UTF-8'de'letztes%20Kapitel,
511 &lt;/TheBook/chapter4&gt;;
512 rel="next"; title*=UTF-8'de'n%c3%a4chstes%20Kapitel
513
514 Here, both links have titles encoded in UTF-8, use the German
515 language ("de"), and the second link contains the Unicode code point
516 U+00E4 ("LATIN SMALL LETTER A WITH DIAERESIS").
517
518 Note that link-values can convey multiple links between the same
519 target and context IRIs; for example:
520
521 Link: &lt;http://example.org/&gt;;
522 rel="start http://example.net/relation/other"
523
524 Here, the link to "http://example.org/" has the registered relation
525 type "start" and the extension relation type
526 "http://example.net/relation/other".
527
528 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
529
530 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Link HTTP Header Registration</span>
531
532 This specification updates the Message Header registry entry for
533 "Link" in HTTP [<a href="./rfc3864" title="&quot;Registration Procedures for Message Header Fields&quot;">RFC3864</a>] to refer to this document.
534
535 Header field: Link
536 Applicable protocol: http
537 Status: standard
538 Author/change controller:
539 IETF ([email protected])
540 Internet Engineering Task Force
541 Specification document(s):
542 [<a href="./rfc5988">RFC5988</a>]
543
544 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Link Relation Type Registry</span>
545
546 This specification establishes the Link Relation Type registry, and
547 updates Atom [<a href="./rfc4287" title="&quot;The Atom Syndication Format&quot;">RFC4287</a>] to refer to it in place of the "Registry of
548 Link Relations".
549
550 The underlying registry data (e.g., the XML file) must include
551 Simplified BSD License text as described in <a href="#section-4">Section 4</a>.e of the Trust
552 Legal Provisions (&lt;<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>&gt;).
553
554
555
556 <span class="grey">Nottingham Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
559
560
561 <span class="h4"><a class="selflink" id="section-6.2.1" href="#section-6.2.1">6.2.1</a>. Registering New Link Relation Types</span>
562
563 Relation types are registered on the advice of a Designated Expert
564 (appointed by the IESG or their delegate), with a Specification
565 Required (using terminology from [<a href="./rfc5226" title="">RFC5226</a>]).
566
567 The requirements for registered relation types are described in
568 <a href="#section-4.1">Section 4.1</a>.
569
570 Registration requests consist of the completed registration template
571 below, typically published in an RFC or Open Standard (in the sense
572 described by <a href="./rfc2026#section-7">[RFC2026], Section&nbsp;7</a>). However, to allow for the
573 allocation of values prior to publication, the Designated Expert may
574 approve registration once they are satisfied that a specification
575 will be published.
576
577 Note that relation types can be registered by third parties, if the
578 Designated Expert determines that an unregistered relation type is
579 widely deployed and not likely to be registered in a timely manner.
580
581 The registration template is:
582
583 o Relation Name:
584
585 o Description:
586
587 o Reference:
588
589 o Notes: [optional]
590
591 o Application Data: [optional]
592
593 Registration requests should be sent to the [email protected]
594 mailing list, marked clearly in the subject line (e.g., "NEW RELATION
595 - example" to register an "example" relation type).
596
597 Within at most 14 days of the request, the Designated Expert(s) will
598 either approve or deny the registration request, communicating this
599 decision to the review list and IANA. Denials should include an
600 explanation and, if applicable, suggestions as to how to make the
601 request successful.
602
603 Decisions (or lack thereof) made by the Designated Expert can be
604 first appealed to Application Area Directors (contactable using
605 [email protected] email address or directly by looking up their
606 email addresses on <a href="http://www.iesg.org/">http://www.iesg.org/</a> website) and, if the
607 appellant is not satisfied with the response, to the full IESG (using
608 the [email protected] mailing list).
609
610
611
612 <span class="grey">Nottingham Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
615
616
617 IANA should only accept registry updates from the Designated
618 Expert(s), and should direct all requests for registration to the
619 review mailing list.
620
621 <span class="h4"><a class="selflink" id="section-6.2.2" href="#section-6.2.2">6.2.2</a>. Initial Registry Contents</span>
622
623 The Link Relation Type registry's initial contents are:
624
625 o Relation Name: alternate
626 o Description: Designates a substitute for the link's context.
627 o Reference: [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]
628
629 o Relation Name: appendix
630 o Description: Refers to an appendix.
631 o Reference: [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]
632
633 o Relation Name: bookmark
634 o Description: Refers to a bookmark or entry point.
635 o Reference: [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]
636
637 o Relation Name: chapter
638 o Description: Refers to a chapter in a collection of resources.
639 o Reference: [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]
640
641 o Relation Name: contents
642 o Description: Refers to a table of contents.
643 o Reference: [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]
644
645 o Relation Name: copyright
646 o Description: Refers to a copyright statement that applies to the
647 link's context.
648 o Reference: [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]
649
650 o Relation Name: current
651 o Description: Refers to a resource containing the most recent
652 item(s) in a collection of resources.
653 o Reference: [<a href="./rfc5005" title="&quot;Feed Paging and Archiving&quot;">RFC5005</a>]
654
655 o Relation Name: describedby
656 o Description: Refers to a resource providing information about the
657 link's context.
658 o Documentation: &lt;<a href="http://www.w3.org/TR/powder-dr/#assoc-linking">http://www.w3.org/TR/powder-dr/#assoc-linking</a>&gt;
659
660 o Relation Name: edit
661 o Description: Refers to a resource that can be used to edit the
662 link's context.
663 o Reference: [<a href="./rfc5023" title="&quot;The Atom Publishing Protocol&quot;">RFC5023</a>]
664
665
666
667
668 <span class="grey">Nottingham Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
671
672
673 o Relation Name: edit-media
674 o Description: Refers to a resource that can be used to edit media
675 associated with the link's context.
676 o Reference: [<a href="./rfc5023" title="&quot;The Atom Publishing Protocol&quot;">RFC5023</a>]
677
678 o Relation Name: enclosure
679 o Description: Identifies a related resource that is potentially
680 large and might require special handling.
681 o Reference: [<a href="./rfc4287" title="&quot;The Atom Syndication Format&quot;">RFC4287</a>]
682
683 o Relation Name: first
684 o Description: An IRI that refers to the furthest preceding resource
685 in a series of resources.
686 o Reference: [<a href="./rfc5988">RFC5988</a>]
687 o Notes: this relation type registration did not indicate a
688 reference. Originally requested by Mark Nottingham in December
689 2004.
690
691 o Relation Name: glossary
692 o Description: Refers to a glossary of terms.
693 o Reference: [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]
694
695 o Relation Name: help
696 o Description: Refers to a resource offering help (more information,
697 links to other sources information, etc.)
698 o Reference: [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]
699
700 o Relation Name: hub
701 o Description: Refers to a hub that enables registration for
702 notification of updates to the context.
703 o Reference: &lt;<a href="http://pubsubhubbub.googlecode.com/">http://pubsubhubbub.googlecode.com/</a>&gt; &lt;<a href="http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.3.html">http://</a>
704 <a href="http://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.3.html">pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.3.html</a>&gt;
705 o Notes: this relation type was requested by Brett Slatkin.
706
707 o Relation Name: index
708 o Description: Refers to an index.
709 o Reference: [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]
710
711 o Relation Name: last
712 o Description: An IRI that refers to the furthest following resource
713 in a series of resources.
714 o Reference: [<a href="./rfc5988">RFC5988</a>]
715 o Notes: this relation type registration did not indicate a
716 reference. Originally requested by Mark Nottingham in December
717 2004.
718
719
720
721
722
723
724 <span class="grey">Nottingham Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
727
728
729 o Relation Name: latest-version
730 o Description: Points to a resource containing the latest (e.g.,
731 current) version of the context.
732 o Reference: [<a href="./rfc5829" title="&quot;Link Relation Types for Simple Version Navigation between Web Resources&quot;">RFC5829</a>]
733
734 o Relation Name: license
735 o Description: Refers to a license associated with the link's
736 context.
737 o Reference: [<a href="./rfc4946" title="&quot;Atom License Extension&quot;">RFC4946</a>]
738
739 o Relation Name: next
740 o Description: Refers to the next resource in a ordered series of
741 resources.
742 o Reference: [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]
743
744 o Relation Name: next-archive
745 o Description: Refers to the immediately following archive resource.
746 o Reference: [<a href="./rfc5005" title="&quot;Feed Paging and Archiving&quot;">RFC5005</a>]
747
748 o Relation Name: payment
749 o Description: indicates a resource where payment is accepted.
750 o Reference: [<a href="./rfc5988">RFC5988</a>]
751 o Notes: this relation type registration did not indicate a
752 reference. Requested by Joshua Kinberg and Robert Sayre. It is
753 meant as a general way to facilitate acts of payment, and thus
754 this specification makes no assumptions on the type of payment or
755 transaction protocol. Examples may include a Web page where
756 donations are accepted or where goods and services are available
757 for purchase. rel="payment" is not intended to initiate an
758 automated transaction. In Atom documents, a link element with a
759 rel="payment" attribute may exist at the feed/channel level and/or
760 the entry/item level. For example, a rel="payment" link at the
761 feed/channel level may point to a "tip jar" URI, whereas an entry/
762 item containing a book review may include a rel="payment" link
763 that points to the location where the book may be purchased
764 through an online retailer.
765
766 o Relation Name: prev
767 o Description: Refers to the previous resource in an ordered series
768 of resources. Synonym for "previous".
769 o Reference: [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]
770
771 o Relation Name: predecessor-version
772 o Description: Points to a resource containing the predecessor
773 version in the version history.
774 o Reference: [<a href="./rfc5829" title="&quot;Link Relation Types for Simple Version Navigation between Web Resources&quot;">RFC5829</a>]
775
776
777
778
779
780 <span class="grey">Nottingham Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
783
784
785 o Relation Name: previous
786 o Description: Refers to the previous resource in an ordered series
787 of resources. Synonym for "prev".
788 o Reference: [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]
789
790 o Relation Name: prev-archive
791 o Description: Refers to the immediately preceding archive resource.
792 o Reference: [<a href="./rfc5005" title="&quot;Feed Paging and Archiving&quot;">RFC5005</a>]
793
794 o Relation Name: related
795 o Description: Identifies a related resource.
796 o Reference: [<a href="./rfc4287" title="&quot;The Atom Syndication Format&quot;">RFC4287</a>]
797
798 o Relation Name: replies
799 o Description: Identifies a resource that is a reply to the context
800 of the link.
801 o Reference: [<a href="./rfc4685" title="&quot;Atom Threading Extensions&quot;">RFC4685</a>]
802
803 o Relation Name: section
804 o Description: Refers to a section in a collection of resources.
805 o Reference: [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]
806
807 o Relation Name: self
808 o Description: Conveys an identifier for the link's context.
809 o Reference: [<a href="./rfc4287" title="&quot;The Atom Syndication Format&quot;">RFC4287</a>]
810
811 o Relation Name: service
812 o Description: Indicates a URI that can be used to retrieve a
813 service document.
814 o Reference: [<a href="./rfc5023" title="&quot;The Atom Publishing Protocol&quot;">RFC5023</a>]
815 o Notes: When used in an Atom document, this relation type specifies
816 Atom Publishing Protocol service documents by default. Requested
817 by James Snell.
818
819 o Relation Name: start
820 o Description: Refers to the first resource in a collection of
821 resources.
822 o Reference: [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]
823
824 o Relation Name: stylesheet
825 o Description: Refers to an external style sheet.
826 o Reference: [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]
827
828 o Relation Name: subsection
829 o Description: Refers to a resource serving as a subsection in a
830 collection of resources.
831 o Reference: [<a href="#ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]
832
833
834
835
836 <span class="grey">Nottingham Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
839
840
841 o Relation Name: successor-version
842 o Description: Points to a resource containing the successor version
843 in the version history.
844 o Reference: [<a href="./rfc5829" title="&quot;Link Relation Types for Simple Version Navigation between Web Resources&quot;">RFC5829</a>]
845
846 o Relation Name: up
847 o Description: Refers to a parent document in a hierarchy of
848 documents.
849 o Reference: [<a href="./rfc5988">RFC5988</a>]
850 o Notes: this relation type registration did not indicate a
851 reference. Requested by Noah Slater.
852
853 o Relation Name: version-history
854 o Description: points to a resource containing the version history
855 for the context.
856 o Reference: [<a href="./rfc5829" title="&quot;Link Relation Types for Simple Version Navigation between Web Resources&quot;">RFC5829</a>]
857
858 o Relation Name: via
859 o Description: Identifies a resource that is the source of the
860 information in the link's context.
861 o Reference: [<a href="./rfc4287" title="&quot;The Atom Syndication Format&quot;">RFC4287</a>]
862
863 o Relation Name: working-copy
864 o Description: Points to a working copy for this resource.
865 o Reference: [<a href="./rfc5829" title="&quot;Link Relation Types for Simple Version Navigation between Web Resources&quot;">RFC5829</a>]
866
867 o Relation Name: working-copy-of
868 o Description: Points to the versioned resource from which this
869 working copy was obtained.
870 o Reference: [<a href="./rfc5829" title="&quot;Link Relation Types for Simple Version Navigation between Web Resources&quot;">RFC5829</a>]
871
872 <span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Link Relation Application Data Registry</span>
873
874 This specification also establishes the Link Relation Application
875 Field registry, to allow entries in the Link Relation Type registry
876 to be extended with application-specific data (hereafter, "app data")
877 specific to all instances of a given link relation type.
878
879 Application data is registered on the advice of a Designated Expert
880 (appointed by the IESG or their delegate), with a Specification
881 Required (using terminology from [<a href="./rfc5226" title="">RFC5226</a>]).
882
883
884
885
886
887
888
889
890
891
892 <span class="grey">Nottingham Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
895
896
897 Registration requests consist of the completed registration template
898 below:
899
900 o Application Name:
901
902 o Description:
903
904 o Default Value:
905
906 o Notes: [optional]
907
908 The Description SHOULD identify the value space of the app data. The
909 Default Value MUST be appropriate to entries to which the app data
910 does not apply.
911
912 Entries that pre-date the addition of app data will automatically be
913 considered to have the default value for that app data; if there are
914 exceptions, the modification of such entries should be coordinated by
915 the Designated Expert(s), in consultation with the author of the
916 proposed app data as well as the registrant of the existing entry (if
917 possible).
918
919 Registration requests should be sent to the [email protected]
920 mailing list, marked clearly in the subject line (e.g., "NEW APP DATA
921 - example" to register "example" app data).
922
923 Within at most 14 days of the request, the Designated Expert will
924 either approve or deny the registration request, communicating this
925 decision to the review list. Denials should include an explanation
926 and, if applicable, suggestions as to how to make the request
927 successful. Registration requests that are undetermined for a period
928 longer than 21 days can be brought to the IESG's attention (using the
929 [email protected] mailing list) for resolution.
930
931 When a registration request is successful, the Designated Expert will
932 forward it to IANA for publication. IANA should only accept registry
933 updates from the Designated Expert(s), and should direct all requests
934 for registration to the review mailing list.
935
936 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
937
938 The content of the Link header field is not secure, private or
939 integrity-guaranteed, and due caution should be exercised when using
940 it. Use of Transport Layer Security (TLS) with HTTP ([<a href="./rfc2818" title="&quot;HTTP Over TLS&quot;">RFC2818</a>] and
941 [<a href="./rfc2817" title="&quot;Upgrading to TLS Within HTTP/1.1&quot;">RFC2817</a>]) is currently the only end-to-end way to provide such
942 protection.
943
944
945
946
947
948 <span class="grey">Nottingham Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
951
952
953 Applications that take advantage of typed links should consider the
954 attack vectors opened by automatically following, trusting, or
955 otherwise using links gathered from HTTP headers. In particular,
956 Link headers that use the "anchor" parameter to associate a link's
957 context with another resource should be treated with due caution.
958
959 The Link entity-header field makes extensive use of IRIs and URIs.
960 See [<a href="./rfc3987" title="&quot;Internationalized Resource Identifiers (IRIs)&quot;">RFC3987</a>] for security considerations relating to IRIs. See
961 [<a href="./rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>] for security considerations relating to URIs. See
962 [<a href="./rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>] for security considerations relating to HTTP headers.
963
964 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Internationalisation Considerations</span>
965
966 Target IRIs may need to be converted to URIs in order to express them
967 in serialisations that do not support IRIs. This includes the Link
968 HTTP header.
969
970 Similarly, the anchor parameter of the Link header does not support
971 IRIs, and therefore IRIs must be converted to URIs before inclusion
972 there.
973
974 Relation types are defined as URIs, not IRIs, to aid in their
975 comparison. It is not expected that they will be displayed to end
976 users.
977
978 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
979
980 <span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span>
981
982 [<a id="ref-RFC2026">RFC2026</a>] Bradner, S., "The Internet Standards Process -- Revision
983 3", <a href="https://www.rfc-editor.org/bcp/bcp9">BCP 9</a>, <a href="./rfc2026">RFC 2026</a>, October 1996.
984
985 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
986 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
987
988 [<a id="ref-RFC2616">RFC2616</a>] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
989 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
990 Transfer Protocol -- HTTP/1.1", <a href="./rfc2616">RFC 2616</a>, June 1999.
991
992 [<a id="ref-RFC3864">RFC3864</a>] Klyne, G., Nottingham, M., and J. Mogul, "Registration
993 Procedures for Message Header Fields", <a href="https://www.rfc-editor.org/bcp/bcp90">BCP 90</a>, <a href="./rfc3864">RFC 3864</a>,
994 September 2004.
995
996 [<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
997 Resource Identifier (URI): Generic Syntax", STD 66,
998 <a href="./rfc3986">RFC 3986</a>, January 2005.
999
1000
1001
1002
1003
1004 <span class="grey">Nottingham Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
1007
1008
1009 [<a id="ref-RFC3987">RFC3987</a>] Duerst, M. and M. Suignard, "Internationalized Resource
1010 Identifiers (IRIs)", <a href="./rfc3987">RFC 3987</a>, January 2005.
1011
1012 [<a id="ref-RFC4288">RFC4288</a>] Freed, N. and J. Klensin, "Media Type Specifications and
1013 Registration Procedures", <a href="https://www.rfc-editor.org/bcp/bcp13">BCP 13</a>, <a href="./rfc4288">RFC 4288</a>, December 2005.
1014
1015 [<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
1016 IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
1017 May 2008.
1018
1019 [<a id="ref-RFC5646">RFC5646</a>] Phillips, A. and M. Davis, "Tags for Identifying
1020 Languages", <a href="https://www.rfc-editor.org/bcp/bcp47">BCP 47</a>, <a href="./rfc5646">RFC 5646</a>, September 2009.
1021
1022 [<a id="ref-RFC5987">RFC5987</a>] Reschke, J., "Character Set and Language Encoding for
1023 Hypertext Transfer Protocol (HTTP) Header Field
1024 Parameters", <a href="./rfc5987">RFC 5987</a>, August 2010.
1025
1026 <span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
1027
1028 [<a id="ref-RFC2068">RFC2068</a>] Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T.
1029 Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1",
1030 <a href="./rfc2068">RFC 2068</a>, January 1997.
1031
1032 [<a id="ref-RFC2817">RFC2817</a>] Khare, R. and S. Lawrence, "Upgrading to TLS Within
1033 HTTP/1.1", <a href="./rfc2817">RFC 2817</a>, May 2000.
1034
1035 [<a id="ref-RFC2818">RFC2818</a>] Rescorla, E., "HTTP Over TLS", <a href="./rfc2818">RFC 2818</a>, May 2000.
1036
1037 [<a id="ref-RFC4287">RFC4287</a>] Nottingham, M., Ed. and R. Sayre, Ed., "The Atom
1038 Syndication Format", <a href="./rfc4287">RFC 4287</a>, December 2005.
1039
1040 [<a id="ref-RFC4685">RFC4685</a>] Snell, J., "Atom Threading Extensions", <a href="./rfc4685">RFC 4685</a>,
1041 September 2006.
1042
1043 [<a id="ref-RFC4946">RFC4946</a>] Snell, J., "Atom License Extension", <a href="./rfc4946">RFC 4946</a>, July 2007.
1044
1045 [<a id="ref-RFC5005">RFC5005</a>] Nottingham, M., "Feed Paging and Archiving", <a href="./rfc5005">RFC 5005</a>,
1046 September 2007.
1047
1048 [<a id="ref-RFC5023">RFC5023</a>] Gregorio, J. and B. de hOra, "The Atom Publishing
1049 Protocol", <a href="./rfc5023">RFC 5023</a>, October 2007.
1050
1051 [<a id="ref-RFC5829">RFC5829</a>] Brown, A., Clemm, G., and J. Reschke, "Link Relation Types
1052 for Simple Version Navigation between Web Resources",
1053 <a href="./rfc5829">RFC 5829</a>, April 2010.
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Nottingham Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
1063
1064
1065 [<a id="ref-W3C.CR-css3-mediaqueries-20090915">W3C.CR-css3-mediaqueries-20090915</a>]
1066 van Kesteren, A., Glazman, D., Lie, H., and T. Celik,
1067 "Media Queries", W3C Candidate Recommendation CR-css3-
1068 mediaqueries-20090915, September 2009,
1069 &lt;<a href="http://www.w3.org/TR/2009/CR-css3-mediaqueries-20090915/">http://www.w3.org/TR/2009/</a>
1070 <a href="http://www.w3.org/TR/2009/CR-css3-mediaqueries-20090915/">CR-css3-mediaqueries-20090915/</a>&gt;.
1071
1072 Latest version available at
1073 &lt;<a href="http://www.w3.org/TR/css3-mediaqueries/">http://www.w3.org/TR/css3-mediaqueries/</a>&gt;.
1074
1075 [<a id="ref-W3C.CR-curie-20090116">W3C.CR-curie-20090116</a>]
1076 Birbeck, M. and S. McCarron, "CURIE Syntax 1.0", W3C
1077 Candidate Recommendation CR-curie-20090116, January 2009,
1078 &lt;<a href="http://www.w3.org/TR/2009/CR-curie-20090116">http://www.w3.org/TR/2009/CR-curie-20090116</a>&gt;.
1079
1080 Latest version available at &lt;<a href="http://www.w3.org/TR/curie">http://www.w3.org/TR/curie</a>&gt;.
1081
1082 [<a id="ref-W3C.REC-html401-19991224">W3C.REC-html401-19991224</a>]
1083 Le Hors, A., Raggett, D., and I. Jacobs, "HTML 4.01
1084 Specification", W3C Recommendation REC-html401-19991224,
1085 December 1999,
1086 &lt;<a href="http://www.w3.org/TR/1999/REC-html401-19991224">http://www.w3.org/TR/1999/REC-html401-19991224</a>&gt;.
1087
1088 Latest version available at
1089 &lt;<a href="http://www.w3.org/TR/html401">http://www.w3.org/TR/html401</a>&gt;.
1090
1091 [<a id="ref-W3C.REC-rdfa-syntax-20081014">W3C.REC-rdfa-syntax-20081014</a>]
1092 Adida, B., Birbeck, M., McCarron, S., and S. Pemberton,
1093 "RDFa in XHTML: Syntax and Processing", W3C
1094 Recommendation REC-rdfa-syntax-20081014, October 2008,
1095 &lt;<a href="http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014">http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014</a>&gt;.
1096
1097 Latest version available at
1098 &lt;<a href="http://www.w3.org/TR/rdfa-syntax">http://www.w3.org/TR/rdfa-syntax</a>&gt;.
1099
1100 [<a id="ref-W3C.REC-xhtml-basic-20080729">W3C.REC-xhtml-basic-20080729</a>]
1101 Baker, M., Ishikawa, M., Stark, P., Matsui, S., Wugofski,
1102 T., and T. Yamakami, "XHTML[TM] Basic 1.1", W3C
1103 Recommendation REC-xhtml-basic-20080729, July 2008,
1104 &lt;<a href="http://www.w3.org/TR/2008/REC-xhtml-basic-20080729">http://www.w3.org/TR/2008/REC-xhtml-basic-20080729</a>&gt;.
1105
1106 Latest version available at
1107 &lt;<a href="http://www.w3.org/TR/xhtml-basic">http://www.w3.org/TR/xhtml-basic</a>&gt;.
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Nottingham Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
1119
1120
1121 <span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Notes on Using the Link Header with the HTML4 Format</span>
1122
1123 HTML motivated the original syntax of the Link header, and many of
1124 the design decisions in this document are driven by a desire to stay
1125 compatible with these uses.
1126
1127 In HTML4, the link element can be mapped to links as specified here
1128 by using the "href" attribute for the target URI, and "rel" to convey
1129 the relation type, as in the Link header. The context of the link is
1130 the URI associated with the entire HTML document.
1131
1132 All of the link relation types defined by HTML4 have been included in
1133 the Link Relation Type registry, so they can be used without
1134 modification. However, there are several potential ways to serialise
1135 extension relation types into HTML4, including
1136
1137 o As absolute URIs,
1138
1139 o using the document-wide "profile" attribute's URI as a prefix for
1140 relation types, or
1141
1142 o using the RDFa [<a href="#ref-W3C.REC-rdfa-syntax-20081014">W3C.REC-rdfa-syntax-20081014</a>] convention of
1143 mapping token prefixes to URIs (in a manner similar to XML name
1144 spaces) (note that RDFa is only defined to work in XHTML
1145 [<a href="#ref-W3C.REC-xhtml-basic-20080729">W3C.REC-xhtml-basic-20080729</a>], but is sometimes used in HTML4).
1146
1147 Individual applications of linking will therefore need to define how
1148 their extension links should be serialised into HTML4.
1149
1150 Surveys of existing HTML content have shown that unregistered link
1151 relation types that are not URIs are (perhaps inevitably) common.
1152 Consuming HTML implementations should not consider such unregistered
1153 short links to be errors, but rather relation types with a local
1154 scope (i.e., their meaning is specific and perhaps private to that
1155 document).
1156
1157 HTML4 also defines several attributes on links that are not
1158 explicitly defined by the Link header. These attributes can be
1159 serialised as link-extensions to maintain fidelity.
1160
1161 Finally, the HTML4 specification gives a special meaning when the
1162 "alternate" and "stylesheet" relation types coincide in the same
1163 link. Such links should be serialised in the Link header using a
1164 single list of relation-types (e.g., rel="alternate stylesheet") to
1165 preserve this relationship.
1166
1167
1168
1169
1170
1171
1172 <span class="grey">Nottingham Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
1175
1176
1177 <span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Notes on Using the Link Header with the Atom Format</span>
1178
1179 Atom conveys links in the atom:link element, with the "href"
1180 attribute indicating the target IRI and the "rel" attribute
1181 containing the relation type. The context of the link is either a
1182 feed IRI or an entry ID, depending on where it appears; generally,
1183 feed-level links are obvious candidates for transmission as a Link
1184 header.
1185
1186 When serialising an atom:link into a Link header, it is necessary to
1187 convert target IRIs (if used) to URIs.
1188
1189 Atom defines extension relation types in terms of IRIs. This
1190 specification re-defines them as URIs, to simplify and reduce errors
1191 in their comparison.
1192
1193 Atom allows registered link relation types to be serialised as
1194 absolute URIs. Such relation types SHOULD be converted to the
1195 appropriate registered form (e.g.,
1196 "<a href="http://www.iana.org/assignments/relation/self">http://www.iana.org/assignments/relation/self</a>" to "self") so that
1197 they are not mistaken for extension relation types.
1198
1199 Furthermore, Atom link relation types are always compared in a case-
1200 sensitive fashion; therefore, registered link relation types SHOULD
1201 be converted to their registered form (usually, lowercase) when
1202 serialised in an Atom document.
1203
1204 Note also that while the Link header allows multiple relations to be
1205 serialised in a single link, atom:link does not. In this case, a
1206 single link-value may map to several atom:link elements.
1207
1208 As with HTML, atom:link defines some attributes that are not
1209 explicitly mirrored in the Link header syntax, but they can also be
1210 used as link-extensions to maintain fidelity.
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Nottingham Standards Track [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc5988">RFC 5988</a> Web Linking October 2010</span>
1231
1232
1233 <span class="h2"><a class="selflink" id="appendix-C" href="#appendix-C">Appendix C</a>. Acknowledgements</span>
1234
1235 This specification lifts the idea and definition for the Link header
1236 from <a href="./rfc2068">RFC 2068</a>; credit for it belongs entirely to the authors of and
1237 contributors to that document. The link relation type registrations
1238 themselves are sourced from several documents; see the applicable
1239 references.
1240
1241 The author would like to thank the many people who commented upon,
1242 encouraged and gave feedback to this specification, especially
1243 including Frank Ellermann, Roy Fielding, Eran Hammer-Lahav, and
1244 Julian Reschke.
1245
1246 Author's Address
1247
1248 Mark Nottingham
1249
1250 EMail: [email protected]
1251 URI: <a href="http://www.mnot.net/">http://www.mnot.net/</a>
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284 Nottingham Standards Track [Page 23]
1285 </pre>