Data / Reuse

Available exports

• Interoperability preview JSON LUX IDs, reviewed external alignments, coverage flags, and next actions.
• CIDOC-CRM aligned preview JSON-LD CIDOC-CRM 7.1.3 classes and properties for lighthouse and lightship identity review.

Per-entity JSON endpoints

Individual lighthouse and heritage-asset pages link to small JSON files behind their "Open ... JSON" buttons (Evidence and data / Connection graph panels). Open the machine-readable index for each aspect's current URL pattern and record count.

• timelineDated lifecycle events for this lighthouse, derived from reviewed relationships.
• graphDirect relationship graph (nodes and edges) connecting this record to places, assets, and other entities within two steps.
• map-historyMovement/location points and paths for mapping this record's history.
• continuityCross-entity continuity profile: threads, related sites/assets/places, and their supporting evidence.
• spatiotemporal-profileReconstructed state-by-year slices combining location, structure, and light characteristic.
• state-profileThe record's state at each distinct historical phase (construction, modification, automation, etc.).
• light-signatureStructured light characteristic (flash pattern, color, period) for this active light.
• evidence-graphDerived graph of how sources, facts, identifiers, and lifecycle events support this record's claims.
• lifecycleDated lifecycle events for this heritage asset (installation, transfer, restoration, etc.).
• lifecycle-widerLifecycle events for objects related to this asset through a shared manufacturer or place, within two graph steps.
• graph-widerRelated-object graph reaching two steps beyond this asset's direct relationships.

These are build-time static files refreshed on every static-site build, not a live queryable API -- their JSON shape may still change between releases.

What current exports cover

Current public preview exports focus on lighthouse and lightship identity, reviewed external alignment, and reuse planning. They do not claim to export every governed relationship used by the public site.

What public pages expose beyond the exports

Selected asset, institution, and lighthouse identity-chain pages expose governed relationships in human-readable form after route, evidence, rights, and explanation checks.

What is intentionally not public

• Candidate rankings and excluded candidates
• Pilot allowlists and QA indexes
• Internal review findings
• Unpublished graph nodes
• Publication-boundary data

Contextual discovery indexes are derived build artefacts, not a stable public API.

How to fetch

curl https://light.lux143.org/exports/cidoc-crm/preview.jsonld

The JSON-LD file contains a top-level @context, metadata, summary counts, and an @graph of LUX lighthouse and lightship records.

What the CIDOC-CRM preview means

The CIDOC-CRM aligned preview maps LUX lighthouse and lightship identity rows to stable CIDOC-CRM classes and properties, including LUX IDs, public record URLs, titles, controlled types, and external-alignment policy metadata.

It is review-preview output and not a full CIDOC compliance claim. The export references the CIDOC-CRM 7.1.3 namespace and version; it does not vendor the CIDOC ontology or claim that every LUX field has a complete CIDOC mapping.

Safe reuse

External users may use these exports to identify LUX records, link back to public archive pages, compare LUX IDs with external identifiers, and plan catalog reconciliation or linked-data review.

External alignments are provenance links, not field evidence unless explicit field support exists. Do not infer coordinates, construction dates, light characteristics, status, names, or other factual fields from an external identifier alone.

Citation and links

When reusing LUX data, link to the public LUX record URL shown in the export and preserve the LUX ID. If a record or export marks uncertainty, keep that uncertainty visible in downstream use.

For citation examples and BibTeX entries, see How to Cite. For licensing terms, see Rights & Reuse.

For the evidence model behind the exports, read the Method / Evidence Policy. For source families and bibliographic context, see Sources.

Institutional reuse

Institutions planning identifier reconciliation, catalog reuse, corrections, or source review can use the existing Contact path. Please include the LUX ID, the external identifier or source URL, and the field or record you want to discuss.