It's coming....coming.... (or would you help us get it done???)...
A set of documented JSON formats (with schemas) to contain Bible data and indexes (rather than using the source USFM or USX or our ESFM).
These (intermediate) computer-readable formats are intended to be used in the middle of command-line (CLI) modules which can be chained/piped together (i.e., taking the output of one and using it as the input for the next one). The enclosed compilers are designed to be fast and simple with minimum error checking of the inputs and minimum user feedback, i.e., they are designed for processing Bibles that are finished and polished.
For a work-in-progress Bible, we recommend using our (Python) BibleOrgSys instead to load the files. Although that Bible Organisational System (also abbreviated BOS) uses the same intermediate formats, the input processors are designed to cope with the many various styles of sculpting (or abusing!) USFM and also with unfinished works and with human errors. The BOS also loads many other different Bible formats into these JSON formats.
The (compiled USFM or whatever) JSON formats.
These formats are designed for any texts which use the traditional Bible Book/Chapter/Verse (B/C/V) referencing. As well as Bibles themselves, this also includes other works such as Bible commentaries.
Fast Rust processors/parsers which load USFM or USX with minimal user feedback and compile the B/C/V text into these JSON formats.
Once we get that done, we would also consider an OSIS parser.
Please note that we would also be happy to include any other similar/better processors/parsers written in other computer languages such as C++ or Carbon, etc. if you're interested in collaborating.
These JSON formats are used by the following systems and/or organisations:
- our BibleOrgSys B/C/V checker and formatter
- our Biblelator B/C/V resource viewer and translation editor
- our Bible Door B/C/V reader app
- our forthcoming Biblelastic Bible-study app