On this page Asset Responsibilities

Assets & Media

Audio, video, image, scan, and PDF media asset references.

Media files should be linked, not embedded. OLS supports audio, video, images, scans, PDFs, notation, and manuscript images.

{
  "id": "asset-audio-kyrie-demo",
  "type": "audio",
  "uri": "assets/audio/kyrie-demo.mp3",
  "linkedTo": "block-kyrie"
}

Asset Responsibilities

An asset record is metadata and linkage, not the binary file itself. Keep large media outside JSON and use a relative package URI or a stable external URI.

For portable packages, processors should resolve relative URIs from the package root. They should report a missing file without discarding the liturgical entity linked by linkedTo.

Record enough metadata to distinguish a demonstration from an authoritative source. At minimum, document the media type, rights or license, provenance, and the entity being illustrated. For audio and video, timeline bindings can connect service entities to exact segments without splitting the media into many files.

Schemas and supported values

Asset type

asset.type Definition ↗

External media kinds supported by asset records. Values outside this closed list are invalid.

audiovideoimagescanpdfnotationmanuscript-image