KJV 1769 JSON export
Use: Prior plain-text scripture baseline and verse-count cross-check for all 66 KJV books.
Source: Scrollmapper Bible Versions and Cross-Reference Databases, formats/json/KJV.json.
Version: master commit e1b254cef86d0e65b1a5d1a94b8b112d0f296a2c.
License note: Repository export is listed under MIT; KJV text is public domain in the United States.
SHA-256: f0b09dc49dfb97bb...
CrossWire KJV OSIS with Strong's Numbers and Morphology
Use: Full KJV verse text, English phrase-to-Strong's tagging, and morphology codes.
Source: CrossWire Bible Society GitLab source file kjv.osis.xml.
Version: master branch file downloaded on 2026-07-22.
Coverage: 31,102 tagged verses, 348,965 English phrase tokens, and 366,939 Strong's source links.
License note: CrossWire offers the KJV project tagging freely; KJV text is public domain in the United States with Crown-right restrictions in the United Kingdom.
SHA-256: 4bcbfe45722fca39...
Open OSIS source
Matthew Henry's Concise Commentary
Use: Verse-range commentary displayed separately from scripture.
Source: Christian Classics Ethereal Library UTF-8 text download.
Coverage: 3,362 parsed source sections, Genesis 1:1-2 through Revelation 22:20-21.
License note: Public Domain status is recorded from the downloaded source header.
SHA-256: 7af7f0feef2a8522...
Open source text
STEPBible Translators Brief Lexicons
Use: Searchable Hebrew and Greek Strong's lexicon entries.
Source: STEPBible-Data TBESG and TBESH lexicon files.
Coverage: 23,663 normalized parsed Hebrew and Greek keys used for Strong's lookup definitions.
License note: CC BY as stated by the recorded source package.
Greek SHA-256: 312f723d7b8ef263...
Open STEPBible lexicon directory
Data boundaries
Text comparison: 152 CrossWire KJV OSIS verse strings differ from the prior Scrollmapper plain-text export after simple whitespace and quote normalization.
Lexicon boundary: CrossWire supplies English phrase-to-Strong's links; STEPBible supplies the brief lookup definitions. The two sources are attributed separately.
Hosting boundary: The public site remains static. SQLite artifacts are generated for the planned PHP read-only proof of concept, not read directly by browser JavaScript.