[B-Greek] Strongs Numbers (was "Inaccurate electronic versions")
James Tauber
jtauber at jtauber.com
Thu Jan 25 17:00:23 EST 2007
[I hope the list doesn't mind indulging me in answering this on-list]
The basic issue is that a simple enumeration of lexemes isn't sufficient
because there is no one correct way to slice the lexemes.
No two lexicons will agree on whether certain pairs of words are the
same lexeme or not.
For example, is BASILEIOS the adjective 'royal' the same lexeme as
BASILEION when used to mean 'palace'?
Is MECRI the same lexeme as MECRIS?
Is EGO the same lexeme as SU?
Is ANAPEIROS the same lexeme as ANAPHROS?
I don't want to get into a discussion as to the specific answers. The
point is that difference lexicons will have a different answer to each
of these. So any database system that has foreign keys into lexical
information coming from different sources, needs to be able to handle
this.
The solution developed by Ulrik Petersen and myself is to number nodes
in a lattice rather than simply enumerate a flat list.
Under this system, MECRI would have a number, MECRIS would have a number
and the join node "MECRI OR MECRIS" would have a number. This way G/K
(who treat them as distinct) can map to them individually, whereas
Strong (who treats them as a the same) can map to the join node.
You can read an earlier draft of a paper we wrote here:
http://jtauber.com/2006/03/28/new-numbering-system.pdf
We will hopefully be publishing our actual numbers soon, including
mappings from/to Strong's and G/K.
James
http://jtauber.com/2006/03/28/new-numbering-system.pdf
On Thu, 25 Jan 2007 16:07:37 -0500, "Alan Bunning" <bunning at verizon.net>
said:
> I would be interested in what system you are going to use. I was going to
> use a system that was backwards compatible with Strongs. Thus, the
> current
> Strongs numbers would be used. And then a "1" digit would be added to the
> words where Strongs goofed up within his own system (thus 2312' would
> become
> 12312 and 2526' would become 12526). Then a "2" digit would be added for
> words that aren't in Strongs, while still keeping the last 4 digits in
> alphabetical order relative to Strongs. Thus, this keeps the current
> system
> intact while allowing expansion and still fitting in 2-bytes. What do you
> think of this? What did you come up with?
>
> Alan Bunning
>
> > -----Original Message-----
> > From: James Tauber [mailto:jtauber at jtauber.com]
> > Sent: Thursday, January 25, 2007 6:47 AM
> > To: bunning at verizon.net
> > Cc: b-greek at lists.ibiblio.org
> > Subject: Re: [B-Greek] Inaccurate electronic versions
> >
> > I should also add, of particular relevance to you, that we
> > are working on an alternative to using Strong's numbers (or
> > G/K for that
> > matter) as the primary key for lexical data.
> >
> > James
> >
> > On 25/01/2007, at 6:26 AM, James Tauber wrote:
> >
> > >
> > > It's the lemmatization that I've mostly focused on over the last
> > > twelve years on and off.
> > >
> > > You are correct that the original CCAT database made available in
> > > 1993 has a lot of errors -- thousands, if you count instances.
> > >
> > > If you get the CCAT file from anywhere other than jtauber.com or
> > > morphgnt.org, you are probably getting either the original CCAT
> > > release from 1993 or one from around 1995 with my first round of
> > > corrections. It's the latter which Broman and others were making
> > > available (and which was the basis for the late Tony Fisher's site).
> > >
> > > However, many significant corrections have been made since then,
> > > especially in 2002 and since 2004.
> > >
> > > Since December 2005, I've been working with Ulrik Petersen (who in
> > > parallel to my CCAT/UBS work had been working on
> > Tischendorf and other
> > > texts). We are working on integrating our data, the first fruits of
> > > which should be available soon.
> > >
> > > James
> > >
> > >
> > > On 24/01/2007, at 6:35 PM, Alan Bunning wrote:
> > >
> > >> Thanks for the info! I'll take a look and compare it with what I
> > >> have. I certainly don't want to have to reinvent the
> > wheel. It does
> > >> look like there is some overlap. Let me know if anything I
> > am doing
> > >> can help your cause. The next thing I was planning on doing, was
> > >> correcting the parsings and roots for those same texts. As
> > I said, I
> > >> barely got started and already found a tremendous number
> > of errors.
> > >> What sort of work have you done in this regard?
> > >> I will certainly add the set you have to the mix when I
> > compare them.
> > >
> > > ---
> > > B-Greek home page: http://www.ibiblio.org/bgreek B-Greek
> > mailing list
> > > B-Greek at lists.ibiblio.org
> > > http://lists.ibiblio.org/mailman/listinfo/b-greek
> >
> > --
> > No virus found in this incoming message.
> > Checked by AVG Free Edition.
> > Version: 7.5.432 / Virus Database: 268.17.10/651 - Release
> > Date: 1/24/2007 6:48 PM
> >
> >
>
--
James Tauber http://jtauber.com/
journeyman of some http://jtauber.com/blog/
More information about the B-Greek
mailing list