JSON-LD

File format for encoding linked data

JSON-LDFilename extension|

.jsonld

|

Internet media type|

application/ld+json

Type of format| Semantic Web
Container for| Linked Data
Extended from| JSON
Standard| JSON-LD 1.1 / JSON-LD 1.1 API
Open format?| Yes

JSON-LD 1.1Abbreviation| JSON-LD

|

Status| W3C Recommendation
Year started| 2010
Editors|

Editors

*     * Gregg Kellogg
* Pierre-Antoine Champin
* Dave Longley

Previous editors

*     * Manu Sporny
* Markus Lanthaler

Authors| Manu Sporny, Dave Longley, Gregg Kellogg, Markus Lanthaler, Niklas Lindström
Base standards|

* BCP 47
* JSON
* RDF
* URI scheme
* Internationalized Resource Identifier
* Unicode Bidirectional Algorithm

Domain| Semantic Web, Data Serialization
Website|

* json-ld.org
* JSON-LD 1.1
* JSON-LD 1.1 Processing Algorithms and API
* JSON-LD 1.1 Framing

JSON-LD (JavaScript Object Notation for Linked Data) is a method of encoding linked data using JSON. One goal for JSON-LD was to require as little effort as possible from developers to transform their existing JSON to JSON-LD.[1] JSON-LD allows data to be serialized in a way that is similar to traditional JSON.[2] It was initially developed by the JSON for Linking Data Community Group[3] before being transferred to the RDF Working Group[4] for review, improvement, and standardization,[5] and is currently maintained by the JSON-LD Working Group.[6] JSON-LD is a World Wide Web Consortium Recommendation.

## Design

[edit]

JSON-LD is designed around the concept of a "context" to provide additional mappings from JSON to an RDF model. The context links object properties in a JSON document to concepts in an ontology. In order to map the JSON-LD syntax to RDF, JSON-LD allows values to be coerced to a specified type or to be tagged with a language. A context can be embedded directly in a JSON-LD document or put into a separate file and referenced from different documents (from traditional JSON documents via an HTTP Link header).

## Example

[edit]

