MetaMuseum
Menu
← Documentation home

Canonical Markdown source · Jul 6, 2026

Linked Art API: Events

linked-art/api/events.md · 70 lines · SHA-256 cdb00a835694

Last refreshed: 2026-07-06

Source: Events 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 Event endpoint describes standalone periods, events, and activities that are noteworthy but are not directly embedded in another entity endpoint, are not provenance activities, and are not exhibitions. Examples include named periods, fires or other events that caused destruction, research projects, and auction or other activities related to works of art.

Linked Art groups `Period`, `Event`, and `Activity` into this one endpoint because they share many properties in API use.

Required Shape

An Event endpoint 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 event.
  • `type`: one of `Period`, `Event`, or `Activity`.
  • `_label`: developer-facing label.
  • `classified_as`: classifications following the `Type` structure.
  • `identified_by`: `Name` and/or `Identifier` structures.
  • `timespan`: `TimeSpan` structure recording when the event occurred.

Optional Shared Fields

  • `referred_to_by`: human-readable statements.
  • `equivalent`: external identities.
  • `representation`: visual works representing the event.
  • `member_of`: sets that include the event.
  • `subject_of`: textual works focused on the event.
  • `attributed_by`: relationship assignment evidence.
  • `part_of`: broader event that directly contains this event.
  • `during`: broader period during which this event occurred.
  • `before`: period, event, or activity after this event in relative order.
  • `after`: period, event, or activity before this event in relative order.
  • `took_place_at`: places where the event occurred.

Type-Specific Fields

Only `Event` and `Activity` use:

  • `caused_by`: event that caused this event or activity.
  • `participant`: people or groups that participated but did not carry it out.

Only `Activity` uses:

  • `influenced_by`: entity that influenced the activity.
  • `carried_out_by`: person or group responsible for carrying out the activity.
  • `used_specific_object`: entity instrumental in carrying out the activity.
  • `technique`: technique used in the activity, modeled as `Type`.

Common Incoming Relationships

  • `part_of` from events or activities in any endpoint. This implies the broader event's spatial and temporal constraints also apply to the referencing event or activity.

Meta Museum Notes

Meta Museum already exposes `/api/events/{id}` as a canonical role route for `Period`, `Event`, and `Activity`. Existing record and role-route tests preserve names, timespans, places, actor responsibility, `caused_by`, `part_of`, `during`, `before`, and `after`. Activity-stream projections also preserve standalone semantic event relationships when they appear on stored records.

Test Ideas

  • Keep `/api/events/{id}` role coverage aligned with exactly `Period`, `Event`, and `Activity`.
  • Preserve an `Activity` fixture with `carried_out_by`, `used_specific_object`, `technique`, `took_place_at`, `subject_of`, and `timespan`.
  • Preserve an `Event` fixture with `caused_by`, `participant`, and `part_of`.
  • Preserve a `Period` fixture with `timespan`, `during`, `before`, and `after`, while avoiding `carried_out_by` on pure periods.