Last refreshed: 2026-07-06
Source: Monetary Amounts 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.
Purpose
Monetary amounts are value/currency structures used to describe an amount of money in a particular modeling context. They are similar to dimensions, but the unit is a `Currency`.
In the Linked Art API and model, monetary amounts are mainly used inside Provenance Activity structures, especially payments, but they can also appear as `dimension` values on sets such as auction lots.
Required Shape
A monetary amount structure includes:
- `type`: required. Must be `MonetaryAmount`.
- `value`: required numeric value.
- `currency`: required `Currency` reference.
- `id`: optional URI identifying the amount.
- `_complete`: optional completeness signal. If an `id` URI has richer dereferenceable information, `_complete: false` must be present.
Recommended Fields
- `_label`: developer-facing label.
- `classified_as`: classifications following the `Type` structure, such as starting price.
- `identified_by`: textual display form of the structured amount, following the `Name` pattern.
Optional Fields
- `upper_value_limit`: highest possible value for the amount.
- `lower_value_limit`: lowest possible value for the amount.
- `referred_to_by`: references to textual works about the amount, or embedded statements about the amount.
Common Incoming Relationships
- `paid_amount`: used by `Payment` parts in Provenance Activity records to record money changing hands.
- `dimension`: used on sets and other entities when a monetary amount describes the entity, such as an auction lot starting price.
Meta Museum Notes
Meta Museum already preserves provenance payment structures and auction lot/set evidence as Linked Art JSON-LD. Monetary amounts should stay structured as `MonetaryAmount` with `value`, `currency`, display `identified_by`, notes, and classifications; UI code should not collapse them into formatted strings because currency URI, notation, and uncertainty bounds are reusable data.
Test Ideas
- Preserve `MonetaryAmount.value`, `currency`, and `classified_as` on payment and auction lot fixtures.
- Preserve `Currency` references with `id`, `type: Currency`, `_label`, and `notation`.
- Preserve `identified_by` display text without replacing structured value/currency data.
- Preserve `upper_value_limit` and `lower_value_limit` for uncertain amounts.
- Preserve `referred_to_by` notes attached to monetary amounts.
- Add a dereferenceable amount `id` with richer detail available and verify `_complete: false`.