No Description

Jesse Griffin 6b8b41d21b Update '' 3 months ago
LICENSE bea112b49d initial commit 8 months ago
Project 3972a48855 Project Explanation 7 months ago 6b8b41d21b Update '' 3 months ago
Volunteer job ccc03f1994 corrected markdown formatting errors 7 months ago


The resource we are using as our UHB is the Open Scriptures Hebrew Bible. This project is the Westminster Leningrad Codex with Strongs lexical data and morphological data marked up in OSIS files.

Parsing Status

See the parsing status for the whole Old Testament. Or use the book by book links below.


Initial Inclusion in tC

Get tC to support OSIS XML files like

  • Lexical data is encoded in lemma attribute, which is the word's Strongs number
  • Morph data is encoded in morph attribute, key here

May as well read the files directly from unless we want to create a process to put this into our container format.

Currently, I'm only seeing about 1% of the words in those files has having morphological data.

Finishing Morphological Data

Stage 1

Write a comparer script that can verify our proposed parsings from against an existing dataset (such as If they check out then they can be marked as verified and included in the XML files.

Stage 2

Create a process that takes verified parsings from and programmatically guess at the rest of the words in the OT (e.g. strip cantillation and find and replace for unknowns). Feed these back into the parsing system at and verify them against an existing dataset and/or Editors.

If we can make this an iterative process then we would be able to cut down the amount of manual intervention necessary to get the morph data.


After the morphology data is complete, the UHB project will effectively be completed. At the moment there are no further plans to markup the text with other information.