"@context": {
"name": "http://xmlns.com/foaf/0.1/name",
"homepage": {
"@id": "http://xmlns.com/foaf/0.1/workplaceHomepage",
"@type": "@id"

"Person": "http://xmlns.com/foaf/0.1/Person"

"@id": "https://me.example.com",
"@type": "Person",
"name": "John Smith",
"homepage": "https://www.example.com/"

The example above describes a person, based on the FOAF (friend of a friend) ontology. First, the two JSON properties `name` and `homepage` and the type `Person` are mapped to concepts in the FOAF vocabulary and the value of the `homepage` property is specified to be of the type `@id`. In other words, the homepage id is specified to be an IRI in the context definition. Based on the RDF model, this allows the person described in the document to be unambiguously identified by an IRI. The use of resolvable IRIs allows RDF documents containing more information to be transcluded which enables clients to discover new data by simply following those links; this principle is known as 'Follow Your Nose'.[7]

By having all data semantically annotated as in the example, an RDF processor can identify that the document contains information about a person (`@type`) and if the processor understands the FOAF vocabulary it can determine which properties specify the person's name and homepage.

## Use

[edit]

The encoding is used by Schema.org,[8] Google Knowledge Graph,[9][10] and used mostly for search engine optimization activities. It has also been used for applications such as biomedical informatics,[11] and representing provenance information.[12] It is also the basis of Activity Streams, a format for "the exchange of information about potential and completed activities",[13] and is used in ActivityPub, the federated social networking protocol.[14] Additionally, it is used in the context of Internet of Things (IoT), where a Thing Description,[15] which is a JSON-LD document, describes the network facing interfaces of IoT devices.

## See also

[edit]

* Hypertext Application Language

## References

[edit]

1. ^ "JSON-LD Syntax 1.1". 2010-07-16. Retrieved 2020-12-10.
2. ^ "On Using JSON-LD to Create Evolvable RESTful Services"., M. Lanthaler and C. Gütl in Proceedings of the 3rd International Workshop on RESTful Design (WS-REST 2012) at WWW2012.
3. ^ "JSON for Linking Data Community Group". json-ld.org.
4. ^ "RDF Working Group". w3.org.
5. ^ "JSON-LD 1.0, A JSON-based Serialization for Linked Data, W3C Recommendation 16 January 2014". 2014-01-16. Retrieved 2020-12-10.
6. ^ "JSON-LD Working Group". w3.org.
7. ^ "Linked Data Patterns, Chapter 5: Follow Your Nose". 2023-06-07. Retrieved 2023-06-07.
8. ^ "Data Model". Schema.org. Retrieved 2018-06-20.
9. ^ "Understanding structured data". Bendev Junior. 14 June 2022.
10. ^ "Method Entities in Search". Google Developers. Retrieved 2017-10-17.
11. ^ Xin, Jiwen; Afrasiabi, Cyrus; Lelong, Sebastien; Adesara, Julee; Tsueng, Ginger; Su, Andrew I.; Wu, Chunlei (2018-02-01). "Cross-linking BioThings APIs through JSON-LD to facilitate knowledge exploration". BMC Bioinformatics. 19 (1): 30. doi:10.1186/s12859-018-2041-5. PMC 5796402. PMID 29390967.
12. ^ Huynh, Trung Dong; Michaelides, Danius T.; Moreau, Luc (2016). "PROV-JSONLD: A JSON and linked data representation for provenance" (PDF). In Mattoso, Marta; Glavic, Boris (eds.). Provenance and annotation of data and processes: 6th International Provenance and Annotation Workshop, IPAW 2016, McLean, VA, USA, June 7-8, 2016, Proceedings. Lecture Notes in Computer Science. Vol. 9672\. Cham: Springer International Publishing. pp. 173–177\. doi:10.1007/978-3-319-40593-3_15. ISBN 978-3-319-40592-6. S2CID 44036472.
13. ^ Prodromou, Evan (May 2017). "Activity Streams 2.0". W3C Recommendation - via W3C.
14. ^ Tallon, Jessica (Jan 2018). "ActivityPub". W3C Recommendation - via W3C.
15. ^ "Web of Things (WoT) Thing Description, W3C Proposed Recommendation". www.w3.org. Retrieved 2020-03-26.

## External links

[edit]

* JSON-LD.org

* v
* t
* e

Semantic Web

Background|

* Databases
* Hypertext
* Internet
* Ontologies
* Semantics
* Semantic networks
* World Wide Web

Sub-topics|

* Dataspaces
* Hyperdata
* Linked data
* Rule-based systems

Applications|

* Semantic analytics
* Semantic computing
* Semantic mapper
* Semantic matching
* Semantic publishing
* Semantic reasoner
* Semantic search
* Semantic service-oriented architecture
* Semantic wiki
* Solid

Related topics|

* Collective intelligence
* Description logic
* Folksonomy
* Geotagging
* Information architecture
* iXBRL
* Knowledge extraction
* Knowledge management
* Knowledge representation and reasoning
* Library 2.0
* Digital library
* Digital humanities
* Metadata
* References
* Topic map
* Web 2.0
* Web engineering
* Web Science Trust

Standards|

| Syntax and supporting technologies|

* HTTP
* IRI
* URI
* RDF
* triples
* RDF/XML
* JSON-LD
* Turtle
* TriG
* Notation3
* N-Triples
* TriX (no W3C standard)
* RRID
* SPARQL
* XML
* Semantic HTML

|

Schemas, ontologies and rules|

* Common Logic
* OWL
* RDFS
* Rule Interchange Format
* Semantic Web Rule Language
* SHACL

Semantic annotation|

* COinS
* GRDDL
* Microdata
* Microformats
* RDFa
* SAWSDL
* Facebook Platform

Common vocabularies|

* BIBFRAME
* BIBO
* DOAP
* Dublin Core
* FOAF
* Schema.org
* SIOC
* SKOS

Microformat vocabularies|

* hAtom
* hCalendar
* hCard
* hProduct
* hRecipe
* hReview

* v
* t
* e

Document markup languages

Office suite|

* Compound Document Format
* OOXML
* SpreadsheetML
* PresentationML
* WordprocessingML
* ODF
* UOF

Well-known|

* HTML
* XHTML
* MathML
* RTF
* TeX
* LaTeX
* Markdown

Lesser-known|

* AmigaGuide
* AsciiDoc
* BBCode
* CML
* C-HTML
* ConTeXt
* CrossMark
* DITA
* DocBook
* EAD
* Enriched text
* FHTML
* GML
* GuideML
* HDML
* HyTime
* IPF
* LilyPond
* LinuxDoc
* Lout
* MIF
* MAML
* MEI
* MusicXML
* OMDoc
* OpenMath
* Org-mode
* POD
* ReStructuredText
* RTML
* RFT
* S1000D
* Setext
* TEI
* Texinfo
* troff
* Wikitext
* WML
* WapTV
* XAML

List of document markup languages

* v
* t
* e

World Wide Web Consortium (W3C)

Products and
standards|

| Recommendations|

* ActivityPub
* Activity Streams
* ARIA
* Canonical XML
* CDF
* CSS
* Animations
* Flexbox
* Grid
* DOM
* EXI
* EmotionML
* Geolocation API
* HTML
* HTML5
* IndexedDB
* ITS
* JSON-LD
* Linked Data Notifications
* MathML
* Micropub
* OWL
* PLS
* RDF
* Schema
* RDFa
* SISR
* SKOS
* SMIL
* SOAP
* SRGS
* SRI
* SSML
* SVG
* Filter Effects
* SCXML
* SHACL
* SPARQL
* Timed text
* VoiceXML
* WebAssembly
* WoT
* TD
* Web storage
* WSDL
* Webmention
* WebSub
* WebVTT
* WOFF
* XHTML
* +RDFa
* XML
* Base
* Encryption
* Events
* Information Set
* Namespace
* Schema
* Signature
* XForms
* XInclude
* XLink
* XOP
* XPath
* 2.0
* 3.x
* XPointer
* XProc
* XQuery
* XSL
* XSL-FO
* XSLT
* elements

|

Notes|

* IndieAuth
* XAdES
* XBL
* XHTML+SMIL
* XUP

Working drafts|

* CCXML
* CURIE
* EME
* InkML
* MSE
* RIF
* SMIL Timesheets
* sXBL
* WebGPU
* WebXR
* XFDL
* XFrames
* XMLHttpRequest

Guidelines|

* Web Content Accessibility Guidelines

Initiative|

* Markup Validation Service
* Web Accessibility Initiative
* Web Components

Deprecated|

* C-HTML
* HDML
* JSSS
* PGML
* VML
* WebPlatform

Obsoleted|

* P3P
* XHTML+MathML+SVG

Organizations|

* WHATWG
* Defunct: World Wide Web Foundation

Elected groups|

* AB
* Board
* TAG

Working groups|

* CSS
* SVG
* WebAssembly
* WebAuthn

Community & business groups|

* Web Advertising BG
* WebAssembly CG

Closed groups|

* Device Description (DDWG)
* HTML
* Multimodal Interaction Activity (MMI)

Software|

* CERN httpd
* Libwww

Browsers|

* Line Mode (1990–)
* Arena (1993–98)
* Agora (1994–97)
* Argo (1994–97)
* Amaya (browser/editor, 1996–2012)

Conferences|

* International World Wide Web Conference (IW3C)
* Steering Committee (IW3C2)
* First conference ("WWW1", 1994)

*[JSON]: JavaScript Object Notation
*[RDF]: Resource Description Framework
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template