Public data reuse
Data / Reuse
LUX Light Archive publishes small review-preview exports for researchers, catalog maintainers, and institutions that want to reconcile lighthouse heritage identities or plan linked-data reuse.
These exports prioritize stable identity and provenance over API breadth or completeness.
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.
How to fetch
curl https://light.lux143.org/exports/cidoc-crm/preview.jsonldThe 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.
Current status
This page documents early reuse surfaces, not a stable public API platform. Export files are review-preview outputs, and their structure may change before a stable public data contract exists.
A fuller data dictionary is planned as documentation when the export contract is mature enough to describe without overstating stability.