7 Key Insights into the Semantic Web's Slow Progress and the Block Protocol Solution

The web began as a space for sharing human-readable documents, but its potential for machine-readable data remains largely untapped. For decades, adding semantic structure—like marking up a book title so computers can understand it—has been a tedious chore. The Block Protocol aims to change that by making structured data effortless. Here are seven essential things you need to know about the journey from HTML to a truly semantic web.

1. The Web's Original Purpose: Publishing for Humans

Since the 1990s, the web has primarily served as a platform for human-readable documents. Content is designed for people to read, not for machines to parse. Early web pages were simple text with basic formatting, and the underlying technology—HTML—was built to present information visually, not to describe its meaning. This human-centric approach worked well for sharing articles, but it created a barrier when we wanted computers to automatically process or connect data. The original vision of the web did not include structured metadata, so even today, most pages remain opaque to software unless explicit effort is made to add semantic layers.

7 Key Insights into the Semantic Web's Slow Progress and the Block Protocol Solution — Source: www.joelonsoftware.com

2. The Limits of HTML Structure

HTML provides minimal structural cues: tags like <p> for paragraphs, <strong> for emphasis. When you mention a book, a human can see that "Goodnight Moon" is the title, but a computer sees only bold text. CSS adds decorative styles—making text tiny and gray, for example—but does not convey meaning. This shallow structure means that applications cannot reliably extract items like book authors, publication dates, or ISBNs without additional markup. The web's architecture was never designed to support rich, machine-readable data, which is why information retrieval often relies on complex heuristics or manual annotation.

3. The Dream of a Semantic Web

As early as 1999, Tim Berners-Lee envisioned a Semantic Web where computers could analyze the full content, links, and transactions online. In his book Weaving the Web, he described intelligent agents handling trade, bureaucracy, and daily life by communicating directly. This vision required web pages to carry structured data—like schema.org definitions for books, events, or people—so that machines could understand not just strings but their roles and relationships. Formats like RDF and JSON-LD were developed to embed this context into HTML. Despite its promise, the Semantic Web remained mostly theoretical because implementation demanded significant extra work from publishers.

4. The Reality: Semantic Markup is Homework

Adding semantic markup to a web page is technically straightforward but mentally draining. You must look up the appropriate schema (e.g., schema.org for a book), choose a format (RDF or JSON-LD), and manually insert the required tags. After crafting a beautiful, human-readable post, the last thing many creators want is to do more coding to make it machine-readable. This friction—often called the "homework problem"—discourages widespread adoption. Without immediate rewards, publishers skip the extra step, leaving the web mostly unstructured. Consequently, the Semantic Web remains an academic ideal rather than a practical reality.

5. Why Most Web Pages Lack Machine-Readable Data

Two decades after Berners-Lee's call, very few websites incorporate meaningful semantic markup. The main obstacle is effort versus payoff: annotating a page yields no tangible benefit for the author unless a third-party application actively consumes that data. Without a critical mass of consumers, publishers have little incentive to invest time. Additionally, existing tools are cumbersome; embedding JSON-LD or RDF often requires copying boilerplate code and tweaking it manually. As a result, the web remains a vast collection of human-readable documents where computers see only text and images, missing the rich metadata that could enable smart search, recommendation, and automation.

6. The Block Protocol: A New Approach to Structure

The Block Protocol (Block) reimagines how web content carries meaning. Instead of forcing authors to dissociate writing from markup, Block embeds structured data directly into blocks—modular, reusable components that combine human-friendly presentation with machine-readable metadata. A block for a book, for example, automatically exposes its title, author, and ISBN in a standardized format, without the creator needing to touch RDF or JSON-LD. This lowers the barrier dramatically: authors can create or use blocks that are both visually appealing and semantically rich. Block is designed to be easy to adopt, turning the homework problem into a simple, intuitive process.

7. The Future: Making Semantic Markup Effortless

The success of the Block Protocol hinges on a simple insight: people will only add semantic markup if doing so is as easy as writing the content itself. By integrating structure into the authoring experience, Block aims to make every web page become a data source automatically. When creators use a block that understands a book, a recipe, or a contact, the markup happens in the background. This could finally realize Berners-Lee's dream, enabling intelligent agents to gather and analyze data at scale. The challenge now is adoption—encouraging platform developers and publishers to embrace blocks and build a new ecosystem where human-readable and machine-readable content coexist seamlessly.

In summary, the Semantic Web has long promised to connect data across the internet, but the effort required has stalled progress. The Block Protocol offers a practical, user-friendly path forward. By lowering the bar for structured data, it could unlock the web's full potential for both humans and machines. The next step is for the community to rally around this vision, making the web smarter—one block at a time.

Tags: