Re: [Tyndale STEP - Programming] Re: Bible book abbreviations and references

We could do... I was wondering if we might ever want to do a range search and how that would work in practice...
what if we want all the historical information linked to Ex.1-2:5

It could be JSword provides us with a list of verses that we can cross-reference on our database...

If we mapped this out to a numerical form and stored a composite key that might make things easier and faster too...

Ex would be 2
The expression would be converted to: where chaptere = 1 or (chapter = 2 and verse <= 5)

Either way, it would make sense to work out what JSword can provide. But we need to remember that we'll need cross reference things to our own DB at some point, and multiple string comparaisons and manipulations could be expensive...

Chris

2009/9/10 Tyndale STEP Project <TyndaleSTEP@gmail.com>

Colin, pointed out that we need a standard list of Bible abbreviations,
and suggests we fit in with the Crosswire list, which is well worked out.

Maybe we've agreed this but I can't see it anywhere. If we haven't, then
given we're building off Crosswire, I think it makes sense to use their
abbreviations, listed at:
http://www.crosswire.org/wiki/OSIS_Book_Abbreviations
together with their internal dot notation for internal use (easier to parse), i.e.,

internally we have 1Cor.5, 1Cor.5.14, but we output it as "1 Cor 5", "1
Cor 5:14" (assuming not 1 Cor. 5 with the dot).

plus the obvious set of ranges

1Cor.5:5-6:7
1Cor.5:5-7
1Cor.5-6
1Cor.5-6:7

Colin

--
Posted By Tyndale STEP Project to Tyndale STEP - Programming on 9/10/2009 01:20:00 AM