Linked Data Current Status

This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title links to the most recent version of a document.

Completed Work

W3C Recommendations have been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and are endorsed by the Director as Web Standards. Learn more about the W3C Recommendation Track.

Group Notes are not standards and do not have the same level of W3C endorsement.



Linked Data Notifications

Linked Data Notifications is a protocol to facilitate exchanging messages between applications which serve as senders, receivers and/or consumers of RDF data.


Web Annotation Data Model

The Web Annotation Data Model specfication describes a structured model and format to enable annotations to be shared and reused across different hardware and software platforms to support a wide variety of simple as well as complex application use cases.


Web Annotation Vocabulary

The Web Annotation Vocabulary specifies the set of RDF classes, predicates and named entities that are used by the Web Annotation Data Model. It also lists recommended terms from other ontologies that are used in the model, and provides the JSON-LD Context and profile definitions needed to use the Web Annotation JSON serialization in a Linked Data context.


Web Annotation Protocol

Annotations are typically used to convey information about a resource or associations between resources. Simple examples include a comment or tag on a single web page or image, or a blog post about a news article.

The Web Annotation Protocol describes the transport mechanisms for creating and managing annotations in a method that is consistent with the Web Architecture and REST best practices.


Linked Data Platform 1.0

A set of best practices and simple approach for a read-write Linked Data architecture, based on HTTP access to web resources that describe their state using RDF.


RDF 1.1 Turtle

The Resource Description Framework (RDF) is a general-purpose language for representing information in the Web.


JSON-LD 1.0 Processing Algorithms and API

An Application Programming Interface and a set of algorithms for programmatically transforming JSON-LD documents in order to make them easier to work with in programming environments like JavaScript, Python, and Ruby.



A common JSON representation format for expressing directed graphs; mixing both Linked Data and non-Linked Data in a single JSON document.


The RDF Data Cube Vocabulary

There are many situations where it would be useful to be able to publish multi-dimensional data, such as statistics, on the web in such a way that it can be linked to related data sets and concepts. The Data Cube vocabulary provides a means to do this using the W3C RDF (Resource Description Framework) standard.


Data Catalog Vocabulary (DCAT)

DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. This document defines the schema and provides examples for its use.


The Organization Ontology

This document describes a core ontology for organizational structures, aimed at supporting linked-data publishing of organizational information across a number of domains. It is designed to allow domain-specific extensions to add classification of organzations and roles, as well as extensions to support neighbouring information such as organizational activities.


Internationalization Tag Set (ITS) Version 2.0

This document defines data categories and their implementation as a set of elements and attributes called the Internationalization Tag Set (ITS) 2.0. ITS 2.0 is the successor of ITS 1.0; it is designed to foster the creation of multilingual Web content, focusing on HTML5, XML based formats in general, and to leverage localization workflows based on the XML Localization Interchange File Format (XLIFF). In addition to HTML5 and XML, algorithms to convert ITS attributes to RDFa and NIF are provided.

Group Notes


Linked Data Patch Format

Linked Data Patch Format (LD Patch) defines a language for expressing a sequence of operations to apply to Linked Data resources; it is suitable for use with the HTTP PATCH method.


Linked Data Platform Paging 1.0

This document describes a HTTP-based protocol for clients and servers to be able to efficiently retrieve large Linked Data Platform Resource representations by splitting up the responses into separate URL-addressable page resources.


Linked Data Platform 1.0 Primer

This primer provides an introduction to the Linked Data Platform (LDP), with examples illustrating the principal concepts such as the notion of an LDP resource and the LDP container and how they can be used by Web clients.


LDP Access Control

This note discusses use cases and requirements for Access Control for the Linked Data Platform WG. It also outlines a charter for developing a standard for HTTP-based access control. The work delineated in the charter may be pursued in the Linked Data Platform WG or an independent, related WG.


Linked Data Platform Best Practices and Guidelines

This document provides best practices and guidelines for implementing Linked Data Platform servers and clients.


Linked Data Platform Use Cases and Requirements

A set of user stories, use cases, scenarios and requirements that motivate a simple read-write Linked Data architecture, based on HTTP access to web resources that describe their state using RDF.


Best Practices for Publishing Linked Data

A compilation of Best Practices for publishing data as Linked Data, for when organizations want their data available for use by others. Written with a focus on Government data, but also useful for scientific, commercial, and other open data needs.


Registered Organization Vocabulary

This is a vocabulary for describing organizations that have gained legal entity status through a formal registration process, typically in a national or regional register. This document is the normative companion to the namespace document at http://www.w3.org/ns/regorg.


Use Cases and Lessons for the Data Cube Vocabulary

Many organizations collect and aggregate numeric data into statistics. In this document, the W3C Government Linked Data Working Group presents use cases and lessons supporting a recommendation of the RDF Data Cube Vocabulary. We describe case studies of existing deployments of an earlier version of the Data Cube Vocabulary as well as other possible use cases that would benefit from using the vocabulary.


Linked Data Glossary

The Linked Data Glossary contains terms defined and used to describe Linked Data, and its associated vocabularies and best practices related to publishing structured data on the Web using open Web standards.


Below are draft documents: other Working Drafts . Some of these may become Web Standards through the W3C Recommendation Track process. Others may be published as Group Notes or become obsolete specifications.

Other Working Drafts


JSON-LD 1.1 Processing Algorithms and API

This specification defines a set of algorithms for programmatic transformations of JSON-LD documents. Restructuring data according to the defined transformations often dramatically simplifies its usage. Furthermore, this document proposes an Application Programming Interface (API) for developers implementing the specified algorithms.


JSON-LD 1.1 Framing

JSON-LD Framing allows developers to query by example and force a specific tree layout to a JSON-LD document.



JSON is a useful data serialization and messaging format. This specification defines JSON-LD, a JSON-based format to serialize Linked Data. The syntax is designed to easily integrate into deployed systems that already use JSON, and provides a smooth upgrade path from JSON to JSON-LD. It is primarily intended to be a way to use Linked Data in Web-based programming environments, to build interoperable Web services, and to store Linked Data in JSON-based storage engines.


Terms for describing people

This document defines a set of terms for describing people. It defines how to describe people's characteristics such as names or addresses and how to relate people to other things, for example to organizations or projects. For each term, guidance on the usage within a running example is provided. This document also defines mappings to widely used vocabularies to enable interoperability.