JSON-LD Serialization

Table of Contents


JSON-LD is a Linked Open Data serialization using the popular JSON (Javascript Object Notation) format that is convenient for both backend and browser based development. It is specified by the W3C as an official serialization. Continued development work happens in the JSON for Linking Data W3C Community Group.

The serialization for JSON-LD is friendly to developers through the use of context documents that specify the mapping between the key used in the json object and the RDF predicate used in the model. This abstraction allows the developer to work with existing patterns and frameworks, while the data is still managed as a graph underneath. This document describes the context used for CIDOC-CRM and other ontologies.

The context that provides the mapping of the terms used in the model is published as:


Media Type

The media type to use for representations in JSON-LD using the context is:


This would be the value of the Content-Type HTTP header on responses, and if there are other representations available via content negotiation, then it can be sent in requests in the Accept header,


The examples throughout the documentation use the JSON-LD serialization. Each has a link to the raw JSON-LD, and to load it into the invaluable JSON-LD playground where you can explore the details. Instead of trying to describe all of the predicates and classes (for that just read the CIDOC-CRM specification), we present the models for the known use cases in an attempt to be more practical and results oriented. We strive for usability and familiarity for developers, and the examples aim to present best practices at the same time as being easy to follow.

An example of the JSON-LD serialization for a painting, that is made of watercolor on a canvas support:

  "@context": "https://linked.art/ns/v1/linked-art.json", 
  "id": "https://linked.art/example/object/32", 
  "type": "ManMadeObject", 
  "label": "Example Painting", 
  "classified_as": [
    {"id": "aat:300033618","type": "Type","label": "Painting"}, 
    {"id": "aat:300133025","type": "Type","label": "Artwork"}
  "made_of": [
    {"id": "aat:300015045","type": "Material","label": "watercolors"}
  "part": [
      "id": "https://linked.art/example/object/32/part/1", 
      "type": "ManMadeObject", 
      "label": "Canvas Support", 
      "classified_as": [
        {"id": "aat:300014844","type": "Type","label": "Support"}
      "made_of": [{"id": "aat:300014078","type": "Material","label": "canvas"}]

JSON-LD (Raw) | JSON-LD (Playground) | Turtle (Raw) | Turtle (Styled)

Context Design

The important part of the JSON-LD serialization is the shared context document. This context has some design constraints that it is useful to understand before looking at the data model and mapping from the ontology. In particular:

There are some challenges overlaid on these principles from the CIDOC-CRM ontology.

The context tries to manage all of these issues in a practical and programmatically accesible way from the ontology definition.


The following process is used to create the JSON-LD keys from the CIDOC-CRM ontology:

The context implements the notion that if a property can ever have multiple values, then it must always be an array. In JSON-LD this is done with @container: @set on such properties, and you'll see many instances of this in the examples where a property has an array with a single object inside it.

The context is designed for JSON-LD 1.1, and uses the feature known as scoped contexts: sub-contexts that are defined per class or per relationship that apply only within that term. This is used to map all of the the various partitioning relationships to part and part_of, regardless of the type of resource being partitioned. This feature makes the JSON much easier to read and write, without losing the semantic precision of the separate underlying terms.

Name collisions and naming inconsistencies in the ontology have been resolved as follows:

Property Key
P2 classified_as
P5 subState
P5i subState_of
P7i location_of
P9 part
P9i part_of
P12 involved
P14i carried_out
P20i specific_purpose_of
P28 transferred_custody_from
P29 transferred_custody_to
P29i acquired_custody_through
P32 technique
P33 specific_technique
P35i condition_identified_by
P37 assigned_identifier
P37i identifier_assigned_by
P42 assigned_type
P42i type_assigned_by
P45 made_of
P46 part
P46i part_of
P56 bears
P65 shows
P78 time_identified_by
P78i identifies_time
P86 part_of
P86i part
P87 place_identified_by
P87i identifies_place
P89 part_of
P89i part
P90 has_value
P101 general_use
P106 part
P106i part_of
P107 member
P107i member_of
P127 part_of
P127i part
P131 actor_identified_by
P131i identifies_actor
P132 volume_overlaps_with
P133 distinct_from
P135i type_created_by
P139 alternative
P140 assigned_to
P149 concept_identified_by
P149i identifies_concept
P151i participated_in_formation
P164i timespan_of_presence
P165i incorporated_by
skos:exactMatch exact_match
sci:O13i_is_triggered_by caused_by
sci:O13_triggers caused
ore:isAggregatedBy aggregated_by
rdfs:seeAlso see_also
dcterms:relation related
dcterms:conformsTo conforms_to
skos:closeMatch close_match
schema:genre style