<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">In testing the beta GenBooks, I saw something I didn't care for and it got me thinking.<div><br></div><div>In the beta GenBook "Imitation" the tree is something like:</div><div>Book 1</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Chapter 1<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Chapter 2<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>...<br></div><div>Book 4</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>...</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Chapter 18<br></div><div><br></div><div>In each of these parts, they start with a declarative heading like:</div><div><span class="Apple-style-span" style="font-family: Times; font-size: 14px; "><div class="sectiontitle" style="">BOOK FOUR</div><div class="sectiontitle" style="">AN INVITATION TO HOLY COMMUNION</div><div class="sectiontitle" style="">The Voice of Christ</div><div class="sectiontitle" style=""><br></div><div class="sectiontitle" style="">and</div><div class="sectiontitle" style=""><br></div><div class="sectiontitle" style="font-weight: bold; "><span class="Apple-style-span" style="font-weight: normal; "><div class="sectiontitle" style="">The First Chapter</div><div class="sectiontitle" style="">The Great Reverence With Which We Should Receive Christ</div><div class="sectiontitle" style="">The Disciple</div><div class="sectiontitle" style=""><br></div><div class="sectiontitle" style="">What I didn't like was the non-descriptive, relatively meaningless keys. From a reader's perspective, I expected a "Table of Contents" like I see in any/every book, with descriptive titling of the chapters.</div><div class="sectiontitle" style=""><br></div><div class="sectiontitle" style="">I.E.</div><div class="sectiontitle" style="">Book 1: Thoughts Helpful in the Life of the Soul</div><div class="sectiontitle" style=""><span class="Apple-tab-span" style="white-space:pre"> </span>Chapter 1: Imitating Christ and Despising All Vanities on Earth</div><div class="sectiontitle" style=""><span class="Apple-tab-span" style="white-space:pre"> </span>Chapter 2: Having a Humble Opinion of Self</div><div class="sectiontitle" style="">...</div><div class="sectiontitle" style=""><br></div><div class="sectiontitle" style="">But, the thought I had was that having keys like Imitation.1.1 (or even Imitation.Book_1.Chapter_1) would be useful, but not for viewing. Having long keys is not useful for cross-references. Some of the new beta modules have rich cross-references.</div><div class="sectiontitle" style=""><br></div><div class="sectiontitle" style="">For dictionaries, such as Strong's, I'd like to see the actual headword, perhaps prefixed with the number, in the listing of "words" in the dictionary. (With TEI dictionaries, this is relatively straight forward to dig out of the text. It is the "first" <orth> element's content.)</div><div class="sectiontitle" style=""><br></div><div class="sectiontitle" style="">For daily devotions, I'd rather not see 01.22, but localized "January 22" (Bible Desktop does this now).</div><div class="sectiontitle" style=""><br></div><div class="sectiontitle" style="">So basically, I'd like for SWORD modules to define an internal key (as is done today) and optionally, an external display key. Either of which would be useful for searching.</div><div class="sectiontitle" style=""><br></div><div class="sectiontitle" style="">This is something we do today with Bibles. The actual key is an index number into the KJV versification. We use transformations to go between verse references and this ordinal value.</div><div class="sectiontitle" style=""><br></div><div class="sectiontitle" style="">In Him,</div><div class="sectiontitle" style=""><span class="Apple-tab-span" style="white-space:pre"> </span>DM<br></div><div class="sectiontitle" style=""><br></div></span></div></span></div></body></html>