{"id":"linked-art/api/shared-concept-references","relativePath":"linked-art/api/shared-concept-references.md","title":"Linked Art API: Shared Concept References","markdown":"# Linked Art API: Shared Concept References\n\n**Last refreshed:** 2026-07-06\n\nSource: [Types / Concepts shared structure](https://linked.art/api/1.0/shared/type/), part of Linked Art API 1.0, published under [CC BY 4.0](http://creativecommons.org/licenses/by/4.0/). This is a project summary; the upstream page is authoritative.\n\n## Purpose\n\nConcept references, usually called Types in Linked Art, connect resource descriptions to controlled vocabularies such as the Getty Art and Architecture Thesaurus. They are used throughout the model for classification, language, material, currency, measurement units, techniques, subjects, and assignment values.\n\nFor full concept records, use the [Concepts endpoint](concepts.md). This shared structure is the compact embedded reference form used inside other records.\n\n## Required Shape\n\nA concept reference includes:\n\n- `id`: required URI identifying the concept.\n- `type`: required. Must be one of `Type`, `Currency`, `Language`, `Material`, or `MeasurementUnit`.\n\n## Recommended Fields\n\n- `_label`: developer-facing label.\n\n## Optional Fields\n\n- `equivalent`: references to equivalent external resources.\n- `notation`: commonly used notation or identifier strings, especially language tags on `Language`.\n- `classified_as`: meta-classifications for the concept, following the same `Type` requirements.\n\n## Concept Classes\n\n- `Type`: generic concept for classifications, techniques, styles, genres, subjects, and meta-types.\n- `Language`: human-spoken language, such as Spanish.\n- `Material`: material that makes up a physical thing, such as gold.\n- `Currency`: currency used by a monetary amount, such as the Euro.\n- `MeasurementUnit`: unit used by a dimension, such as inches.\n\n## Common Incoming Relationships\n\n- `classified_as`: almost every entity can be classified by a `Type`.\n- `technique`: activities can have techniques modeled as `Type`.\n- `influenced_by`: activities can be motivated by a `Type`.\n- `about`: textual and visual works can have conceptual subjects.\n- `assigned`: attribute assignments can assign a classification.\n- `language`: linguistic content uses `Language`.\n- `currency`: monetary amounts use `Currency`.\n- `unit`: dimensions use `MeasurementUnit`.\n- `made_of`: physical objects use `Material`.\n\n## Meta Museum Notes\n\nMeta Museum already preserves compact concept references and full concept records. Existing coverage proves `Type`, `Material`, `Language`, `Currency`, and `MeasurementUnit` remain valid concept classes; records preserve `classified_as`, `language`, `unit`, `equivalent`, `notation`, `broader`, and concept-scheme membership without flattening controlled vocabulary references into plain strings. The important project rule is to preserve meta-classification, such as a painting Type classified as Type of Work.\n\n## Test Ideas\n\n- Preserve all allowed concept reference classes: `Type`, `Currency`, `Language`, `Material`, and `MeasurementUnit`.\n- Preserve `classified_as` meta-types on concepts, such as painting classified as Type of Work.\n- Preserve `notation` for language tags.\n- Preserve concept references in `classified_as`, `technique`, `influenced_by`, `about`, `assigned`, `language`, `currency`, `unit`, and `made_of`.\n- Preserve `equivalent[]` for external vocabulary reconciliation without treating labels as stable identifiers.\n","sections":[{"level":2,"heading":"Purpose","anchor":"purpose"},{"level":2,"heading":"Required Shape","anchor":"required-shape"},{"level":2,"heading":"Recommended Fields","anchor":"recommended-fields"},{"level":2,"heading":"Optional Fields","anchor":"optional-fields"},{"level":2,"heading":"Concept Classes","anchor":"concept-classes"},{"level":2,"heading":"Common Incoming Relationships","anchor":"common-incoming-relationships"},{"level":2,"heading":"Meta Museum Notes","anchor":"meta-museum-notes"},{"level":2,"heading":"Test Ideas","anchor":"test-ideas"}],"html":"

Linked Art API: Shared Concept References

\n

Last refreshed: 2026-07-06

\n

Source: Types / Concepts shared structure, part of Linked Art API 1.0, published under CC BY 4.0. This is a project summary; the upstream page is authoritative.

\n

Purpose

\n

Concept references, usually called Types in Linked Art, connect resource descriptions to controlled vocabularies such as the Getty Art and Architecture Thesaurus. They are used throughout the model for classification, language, material, currency, measurement units, techniques, subjects, and assignment values.

\n

For full concept records, use the Concepts endpoint(concepts.md). This shared structure is the compact embedded reference form used inside other records.

\n

Required Shape

\n

A concept reference includes:

\n\n

Recommended Fields

\n\n

Optional Fields

\n\n

Concept Classes

\n\n

Common Incoming Relationships

\n\n

Meta Museum Notes

\n

Meta Museum already preserves compact concept references and full concept records. Existing coverage proves `Type`, `Material`, `Language`, `Currency`, and `MeasurementUnit` remain valid concept classes; records preserve `classified_as`, `language`, `unit`, `equivalent`, `notation`, `broader`, and concept-scheme membership without flattening controlled vocabulary references into plain strings. The important project rule is to preserve meta-classification, such as a painting Type classified as Type of Work.

\n

Test Ideas

\n","updatedAt":"2026-07-06T00:00:00.000Z","checksum":"d1d6465ac086ba4afaade5b1de6946e49349cc9426cf81fd779e8ec16a27f7e8","checksumPrefix":"d1d6465ac086","anchorCount":8,"lineCount":61,"rawUrl":"/api/docs/content?path=linked-art%2Fapi%2Fshared-concept-references.md","htmlUrl":"/docs?doc=linked-art%2Fapi%2Fshared-concept-references.md","apiUrl":"/api/docs/content?path=linked-art%2Fapi%2Fshared-concept-references.md"}