…ce that is closely related to the conceptual model of Links as established in [ RFC5988 ]. The properties of the Link object are not the properties of the referenced resource, but are provided as hints for rendering agents to understand how to make use of the resource. For exampl…
… redirected-to page for discovery. Clients MUST check for an HTTP Link header [ RFC5988 ] with the appropriate rel value. If the content type of the document is HTML, then the client MUST check for an HTML <link> element with the appropriate rel value. If more than one of these i…
…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. …
…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. …
…tax A JSON-LD document is first, and foremost, a JSON document (as defined in [ RFC5988 ]), and any syntactically correct JSON document must be processed by a conforming JSON-LD processor. However, JSON-LD describes a specific syntax to use for expressing Linked Data. This includ…
…^xsd:string ; rdfs:isDefinedBy eop: ; rdfs:seeAlso <https://tools.ietf.org/html/rfc5988> . ianarel:related a owl:ObjectProperty ; rdfs:label "related" ; dc:description "Reference to the location of a related resource, e.g. cloud mask, snow mask." ; dcterms:source "OGC 17-003"^^xs…
…target URL (and follow redirects [ FETCH ]) and check for an HTTP Link header [ RFC5988 ] with a rel value of webmention . If the content type of the document is HTML, then the sender MUST look for an HTML <link> and <a> element with a rel value of webmention . If more than one o…
… 8.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" 8.2.4 JF2 Feed Example E…
…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…
…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…
…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…
…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…