…ally following, trusting, or otherwise using links gathered from HTTP headers." RFC5988 . REALLY SHOULD NOT The phrase "REALLY SHOULD NOT" is used to indicate dangerous behaviors that some important vendor still does and therefore we were unable to make MUST NOT. For example: "Th…

…n statically specified syntax. Several existing specifications can aid in this. RFC5988 ] specifies relation types for Web links. By providing a framework for linking on the Web, where every link has a relation type, context and target, it allows applications to define a link's s…

…n the problem details object. For example, an extension might use typed links [ RFC5988 ] to another resource that can be used by machines to resolve the problem. If such additional members are defined, their names SHOULD start with a letter (ALPHA, as per [RFC5234], Appendix B.1…

…sting an external stylesheet when processing a Link HTTP response header field [RFC5988] Note: As this stylesheet might be prefetched before a Document actually exists, user agents will need to carefully consider how to instantiate a meaningful policy against which to compare thi…

…ntal model for web links and the "Link Relations" registry are established by [ RFC5988 ]. This specification defines and adds the following additional link relation types to the registry: "about", "preview", "privacy-policy", "terms-of-service", and "type". . "about" The "about"…

…alternative lookup process uses Web-host Metadata [ RFC6415 ] and Web Linking [ RFC5988 ], where the link relation type is "urn:xmpp:alt-connections:websocket" as described in "Discovering Alternative XMPP Connection Methods" [ XEP-0156 ]. Conceptually, the host-meta lookup proce…

… 9.2.3 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= "http://www.example.com/jf2feed.json" 9.2.4 JF2 Feed Example E…

…he alternative lookup process uses Web-host Metadata [RFC6415] and Web Linking [RFC5988], where the link relation type is "urn:xmpp:alt-connections:websocket" as described in "Discovering Alternative XMPP Connection Methods" [XEP-0156]. Conceptually, the host-meta lookup process …

…The link relation type below has been registered by IANA per Section 6.2.1 of [ RFC5988 ]: Relation Name: micropub Description: Used for discovery of a Micropub endpoint which can be used to create posts according to the Micropub protocol. Reference: W3C Micropub Specification (h…

…e relation type used MUST be "describedBy", as defined by RFC 5988, section 5.3 RFC5988 ]. The target URI of the "Link" header MUST be a valid JSON Schema. An example of such a header would be: Link: <http://example.com/my-hyper-schema#>; rel="describedBy" . IANA Considerations T…

…author MUST specify an IRI to a valid JSON-LD document in an HTTP Link Header [ RFC5988 ] using the link relation. The referenced document MUST have a top-level JSON object The @context subtree within that object is added to the top-level JSON object of the referencing document. …

…The link relation type below has been registered by IANA per Section 6.2.1 of [ RFC5988 ]: Relation Name: micropub Description: Used for discovery of a Micropub endpoint which can be used to create posts according to the Micropub protocol. Reference: W3C Micropub Specification (h…

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