MetaMuseum
Menu
← Documentation home

Canonical Markdown source · Jul 6, 2026

Linked Art API: Places

linked-art/api/places.md · 55 lines · SHA-256 5b00bba40010

Last refreshed: 2026-07-06

Source: Places 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 Place endpoint describes spatial extents that provide context for activities and locations. A `Place` is independent of time and independent of which objects happen to be present there. Linked Art models place geometry with WKT in `defined_by`.

Required Shape

A Place 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 place.
  • `type`: `Place`.
  • `_label`: developer-facing label.
  • `classified_as`: classifications following the `Type` structure, such as city, nation, gallery, or room.
  • `identified_by`: `Name` and/or `Identifier` structures.

Optional Fields

  • `referred_to_by`: statements about the place.
  • `equivalent`: external identities.
  • `representation`: visual works representing the place.
  • `member_of`: sets that include the place.
  • `subject_of`: textual works focused on the place.
  • `attributed_by`: relationship assignment evidence.
  • `part_of`: broader place within which this place falls.
  • `defined_by`: WKT geometry string for the place.

Common Incoming Relationships

  • `took_place_at` from events and activities.
  • `current_location` from physical object records.
  • `current_permanent_location` from physical object records.
  • `moved_from` and `moved_to` from provenance `Move` activities.
  • `residence` from person and group records.

Meta Museum Notes

Meta Museum already exposes places through `/api/places/{id}` and preserves full `Place` records through `/api/records/{id}`. Existing place coverage proves classifications, names, descriptions, `part_of` hierarchy, external `equivalent[]`, WKT `defined_by`, approximate place nesting, and `HumanMadeObject.current_location -> Place` references. The project also keeps buildings and other immovable human-made things as `HumanMadeObject` records rather than coercing them into `Place`.

Test Ideas

  • Keep `/api/places/{id}` role coverage aligned with `Place`.
  • Preserve a `Place` fixture with `classified_as`, `identified_by`, `referred_to_by`, `equivalent`, `part_of`, `member_of`, and `defined_by`.
  • Preserve incoming `current_location` and `produced_by.took_place_at` references from physical objects.
  • Preserve `moved_from` and `moved_to` place references in provenance movement activities.
  • Continue separating geographic places from buildings or immovable objects modeled as `HumanMadeObject`.