---
slug: thinker-markus-lanthaler
title: Markus Lanthaler — Hydra and Machine-Readable Web Operations
canonical: https://miscsubjects.com/a/thinker-markus-lanthaler
---

<!-- hierarchy:nav -->
> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Thinkers](https://miscsubjects.com/a/oip-thinkers) › **Markus Lanthaler — Hydra and Machine-Readable Web Operations**
>
> **Shelf:** Thinkers · **Traversal:** self-explaining · hierarchical · voxel-ready
> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)

# Markus Lanthaler — Hydra and Machine-Readable Web Operations

## §SELF — thinker-markus-lanthaler

**What this page is:** A profile of Markus Lanthaler and the Hydra vocabulary for machine-readable web APIs.
**What it explains:** How Hydra makes REST API responses self-describing so machines can discover available operations without prior documentation.
**Why read it:** To understand the closest standardized technology to OIP's goals, and how OIP can inherit Hydra's vocabulary for object descriptions and operations.

### What Hydra Is

Hydra is a vocabulary (a defined set of terms) for describing hypermedia-driven web APIs in RDF (Resource Description Framework, a standard data model for structured data on the web). It was developed by the Hydra W3C Community Group, led by Markus Lanthaler at Graz University of Technology in Austria. Hydra lets an API response include machine-readable descriptions of what operations are available on the returned resources.

### The Problem Lanthaler Solved

A conventional REST API returns data but does not tell the client what it can do with that data. The client must be programmed with out-of-band knowledge — API documentation, SDKs, or hardcoded URL patterns. This breaks when the API changes. Lanthaler asked: what if the response itself described the available operations? Then a generic client could interact with any Hydra-described API without prior knowledge.

### The Key Idea

A Hydra response contains four elements: (1) Operation descriptions — what HTTP methods (GET, POST, PUT, DELETE) are available and what inputs each requires and what outputs each produces, (2) Supported properties — what fields the resource has, their types, and whether they are required, (3) Links — how to navigate to related resources via URL, (4) Status codes — what each possible response means. A machine reading a Hydra response can construct valid requests without ever having seen that API before.

### What Hydra Provides

- `hydra:Operation`: Describes an action available on a resource, including method, expected input format, and possible outputs.
- `hydra:supportedProperty`: Lists the properties of a resource, their data types, and constraints.
- `hydra:Link`: Defines navigable relationships between resources.
- `hydra:StatusCodeDescription`: Explains what each HTTP status code means in the context of that specific operation.
- `hydra:ApiDocumentation`: A discoverable document that describes the entire API in one place.

### What Lanthaler Got Right

- Hydra makes REST APIs self-describing. This eliminates the need for separate API documentation as a prerequisite for machine interaction.
- The vocabulary is built on RDF, so it inherits the entire Linked Data ecosystem — existing parsers, reasoners, and query engines work with Hydra out of the box.
- The design separates the data (the resource) from the affordances (what you can do with it), which matches how hypermedia works on the human web.
- Hydra is standardized through a W3C Community Group, giving it institutional stability and a defined governance process.

### What Lanthaler Got Wrong or Left Unfinished

- Adoption has been limited. Most API developers still prefer OpenAPI/Swagger specifications, which are more widely supported by tooling even though they are not self-describing in responses.
- Hydra does not define a standard for authentication or authorization. A machine can see what operations are available but cannot determine whether it is permitted to execute them.
- The vocabulary is general by design, which means it lacks domain-specific constraints. A Hydra client knows what operations exist but may not know business rules (for example, "you cannot transfer more than your balance").
- Hydra focuses on HTTP APIs. It does not extend naturally to non-HTTP transports or to capabilities as first-class objects.

### How It Connects to Other Ideas

- **REST and HATEOAS**: Hydra is a concrete implementation of HATEOAS (Hypermedia as the Engine of Application State), the principle that a REST API should guide the client through available actions via hypermedia links in responses.
- **Linked Data and RDF**: Hydra is an RDF vocabulary, so any RDF parser can read it. This gives Hydra interoperability with the broader semantic web infrastructure.
- **Object Identity Protocol (OIP)**: Hydra is the most OIP-adjacent standardized technology. OIP can adopt Hydra's `Operation` type for object contracts and `supportedProperty` for input schemas. This would give OIP immediate interoperability with existing Linked Data tools. Where Hydra describes web APIs, OIP describes model-operated objects — but both share the goal of making responses self-describing so a machine can operate them without prior knowledge.
- **OpenAPI/Swagger**: OpenAPI describes APIs in a static document. Hydra describes them in the response itself. OIP should follow Hydra's approach (self-describing responses) rather than OpenAPI's (external specification).

### Sources

- Lanthaler, Markus. "Hydra: A Vocabulary for Hypermedia-Driven Web APIs." W3C Community Group.
- Lanthaler, Markus and Christian Gütl. "On Using JSON-LD to Create Evolvable RESTful Services." Proceedings of the International World Wide Web Conference (WWW), 2012.
- Hydra W3C Community Group: https://www.hydra-cg.com/
- JSON-LD 1.1, W3C Recommendation (the serialization format Hydra uses).

---

## Up the tree

- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry
- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map
- [Thinkers shelf](https://miscsubjects.com/a/oip-thinkers) — siblings on this shelf
- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels
- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)

## Related on this shelf

- [Alan Kay — The Big Idea Is Messaging](https://miscsubjects.com/a/thinker-alan-kay)
- [Alfred North Whitehead — Process and Reality](https://miscsubjects.com/a/thinker-alfred-north-whitehead)
- [J.L. Austin and John Searle — Speech Acts](https://miscsubjects.com/a/thinker-austin-searle)
- [Barbara Liskov — Abstract Data Types and Distributed Consensus](https://miscsubjects.com/a/thinker-barbara-liskov)
- [Bram Cohen — BitTorrent and Content-Addressed Protocol Design](https://miscsubjects.com/a/thinker-bram-cohen)
- [Butler Lampson — Protection and Access Control](https://miscsubjects.com/a/thinker-butler-lampson)
- [Carl Hewitt — The Actor Model](https://miscsubjects.com/a/thinker-carl-hewitt)
- [Charles Sanders Peirce — Signs, Abduction, and Pragmatism](https://miscsubjects.com/a/thinker-charles-peirce)

## Machine surfaces

- Public page: `https://miscsubjects.com/a/thinker-markus-lanthaler`
- JSON article: `https://miscsubjects.com/api/articles/thinker-markus-lanthaler`
- OIP ask: `https://miscsubjects.com/api/dispatch?ask=Markus%20Lanthaler%20%E2%80%94%20Hydra%20and%20Machine-Readable%20Web%20Operations`

