The BDB Outline

[David Troidl]

Hi all,

The official release of the BDB Outline in online at
http://github.com/openscriptures/HebrewLexicon/downloads
It include the XML schema and the readme.

Questions or comments welcome.

Peace,

David

--
You received this message because you are subscribed to the Google Groups "Open Scriptures" group.
To post to this group, send email to open-sc...@googlegroups.com.
To unsubscribe from this group, send email to open-scriptur...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/open-scriptures?hl=en.

[Ze'ev Clementson]

Hi David,

On Wed, May 12, 2010 at 5:46 AM, David Troidl <David...@aol.com> wrote:
> Hi all,
>
> The official release of the BDB Outline in online at
> http://github.com/openscriptures/HebrewLexicon/downloads
> It include the XML schema and the readme.
>
> Questions or comments welcome.

This is excellent! Thank you for doing this (and releasing it as PD)
as this must have taken you a huge amount of time to collate. Just a
few questions (some of which I can guess at but which I just want your
confirmation on):

1. What's the difference (or significance of them having different
attributes) between the following word entries (they all have
different attributes):
<w strong="1417">גְּדוּד</w>
<w src="BDB" strong="1418">גְּדוּדָה</w>
<w src="Strong" strong="1417">גְּדֻדָה</w>
<w>גַּד</w>

2. Sometimes a ref has a word associated with it and sometimes not - why?:
<w>גִּדְגָּד</w>
<v ref="g.ao.am"/>
<v ref="x.bm.ab">חֹר</v>

3. What is the significance of the following 'type', 'cite', and the
form attributes (I saw the permissible values in the xsd schema but am
not sure of the exact usage) :
<entry id="g.cb.aa" type="root" cite="full" form="false">
   (e.g. - what's the difference between root/entry, full/partial, and
true/false values for these attributes?)

4. There is still no Page#1 - is there some reason for this or is this a bug?

5. Earlier, you indicated that you would be "numbering the WLC with
the new IDs" - is this still your intention? Presumably you will
associate both Strongs# and BDB ref with each WLC word? If so, what
attribute will you use for BDB ref?

6. In the first release (in April), you noted: "There are 521
unassigned Strong numbers.  I'll have to catalog those and look into
them. 7591 Strong numbers have a unique BDB entry.  This bodes well
for merging the IDs. The Strong numbers with multiple entries, 573, I
intend to break down by reference." - Did you resolve the issue of the
521 unassigned Strong numbers?

Thanks,
Ze'ev

