]>

Prahran Australia mnot@mnot.net https://www.mnot.net/

Applications and Real-Time Building Blocks for HTTP APIs link relation This specification defines the Link-Template HTTP header field, providing a means for describing the structure of a link between two resources, so that new links can be generated. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the Building Blocks for HTTP APIs Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .

Introduction defines a syntax for templates that, when expanded using a set of variables, results in a URI . This specification defines a HTTP header field for conveying templates for links in the headers of a HTTP message. It is complimentary to the Link header field defined in , which carries links directly.

Notational Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. This specification uses the following terms from : List, String, Parameter.

The Link-Template Header Field The Link-Template header field is a Structured Field that serializes one or more links into HTTP message metadata. It is semantically equivalent to the Link header field defined in , except that it uses URI Templates to convey the structure of links. Its value is a List of Strings. Each String is a URI Template, and Parameters on it carry associated metadata. For example: indicates that a resource with the relation type "https://example.org/rel/user" can be found by expanding the "username" variable into the template given. The target for the link (as defined in ) is the result of expanding the URI Template (being converted to an absolute URI after expansion, if necessary). The context, relation type and target attributes for the link are determined as defined for the Link header field in . Parameters on a templated link have identical semantics to those of a Link header field. This includes (but is not limited to) the use of the "rel" parameter to convey the relation type, the "anchor" parameter to modify the context IRI, and so on. Parameter values MUST be Strings. Likewise, the requirements for parameters on templated links are the same as those for a Link header field. However, the "anchor" parameter MAY contain a URI Template. For example: ; rel="author" anchor="#{book_id}" ]]> Here, the link to the author for a particular book in a list of books can be found by following the link template. Implementations MUST support all levels of template defined by in both the rel and anchor parameters. This specification defines additional semantics for the "var-base" parameter on templated links; see below.

The 'var-base' parameter When a templated link has a 'var-base' parameter, its value conveys a URI-reference that is used as a base URI for the variable names in the URI template. This allows template variables to be globally identified, rather than specific to the context of use. Dereferencing the URI for a particular variable might lead to more information about the syntax or semantics of that variable; specification of particular formats for this information is out of scope for this document. To determine the URI for a given variable, the value given is used as a base URI in reference resolution (as specified in ). If the resulting URI is still relative, the context of the link is used as the base URI in a further resolution; see . For example: indicates that a resource with the relation type "https://example.org/rel/widget" can be found by expanding the "https://example.org/vars/widget_id" variable into the template given. If the current context of the message that the header appears within is "https://example.org/", the same information could be conveyed by this header field:

Security Considerations The security consideration for the Link header field in and those for URI Templates both apply.

IANA Considerations This specification enters the "Link-Template" into the Hypertext Transfer Protocol (HTTP) Field Name Registry.

Normative References Adobe Fastly greenbytes GmbH The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes. This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230. A URI Template is a compact sequence of characters for describing a range of Uniform Resource Identifiers through variable expansion. This specification defines the URI Template syntax and the process for expanding a URI Template into a URI reference, along with guidelines for the use of URI Templates on the Internet. [STANDARDS-TRACK] A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. [STANDARDS-TRACK] This specification defines a model for the relationships between resources on the Web ("links") and the type of those relationships ("link relation types"). It also defines the serialisation of such links in HTTP headers with the Link header field. This document describes a set of data types and associated algorithms that are intended to make it easier and safer to define and handle HTTP header and trailer fields, known as "Structured Fields", "Structured Headers", or "Structured Trailers". It is intended for use by specifications of new HTTP fields that wish to use a common syntax that is more restrictive than traditional HTTP field values. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.