identity 1.0 documentation

RFC5988:Web Linking

«  RFC5783: Defining Well-Known Uniform Resource Identifiers (URIs)   ::   Contents   ::   ID Token:Implementation  »

RFC5988:Web Linking

Based on http://tools.ietf.org/html/rfc5988

Abstract

This document specifies relation types for Web links, and defines a registry for them. It also defines the use of such links in HTTP headers with the Link header field.

1. Introduction

( http://tools.ietf.org/html/rfc5988#section-1 )

A means of indicating the relationships between resources on the Web, as well as indicating the type of those relationships, has been available for some time in HTML [W3C.REC-html401-19991224], and more recently in Atom [RFC4287]. These mechanisms, although conceptually similar, are separately specified. However, links between resources need not be format specific; it can be useful to have typed links that are independent of their serialisation, especially when a resource has representations in multiple formats.

To this end, this document defines a framework for typed links that isn’t specific to a particular serialisation or application. It does so by redefining the link relation registry established by Atom to have a broader domain, and adding to it the relations that are defined by HTML.

Furthermore, an HTTP header field for conveying typed links was defined in Section 19.6.2.4 of [RFC2068], but removed from [RFC2616], due to a lack of implementation experience. Since then, it has been implemented in some User Agents (e.g., for stylesheets), and several additional use cases have surfaced.

Because it was removed, the status of the Link header is unclear, leading some to consider minting new application-specific HTTP headers instead of reusing it. This document addresses this by re-specifying the Link header as one such serialisation, with updated but backwards-compatible syntax.

«  RFC5783: Defining Well-Known Uniform Resource Identifiers (URIs)   ::   Contents   ::   ID Token:Implementation  »