Skip to main content

1. Introduction

This document defines a framework for typed links that is independent of serialization or application format. The concept of typed links has existed in HTML and Atom, but this specification provides a unified approach.

Key Objectives​

  • Establishes a common framework for Web links across different formats
  • Redefines the link relation registry from Atom with broader scope
  • Incorporates HTML-defined relations into the registry
  • Re-specifies the Link HTTP header field (originally in RFC 2068)
  • Provides backwards-compatible syntax
  • Enables link expression in HTTP headers independent of content format

Background​

Historical Context:

  • HTML has supported typed links via <link> elements
  • Atom introduced atom:link for feed-level links
  • RFC 2068 defined Link header but was removed in RFC 2616 due to limited implementation

Current Need:

  • Multiple formats need to express relationships between resources
  • Links should be independent of content serialization
  • Unified registry prevents fragmentation of relation types

Use Cases​

  1. Format Independence: Resources with multiple representations (JSON, XML, HTML) can share link semantics
  2. HTTP Header Links: Convey relationships without parsing message body
  3. Registry Consolidation: Single authoritative source for link relation types

Related Sections:

Last updated on