Linked Art API: Abstract Works

Last refreshed: 2026-07-06

Source: Abstract Works endpoint, part of Linked Art API 1.0, published under CC BY 4.0. This is a project summary; the upstream page is authoritative.

Purpose

The Abstract Work endpoint describes conceptual works that are not best modeled as physical things, digital files, textual works, or visual works. Examples include an exhibition idea, a performance concept, or a general abstract work that can be instantiated by activities.

Required Shape

An Abstract Work record dereferences to one JSON-LD object:

• `@context`: Linked Art context URI, or an array ending with that URI for extensions.
• `id`: dereferenceable HTTP(S) URI for the work.
• `type`: `PropositionalObject`.

Recommended Fields

• `_label`: developer-facing label.
• `classified_as`: classifications following the `Type` structure.
• `identified_by`: `Name` and/or `Identifier` structures.

Optional Fields

• `referred_to_by`: human-readable statements.
• `equivalent`: external identities.
• `subject_of`: textual works focused on this abstract work.
• `representation`: visual works representing it.
• `member_of`: sets that include it.
• `attributed_by`: relationship assignment evidence.
• `dimension`: abstract dimensions.
• `conceptually_part_of`: broader abstract works.
• `about`: primary subjects of the work.
• `subject_to`: rights over the intellectual work.
• `created_by`: `Creation` event for the abstract work.

Common Incoming Relationships

• `about` from Textual Work records.
• `influenced_by` from Activity records, including exhibitions.

Meta Museum Notes

Current record storage can preserve a `PropositionalObject` record through `/api/records/{id}` because record detail responses keep arbitrary Linked Art JSON-LD structure. We do not yet expose a dedicated `/api/abstract-works/{id}` canonical role route. If this endpoint becomes a public contract, add route coverage and role-specific tests rather than treating all abstract works as textual works.

Test Ideas

• A `PropositionalObject` fixture with `about`, `created_by`, `member_of`, `subject_to`, and `conceptually_part_of` survives record dereference unchanged.
• A future role route rejects `LinguisticObject` or `VisualItem` when an Abstract Work endpoint expects `PropositionalObject`.
• Activity projections preserve `influenced_by` references to abstract works without flattening them into plain labels.