….org/html/rfc5646 IETF: RFC 5988 - Web Linking, 2010 http://tools.ietf.org/html/rfc5988, http://www.iana.org/assignments/link-relations/link-relations.xhtml 4. Terms and Definitions This document uses the terms defined in Sub-clause 5.3 of [RD.1], which is based on the ISO/IEC Di…

…wed in between. Notes: RFC5987 clarifies RFC2231 for use in HTTP. The update in RFC5988 left two mentions of RFC2231 which should be updated. Errata ID: 2631 Status: Held for Document Update Type: Editorial Publication Format(s) : TEXT Reported By: Julian Reschke Date Reported: 2…

…tion. It is possible to communicate the list using a set of Link header fields [RFC5988], each with a relationship of "alternate", though deployment is a chicken-and-egg problem. 6.4.2. 301 Moved Permanently The 301 (Moved Permanently) status code indicates that the target resour…

…ion. It is possible to communicate the list using a set of Link header fields [ RFC5988 ], each with a relationship of "alternate", though deployment is a chicken-and-egg problem. 6.4.2 . 301 Moved Permanently The 301 (Moved Permanently) status code indicates that the target reso…

…ion. It is possible to communicate the list using a set of Link header fields [ RFC5988 ], each with a relationship of "alternate", though deployment is a chicken-and-egg problem. 6.4.2 . 301 Moved Permanently The 301 (Moved Permanently) status code indicates that the target reso…

…ion. It is possible to communicate the list using a set of Link header fields [ RFC5988 ], each with a relationship of "alternate", though deployment is a chicken-and-egg problem. 6.4.2 . 301 Moved Permanently The 301 (Moved Permanently) status code indicates that the target reso…

…wed in between. Notes: RFC5987 clarifies RFC2231 for use in HTTP. The update in RFC5988 left two mentions of RFC2231 which should be updated. Errata ID: 2631 Status: Held for Document Update Type: Editorial Publication Format(s) : TEXT Reported By: Julian Reschke Date Reported: 2…

…ion. It is possible to communicate the list using a set of Link header fields [ RFC5988 ], each with a relationship of "alternate", though deployment is a chicken-and-egg problem. 6.4.2 . 301 Moved Permanently The 301 (Moved Permanently) status code indicates that the target reso…

…ion. It is possible to communicate the list using a set of Link header fields [ RFC5988 ], each with a relationship of "alternate", though deployment is a chicken-and-egg problem. 6.4.2 . 301 Moved Permanently The 301 (Moved Permanently) status code indicates that the target reso…

…tion. It is possible to communicate the list using a set of Link header fields [RFC5988], each with a relationship of "alternate", though deployment is a chicken-and-egg problem. 6.4.2. 301 Moved Permanently The 301 (Moved Permanently) status code indicates that the target resour…

…ion. It is possible to communicate the list using a set of Link header fields [ RFC5988 ], each with a relationship of "alternate", though deployment is a chicken-and-egg problem. 6.4.2 . 301 Moved Permanently The 301 (Moved Permanently) status code indicates that the target reso…

…ion. It is possible to communicate the list using a set of Link header fields [ RFC5988 ], each with a relationship of "alternate", though deployment is a chicken-and-egg problem. 6.4.2 . 301 Moved Permanently The 301 (Moved Permanently) status code indicates that the target reso…

…ion. It is possible to communicate the list using a set of Link header fields [ RFC5988 ], each with a relationship of "alternate", though deployment is a chicken-and-egg problem. 6.4.2 . 301 Moved Permanently The 301 (Moved Permanently) status code indicates that the target reso…