Linked Art API: Type Structure


Concepts, called Types, are a core part of the model and present in practically every resource description. They give access to external vocabularies, such as the Getty's Art and Architecture Thesaurus, in order to add classifications to entities described. As they are external entities, rather than the focus of the Linked Art documentation, they are only slightly more detailed than any other entity reference, allowing an additional meta-classification to be asserted about the Type.

The Type pattern is also used for more specific concept types:

Types are described in the base patterns of the model documentation, and examples are present for practically every class.

For full records that describe a Type, please see the Concept Endpoint documentation.

Property Definitions

Properties of Types

Property Name Datatype Requirement Description
id string Required The value MUST be a URI identifying the concept
type string Required The class of the concept, which MUST be one of the following values: "Type", "Currency", "Language", "Material", or "MeasurementUnit"
_label string Recommended A human readable label for the concept, intended for developers
classified_as array Recommended An array of json objects, each of which is a further classification of the concept and MUST follow these requirements for Type

Property Diagram


Incoming Properties

Types and other instances of concepts are typically found as the object of the following properties. This list is not exhaustive, but is intended to cover the likely cases.

Property Name Source Class Description
classified_as All Almost every entity can be classified as a Type
technique Activity Activities (of all sorts) can have a technique, which is modeled as a Type
motivated_by Activity Activities can also be motivated by a Type
about LinguisticObject, VisualItem Textual and Visual Works can have subjects, which are modeled as Types
assigned AttributeAssignment The classification of an object might be assigned as part of a documented Attribute Assignment
language LinguisticObject The language of linguistic content is modeled as a Language
currency MonetaryAmount The currency of a MonetaryAmount is modeled as a Currency
unit Dimension The unit of a Dimension is modeled as a MeasurementUnit
made_of Material The materials of a HumanMadeObject are modeled as Materials


A painting is classified as a painting, which is in turn classified as a type of work.

  "@context": "",
  "id": "",
  "type": "HumanMadeObject",
  "classified_as": [
      "id": "",
      "type": "Type",
      "_label": "Painting",
      "classified_as": [
          "id": "",
          "type": "Type",
          "_label": "Type of Work"

graph TD classDef object stroke:black,fill:#E1BA9C,rx:20px,ry:20px; classDef actor stroke:black,fill:#FFBDCA,rx:20px,ry:20px; classDef type stroke:red,fill:#FAB565,rx:20px,ry:20px; classDef name stroke:orange,fill:#FEF3BA,rx:20px,ry:20px; classDef dims stroke:black,fill:#c6c6c6,rx:20px,ry:20px; classDef infoobj stroke:#907010,fill:#fffa40,rx:20px,ry:20px classDef timespan stroke:blue,fill:#ddfffe,rx:20px,ry:20px classDef place stroke:#3a7a3a,fill:#aff090,rx:20px,ry:20px classDef event stroke:#1010FF,fill:#96e0f6,rx:20px,ry:20px classDef literal stroke:black,fill:#f0f0e0; classDef classstyle stroke:black,fill:white; O1(object/12) class O1 object; O1-- type -->O1_0[HumanMadeObject] class O1_0 classstyle; O2(aat:300033618) class O2 type; O2-- type -->O2_0[Type] class O2_0 classstyle; O2-- _label -->O2_3("''Painting''") class O2_3 literal; O3(aat:300435443) class O3 type; O3-- type -->O3_0[Type] class O3_0 classstyle; O3-- _label -->O3_3("''Type of Work''") class O3_3 literal; O2-- classified_as -->O3 O1-- classified_as -->O2
Other Representations: JSON-LD (raw) | JSON-LD (playground) | Turtle (raw) | Turtle (styled)