29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 |
41 |
42 |
43 |
44 |
45 |
46 |
47 |
48 |
49 |
50 |
51 |
52 |
53 |
54 |
55 |
56 |
57 |
58 |
59 |
60 |
61 |
62 | Root:
63 |
64 |
65 |
66 |
67 |
68 |
69 |
--------------------------------------------------------------------------------
/HomeFiles/readme.md:
--------------------------------------------------------------------------------
1 | # The OSHB Lexicon App
2 |
3 | Our Lexicon App is a basic prototype application, to demonstrate the
4 | usage of the different parts of the lexicon, and their connection to
5 | the lemma attributes of the OSHB text. The easiest way to use the app
6 | in this form is to type one of those lemmas into the input box of the
7 | lexicon app, and Enter.
8 |
9 | 1. For example, if you look at Genesis 1:1, the first word has lemma
10 | b/7225. If you type this into the input box, the app will
11 | automatically choose the main word for you. The display should
12 | open up to the Lexical Index tab. It will show you the Word Group
13 | _reshiyth_ belongs to. At the top is the root word, then a list of
14 | words derived from that root, with _reshiyth_ checked. On the Brown,
15 | Driver, Briggs tab, you will find an abridged transcription of the
16 | BDB entry for that word. On the Strong’s Dictionary tab, you will
17 | find the corresponding entry from Strong’s Dictionary. You can use
18 | the radio buttons on the Lexical Index tab to look deeper into the
19 | context of the word in Hebrew.
20 |
21 | 2. The b in b/7225 represents the prefix, _bet_ in Hebrew. If you want
22 | to look up the definition for that, just enter b in the input box.
23 | You will notice that Strong has no entry for that ID.
24 |
25 | 3. The second word has lemma 1254 a. This is an indication that BDB
26 | has more than one entry corresponding to that word. If you enter
27 | the lemma that way, the app will remove the space, and locate the
28 | proper entry. If you want to see the difference in BDB for 1254b,
29 | you can enter that. Some words have as many as five or six entries
30 | in BDB. With the app in its present form, the only way to know that
31 | is either to find the words in the text, or to look at AugIndex.xml
32 | in the [repository](https://github.com/openscriptures/HebrewLexicon).
33 | There are 540 entries in all that are divided this way.
34 |
35 | 4. You can enter any Strong number. The app will automatically add the
36 | a, if needed. The Strong’s definition will still display correctly.
37 | You can investigate the distinctions BDB is making by following the
38 | instructions in #3, above.
39 |
40 | To learn more about the lexicon and what everything means, see the
41 | [documentation](https://github.com/openscriptures/HebrewLexicon/blob/master/HebrewLexicon.pdf).
42 |
43 | August 27, 2019
44 |
--------------------------------------------------------------------------------
/LiSchema.xsd:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
The Lexical Index schema is version 1.0.
9 | It is released to the public domain.
The OSHB Hebrew Lexicon is based in some significant work that has been done in
24 | matching the words of the Hebrew Bible to the entries in Brown, Driver, Briggs
25 | Hebrew and English Lexicon of the Old Testament. This provides a great amount
26 | of in-depth analysis of the individual words. At the same time, we recognize the
27 | value of the dictionary approach to accessing word definitions. We are also
28 | considering the great popularity of Strong’s Concordance, not only among Bible readers,
29 | but also among websites providing online access to the Bible. So we have merged the
30 | numbering of James Strong’s Concise Dictionary of the Words in the Hebrew Bible
31 | into the references in the Hebrew Bible. These are then augmented by letters
32 | distinguishing words where BDB has a finer-grained analysis. These augmented Strong
33 | numbers are then aligned with the entries in our lexicon. See the
34 | Lexicon App for a demonstration.
35 |
36 |
The Lexical Index was formed as a hub where all this information comes together.
37 | It includes the dictionary form of the word, its part of speech, a short gloss of its
38 | meaning, cross-reference information for the other parts of the system, and
39 | derivative information, for investigating the etymology of the word. It is also
40 | intended to make the lexicon extensible to include
41 | other works in the future. As I use the lexicon files in my own applications, I
42 | generate groups of related words, from the Lexical Index, as in the illustration, and
43 | connect with the specific word of interest at the time. This gives a more well-rounded
44 | understanding of the word within the language, as well as its scriptural context. The
45 | Lexicon App illustrates this usage of the lexicon.
46 |
47 |
If you want a more detailed description, you can see the
48 | Hebrew Lexicon Documentation.
49 | The files of the lexicon are also available at the
50 | OSHB Hebrew Lexicon,
51 | as well as the XML schema definition for each part of the lexicon. For more information
52 | on the Open Scriptures Hebrew Bible project in general, see the
53 | OSHB home page.
60 |
61 |
--------------------------------------------------------------------------------
/readme.md:
--------------------------------------------------------------------------------
1 | # The OSHB Hebrew Lexicon
2 |
3 | The Hebrew Lexicon is established in a modular format. It is comprised
4 | of three separate files:
5 |
6 | 1. BrownDriverBriggs.xml contains the current BDB content. It remains
7 | a work in progress. Entries can be filled out over time, especially
8 | in the area of completing the scripture references, and Hebrew words.
9 |
10 | 2. HebrewStrong.xml contains the content for Strong’s Hebrew Dictionary.
11 | Numerous corrections have been made, since the initial offering, in a
12 | significantly different form. The layout now has duplicated entries
13 | recombined.
14 |
15 | 3. LexicalIndex.xml is now the meeting place of BDB, Strong and the
16 | TWOT numbers, again significantly improved from the original Strong's
17 | Dictionary, and incorporating corrections that have arisen in the
18 | process of constructing the new lexicon.
19 |
20 | The lexical index is meant to bridge the gap between the accessibility
21 | and ubiquity of Strong's Dictionary, and the comprehensiveness and
22 | accuracy of BDB. For those versed in Hebrew, and wanting the depth of
23 | BDB, it can now be accessed on its own terms. For those more familiar
24 | with Strong numbers, or having current applications based on them, the
25 | lexical index provides access directly to entries via the Strong numbers.
26 |
27 | Additional files for the current iteration of the lexicon include:
28 |
29 | 1. AugIndex.xml to map the augmented Strong numbers of the OSHB to the
30 | IDs of the lexical index.
31 |
32 | 2. BdbSchema.xsd the XML schema for BrownDriverBriggs.xml.
33 |
34 | 3. LiSchema.xsd the XML schema for LexicalIndex.xml.
35 |
36 | 4. StrongSchema.xsd the XML schema for HebrewStrong.xml.
37 |
38 | 5. HebrewLexicon.pdf documentation for all parts of the lexicon.
39 |
40 | 6. index.html and its HomeFiles directory have been added to provide a
41 | home page for the lexicon project.
42 |
43 | 7. HomeFiles has been significantly expanded to implement the Lexicon
44 | App, for demonstrating the possibilities of the lexicon.
45 |
46 | TWOT numbers are included for reference purposes only. We are in no way
47 | directly transcribing the Theological Wordbook of the Old Testament.
48 |
49 | Thanks to Daniel Owens, for much help, especially in transcribing the
50 | main entries, not listed in Strong’s.
51 |
52 | These files are released under the
53 | [Creative Commons Attribution 4.0 International](http://creativecommons.org/licenses/by/4.0/)
54 | license. The actual text of Brown, Driver, Briggs and Strong’s Hebrew
55 | dictionary remain in the public domain. For attribution purposes,
56 | credit the Open Scriptures Hebrew Bible Project.
57 |
58 | Updated 8/27/2019
59 | Updated 8/2/2019
60 | 7/5/2013
61 |
--------------------------------------------------------------------------------
/sinri/HebrewStrongDictionary.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Hebrew Strong Dictionary
6 |
7 |
53 |
83 |
84 |
85 |
Hebrew Strong Dictionary
86 |
87 |
88 | Hebrew:
89 |
90 |
91 |
92 |
93 | Strong Number:
94 |
95 |
96 |
97 |
98 |
99 |
100 |
101 |
104 |
105 |
106 |
--------------------------------------------------------------------------------
/sinri/README.md:
--------------------------------------------------------------------------------
1 | # JSONify!
2 |
3 | provide tools to turn the Strong's Hebrew XML data into json, and provide a html sample to use as a live dictionay.
4 |
5 | > By Sinri Edogawa, 2017 March 18th
6 |
7 | > For attribution purposes, the XML building project is https://github.com/openscriptures/HebrewLexicon.
8 |
9 | > These files are released under the Creative Commons Attribution 4.0 International(http://creativecommons.org/licenses/by/4.0/) license. The actual text of Brown, Driver, Briggs and Strong’s Hebrew dictionary remain in the public domain. For attribution purposes, credit the Open Scriptures Hebrew Bible Project.
--------------------------------------------------------------------------------
/sinri/StrongXML2Json.php:
--------------------------------------------------------------------------------
1 | אָב
18 | $w=[
19 | "pos"=>(String)$entry->w['pos'],
20 | "pron"=>(String)$entry->w['pron'],
21 | "xlit"=>(String)$entry->w['xlit'],
22 | "src"=>(String)$entry->w['src'],
23 | "w"=>(String)$entry->w,
24 | ];
25 | // 2. a primitive word;
26 | $source=$entry->source->asXML();
27 | // 3. father, in a literal and immediate, or figurative and remote application
28 | $meaning=$entry->meaning->asXML();
29 | // 4. chief, (fore-) father(-less), × patrimony, principal. Compare names in 'Abi-'.
30 | $usage=$entry->usage->asXML();
31 | // 5. optional xlit ʼĂbîyshûwac corrected to ʼĂbîyshûwaʻ
32 | $note=$entry->note->asXML();
33 |
34 | $dictionary[$entry_id]=[
35 | "w"=>$w,
36 | "source"=>makeFalseAsEmptyString($source),
37 | "meaning"=>makeFalseAsEmptyString($meaning),
38 | "usage"=>makeFalseAsEmptyString($usage),
39 | "note"=>makeFalseAsEmptyString($note),
40 | ];
41 | $dictionary_mapping[$w['w']]=$entry_id;
42 | // echo $entry_id." Done. ";
43 | // if($debug_limit--<0)break;
44 | }
45 | echo PHP_EOL;
46 | // print_r($dictionary);
47 | // print_r($dictionary_mapping);
48 |
49 | $strong_book = ["dict"=>$dictionary,"mapping"=>$dictionary_mapping];
50 |
51 | $text=json_encode($strong_book);
52 | if(file_exists($json_file_path)){
53 | unlink($json_file_path);
54 | }
55 | $bytes=file_put_contents($json_file_path, $text);
56 | echo "Byte/{$bytes} written to {$json_file_path}!".PHP_EOL;
57 |
58 | function makeFalseAsEmptyString($x){
59 | if(empty($x))$x="";
60 | return $x;
61 | }
--------------------------------------------------------------------------------