…resource and returns status 451, it SHOULD include a "Link" HTTP header field [ RFC5988 ] whose value is a URI reference [ RFC3986 ] identifying itself. When used for this purpose, the "Link" header field MUST have a "rel" parameter whose value is "blocked-by". The intent is that…

…resource and returns status 451, it SHOULD include a "Link" HTTP header field [ RFC5988 ] whose value is a URI reference [ RFC3986 ] identifying itself. When used for this purpose, the "Link" header field MUST have a "rel" parameter whose value is "blocked-by". The intent is that…

…resource and returns status 451, it SHOULD include a "Link" HTTP header field [ RFC5988 ] whose value is a URI reference [ RFC3986 ] identifying itself. When used for this purpose, the "Link" header field MUST have a "rel" parameter whose value is "blocked-by". The intent is that…

… resource and returns status 451, it SHOULD include a "Link" HTTP header field [RFC5988] whose value is a URI reference [RFC3986] identifying itself. When used for this purpose, the "Link" header field MUST have a "rel" parameter whose value is "blocked-by". The intent is that th…

…resource and returns status 451, it SHOULD include a "Link" HTTP header field [ RFC5988 ] whose value is a URI reference [ RFC3986 ] identifying itself. When used for this purpose, the "Link" header field MUST have a "rel" parameter whose value is "blocked-by". The intent is that…

…resource and returns status 451, it SHOULD include a "Link" HTTP header field [ RFC5988 ] whose value is a URI reference [ RFC3986 ] identifying itself. When used for this purpose, the "Link" header field MUST have a "rel" parameter whose value is "blocked-by". The intent is that…

…verable (if any). 7.2.1. 'ct' Attribute This section defines a new Web Linking [RFC5988] attribute for use with [RFC6690]. The Content-Format code "ct" attribute provides a hint about the Content-Formats this resource returns. Note that this is only a hint, and it does not overri…

…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 resou…

…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…

…S)</li> <li>2015-01-26 - Align usage of Link: rel= to not use single quotes per RFC5988 (SS)</li> </ul> ldpwg Hosted by W3C Systems Team, please report bugs to sysreq@w3.org

…/tools.ietf.org/html/rfc5646 RFC 5988, Web Linking - http://tools.ietf.org/html/rfc5988 3.1 Other References HMA - Heterogeneous Missions Accessibility – Design Methodology, Architecture and Use of Geospatial Standards for the Ground Segment Support of Earth Observation missions …

…ssues Discovery The JF2 Feed for a page may be published as HTTP Link header [[!RFC5988]], or as an HTML <link> or <a> tag element with the following attributes. rel="alternate" type="application/jf2feed+json" href="https://example.com/jf2feed.json" JF2 Feed Example "type": "feed…

….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…

… and the response has a content type application/json and an HTTP Link Header [ RFC5988 ] using the link relation, update the active context using the Context Processing algorithm , passing the context referenced in the HTTP Link Header as local context Set expanded to the result…

….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…