[Ze'ev Clementson]

Hi all,

The latest version of my Hebrew Bible iphone/ipad app now has support
for the Brown–Driver–Briggs Hebrew Lexicon (BDB). This is as a result
of the work that David Troidl has done in creating a BDB outline
linking words defined in the Brown–Driver–Briggs Lexicon to their
Strong's Concordance numbers. By having a cross-reference of the
Brown–Driver–Briggs pages to specific Hebrew words from the Tanach, I
have been able to link directly to the relevant Brown–Driver–Briggs
page for each Hebrew word. This should be useful for anyone either
learning or wanting to improve their knowledge of Biblical Hebrew.
Anyone interested in this can get more detail (and screen shots) from
my blog post:

http://beresheit.blogspot.com/2010/05/bdb-support-in-hebrew-bible-iphoneipad.html

Thanks again to David for all of his work with both the Strongs and
BDB xml data!

- Ze'ev

On Wed, May 12, 2010 at 5:46 AM, David Troidl <David...@aol.com> wrote:

> Hi all,
>
> The official release of the BDB Outline in online at
> http://github.com/openscriptures/HebrewLexicon/downloads
> It include the XML schema and the readme.
>
> Questions or comments welcome.
>
> Peace,
>
> David
>
> --
> You received this message because you are subscribed to the Google Groups

> "opensiddur-tech" group.
> To post to this group, send email to opensid...@googlegroups.com.

> To unsubscribe from this group, send email to

> opensiddur-te...@googlegroups.com.

> For more options, visit this group at

> http://groups.google.com/group/opensiddur-tech?hl=en.
>
>

[Robert Hunt]

Dear David,

I was just looking at this BDB outline and have a few learner questions:

1/ Why doesn't it have an explicit <page p="1"/> tag anywhere?

2/ What is APTBibleTools from the namespace http://www.APTBibleTools.com/namespace. (I couldn't detect a server there.)

3/ Is only the outline public domain, not the content of the entries?

4/ Am I correct in assuming that the ids have no actual meaning, just unique and in a nice logical sequence?

5/ What does mod="II" mean? (That seems to be a BDB question, not an encoding question.)

6/ Did you enter all of this by hand? (Your README.txt only refers to scanned images of pages of the book with only the first two pages have a text layer.)

7/ What's the recommended module for dealing with structured XML like this in Python?

8/ Do you know anyone else currently using it other than Ze'ev?

It's wonderful having those links to the scanned images. That's what I was dreaming of doing with the OET-LV (Open English Translation of the Bible -- Literal Version) pointing to the original manuscripts.

Great work David, and Ze'ev for using it!

Robert.

On 30/05/10 08:30, Ze'ev Clementson wrote:

Hi all,

The latest version of my Hebrew Bible iphone/ipad app now has support
for the Brown�Driver�Briggs Hebrew Lexicon (BDB). This is as a result
of the work that David Troidl has done in creating a BDB outline
linking words defined in the Brown�Driver�Briggs Lexicon to their
Strong's Concordance numbers. By having a cross-reference of the
Brown�Driver�Briggs pages to specific Hebrew words from the Tanach, I
have been able to link directly to the relevant Brown�Driver�Briggs
page for each Hebrew word. This should be useful for anyone either
learning or wanting to improve their knowledge of Biblical Hebrew.
Anyone interested in this can get more detail (and screen shots) from
my blog post:

http://beresheit.blogspot.com/2010/05/bdb-support-in-hebrew-bible-iphoneipad.html

Thanks again to David for all of his work with both the Strongs and
BDB xml data!

- Ze'ev

On Wed, May 12, 2010 at 5:46 AM, David Troidl <David...@aol.com> wrote:
  

[David Troidl]

Hi Robert,

On 7/12/2010 8:06 PM, Robert Hunt wrote:

Dear David,

I was just looking at this BDB outline and have a few learner questions:

1/ Why doesn't it have an explicit <page p="1"/> tag anywhere?

The page elements are meant to record page breaks in the manuscript, and include the number of the page that starts after the break.

2/ What is APTBibleTools from the namespace http://www.APTBibleTools.com/namespace. (I couldn't detect a server there.)

Fictitious.� Maybe someday I'll register it, if I get around to having a website.

3/ Is only the outline public domain, not the content of the entries?

The whole BDB is public domain, since the copyright expired, at least in the USA.� Check your local copyright laws.

4/ Am I correct in assuming that the ids have no actual meaning, just unique and in a nice logical sequence?

The first section is meant to be a rough ASCII transliteration character for the first letter of the main entries in that section, with 'a' prefixed for Aramaic.� The rest are just sequential, and potentially extensible.

5/ What does mod="II" mean? (That seems to be a BDB question, not an encoding question.)

BDB splits some of the consonantal roots into several derivations.� These are indicated by I, II, etc.

6/ Did you enter all of this by hand? (Your README.txt only refers to scanned images of pages of the book with only the first two pages have a text layer.)

Yes.

7/ What's the recommended module for dealing with structured XML like this in Python?

I'm not a Python person.� Maybe someone else could address this.

8/ Do you know anyone else currently using it other than Ze'ev?

Not to my knowledge.

It's wonderful having those links to the scanned images. That's what I was dreaming of doing with the OET-LV (Open English Translation of the Bible -- Literal Version) pointing to the original manuscripts.

It would be great if you could make use of it.� I was about halfway through mapping the words of the WLC to their entries in BDB, when I got distracted by more pressing work.� I'm hoping to get to that sometime.

Great work David, and Ze'ev for using it!

Thanks.

Peace,

David

--
You received this message because you are subscribed to the Google Groups "Open Scriptures" group.
To post to this group, send email to open-sc...@googlegroups.com.
To unsubscribe from this group, send email to open-scriptur...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/open-scriptures?hl=en.

[Jesse Griffin]

Robert,

This is an old thread, but I thought I would respond to the Python XML question.  I'm thinking of writing a python script to convert the BDB xml files into a Python dictionary.  For now I have just written a quick script that creates a python dictionary for each word that includes the definitions only.

I'm using minidom from xml.dom.  See https://github.com/jag3773/d-bdb for the script.

Thanks,
Jesse

On Mon, Jul 12, 2010 at 6:50 PM, David Troidl <David...@aol.com> wrote:

Hi Robert,

On 7/12/2010 8:06 PM, Robert Hunt wrote:

Dear David,

I was just looking at this BDB outline and have a few learner questions:

1/ Why doesn't it have an explicit <page p="1"/> tag anywhere?

The page elements are meant to record page breaks in the manuscript, and include the number of the page that starts after the break.

2/ What is APTBibleTools from the namespace http://www.APTBibleTools.com/namespace. (I couldn't detect a server there.)

Fictitious.  Maybe someday I'll register it, if I get around to having a website.

3/ Is only the outline public domain, not the content of the entries?

The whole BDB is public domain, since the copyright expired, at least in the USA.  Check your local copyright laws.

4/ Am I correct in assuming that the ids have no actual meaning, just unique and in a nice logical sequence?

The first section is meant to be a rough ASCII transliteration character for the first letter of the main entries in that section, with 'a' prefixed for Aramaic.  The rest are just sequential, and potentially extensible.

5/ What does mod="II" mean? (That seems to be a BDB question, not an encoding question.)

BDB splits some of the consonantal roots into several derivations.  These are indicated by I, II, etc.

6/ Did you enter all of this by hand? (Your README.txt only refers to scanned images of pages of the book with only the first two pages have a text layer.)

Yes.

7/ What's the recommended module for dealing with structured XML like this in Python?

I'm not a Python person.  Maybe someone else could address this.

8/ Do you know anyone else currently using it other than Ze'ev?

Not to my knowledge.

It's wonderful having those links to the scanned images. That's what I was dreaming of doing with the OET-LV (Open English Translation of the Bible -- Literal Version) pointing to the original manuscripts.

It would be great if you could make use of it.  I was about halfway through mapping the words of the WLC to their entries in BDB, when I got distracted by more pressing work.  I'm hoping to get to that sometime.

Great work David, and Ze'ev for using it!

Thanks.

Peace,

David

Robert.


On 30/05/10 08:30, Ze'ev Clementson wrote:

Hi all,

The latest version of my Hebrew Bible iphone/ipad app now has support
for the Brown–Driver–Briggs Hebrew Lexicon (BDB). This is as a result
of the work that David Troidl has done in creating a BDB outline
linking words defined in the Brown–Driver–Briggs Lexicon to their
Strong's Concordance numbers. By having a cross-reference of the
Brown–Driver–Briggs pages to specific Hebrew words from the Tanach, I
have been able to link directly to the relevant Brown–Driver–Briggs
page for each Hebrew word. This should be useful for anyone either
learning or wanting to improve their knowledge of Biblical Hebrew.
Anyone interested in this can get more detail (and screen shots) from
my blog post:

[evstevemd]

Nice one!

On Apr 25, 5:23 am, Jesse Griffin <jag3...@gmail.com> wrote:
> Robert,
>
> This is an old thread, but I thought I would respond to the Python XML
> question.  I'm thinking of writing a python script to convert the BDB xml
> files into a Python dictionary.  For now I have just written a quick script
> that creates a python dictionary for each word that includes the
> definitions only.
>
> I'm using minidom from xml.dom.  Seehttps://github.com/jag3773/d-bdbfor
> the script.
>
> Thanks,
> Jesse
>
>
>
>
>
>
>

> On Mon, Jul 12, 2010 at 6:50 PM, David Troidl <DavidTro...@aol.com> wrote:
> > **

> > Hi Robert,
>
> > On 7/12/2010 8:06 PM, Robert Hunt wrote:
>
> > Dear David,
>
> > I was just looking at this BDB outline and have a few learner questions:
>
> > 1/ Why doesn't it have an explicit <page p="1"/> tag anywhere?
>
> > The page elements are meant to record page breaks in the manuscript, and
> > include the number of the page that starts after the break.
>
> > 2/ What is APTBibleTools from the namespace
> >http://www.APTBibleTools.com/namespace. (I couldn't detect a server
> > there.)
>
> > Fictitious.  Maybe someday I'll register it, if I get around to having a
> > website.
>

> > 3/ Is only the *outline* public domain, not the *content* of the entries?

> >http://beresheit.blogspot.com/2010/05/bdb-support-in-hebrew-bible-iph...

>
> > Thanks again to David for all of his work with both the Strongs and
> > BDB xml data!
>
> > - Ze'ev
>

> > On Wed, May 12, 2010 at 5:46 AM, David Troidl <DavidTro...@aol.com> <DavidTro...@aol.com> wrote:
>
> >  Hi all,
>

> > The official release of the BDB Outline in online athttp://github.com/openscriptures/HebrewLexicon/downloads