> With all of these questions, possibilities and alternatives, perhaps > it would help if you were to write up some sort of formal > specification or even a Design Document for the code as you see it. > Even something as basic as an outlined header file including just the > interface methods and some documentation for those methods would allow > people to focus their thoughts and avoid the floundering in ideas.
There's some skeletal code in the VerseTreeKey class. We have VerseKey, which represents the key type of verse-based modules (Bibles & commentaries). And we have TreeKey, which represents the key type of hierarchical tree-based modules (RawGenBook). RawGenBook modules can contain anything, as long as it is organized as a hierarchical tree. Since Bibles are arranged as hierarchical trees of verses within chapters within books, we can use the RawGenBook storage format to hold Bibles and TreeKeys to access their contents, giving us much more flexibility in terms of versification. Now we want to use VerseTreeKey to interface RawGenBook-type Bible modules the same way we do RawVerse-type Bibles. > When I hear and think of this project I come up with thoughts such as: > > --There should be no restriction on the names of books, the numbers of > chapters and/or verses, or even the need to have discretized verses. > These should be taken directly from the input OSIS file itself when > the work is imported under the new scheme. > > --Since there is no restriction on the names of books, non-standard > books (as-in, those not in the standard Protestant or Catholic > scriptures), books like 3rd and 4th Maccabees, The Gospel of Thomas, > the various books in the Book of Mormon, etc, would need to have > allowable abbreviations specified in a configuration file distributed > with the module More or less. 3 & 4 Maccabees are part of the Bible. Thomas and the Book of Mormon are not. If we want to change the goals at a later date, we can, but the immediate objective is just to support books of the Bible. Furthermore, since we need to use standard abbreviations, we shouldn't be attempting to cram books into these modules for which abbreviations are not defined. I posted a complete list of OSIS Bible book abbreviations here: http://www.crosswire.org/wiki/index.php/DevTools:OSISBookNames --Chris _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
