JSON-LD

Protocolo Semántico y de Datos

A W3C-standardized JSON-based format for serializing Linked Data, allowing existing JSON to be interpreted as RDF with minimal changes. JSON-LD provides a meaning layer on top of plain JSON by using a @context to map JSON keys to IRIs (Internationalized Resource Identifiers), enabling machine-readable interoperability across systems without requiring shared implementation. Widely used as the default serialization for W3C Verifiable Credentials, ActivityPub, schema.org embeddings, and other decentralized-data ecosystems .

Comunidad
Enlaces
Visitar Comunidad

Detalles

Licencia N/A — specification document; many open-source implementations exist (jsonld.js, jsonld.py, ruby-rdf, jsonld-java, titanium-json-ld, and others) under various permissive licenses
Estado de Desarrollo 🏁 Final
Detalle del Estado de Desarrollo Released (JSON-LD 1.1 is a stable W3C Recommendation since July 16, 2020; widely deployed across the W3C Verifiable Credentials, Activity Streams 2.0, schema.org, and Linked Data ecosystems)
Propietario W3C JSON-LD Working Group (specification editors include Gregg Kellogg, Pierre-Antoine Champin, and Dave Longley); the underlying ideas originated in the JSON-LD Community Group
Órgano de Gobierno W3C (Recommendation track — JSON-LD Working Group; originated in the JSON-LD Community Group)
País International (W3C is a global standards body; editors and contributors distributed across multiple countries and organizations)
Año de Inicio 2010
Stack N/A — specification, not implementation
Financiamiento W3C (open standards body funded by member organizations and grants)
Última Investigación 1 jul 2026

Dominios de Caso de Uso

Co-creación y Conocimiento

Protocolo Semántico y de Datos Atributos

Orígenes Semantic Web / Linked Data (designed to bridge plain-JSON developer ergonomics with RDF / Linked Data interoperability; explicit goal: enable JSON developers to participate in the Semantic Web without leaving JSON)
Base de Datos N/A — JSON-LD is a data format, not a database
Lenguaje de Consulta JSON-LD documents can be queried with SPARQL after being interpreted as RDF; framing (a JSON-LD 1.1 capability) provides a query-by-example mechanism for shaping output documents
Formatos de Datos JSON-LD (the format itself); can be losslessly converted to and from N-Quads, Turtle, RDF/XML, and other RDF serializations; JSON-LD 1.1 specifies expansion, compaction, flattening, and framing transformations
Edición Colaborativa en Vivo N/A
Edición de Texto Enriquecido N/A
Soporte Móvil N/A — data format; works in any environment that supports JSON
Soporte Web Yes — JSON-LD is widely consumed in browsers; schema.org JSON-LD embedded in HTML pages is the most common form of structured data on the web
Aplicaciones Nativas N/A — data format works in any runtime; processor libraries exist for all major languages
Términos Free open standard (no licensing fees; W3C standards are royalty-free under the W3C Patent Policy)
Fondos N/A — open standard, no funding round
Basado En JSON (RFC 8259 — the underlying serialization syntax); RDF (the data model JSON-LD serializes); IRIs (RFC 3987 — used as global identifiers in @context mappings); W3C Patent Policy (royalty-free licensing framework)
Compatibilidad con la Web Semántica Full RDF compliance (JSON-LD is one of the official RDF 1.1 serialization formats; documents can be interpreted as RDF graphs and queried with SPARQL; the JSON-LD 1.1 API specifies the algorithms for this transformation)
Madurez del Protocolo / Estandarización W3C Standard (JSON-LD 1.1 published as W3C Recommendation on 16 July 2020; the family includes JSON-LD 1.1 Syntax, JSON-LD 1.1 Processing Algorithms and API, and JSON-LD 1.1 Framing — all Recommendations)
Tipo de Vocabulario / Ontología General-purpose (JSON-LD is domain-agnostic; the same format is used for credentials, social media, knowledge graphs, structured data on the web, IoT, and many other domains)
Patrón de Uso Embedded in other protocols (JSON-LD is rarely a standalone protocol; it serves as the data format beneath higher-level specifications including W3C Verifiable Credentials, ActivityPub, schema.org, Solid, and many others; @context mechanism allows it to carry domain-specific vocabularies)