Title Abstract Acknowledgments Theory Results and Discussion Terminology References Appendices Background Prophecy and Fulfillment Autobiography Style of Writing WordEngineering Ken Adeniji A thesis submitted for the degree of Doctor of Philosophy in the Faculty of Science. Abstract Thesis Statement: This dissertation introduces AlphabetSequence ( 2 Corinthians 10:9-18 ). The AlphabetSequenceIndex is the result of a pure function to sum alphabet places AlphabetSequence.cs . The AlphabetSequenceIndexScriptureReference are the offsets from the beginning and the ending of the Scripture. The AlphabetSequenceIndexScriptureReference consists of four parts; there are two references each to particular chapters and verses. The first mention is the forward verse, which the author calculates by determining the AlphabetSequenceIndex verse in the Bible. The second mention is the forward chapter, and this the author calculates as before, but by substituting the verse with the chapter. Both the backward chapter and backward verse are the corresponding, anticlockwise places. The importance of this work? Follow God, as a character. To track dates and words? And, find meaning, correlation. Where does the Bible list? Creation days, genealogies, allies, plagues, tribes, journey, commandments, reigns, kingdoms, disciples, fruit of the Holy Spirit, churches. Acknowledgments Chuck Missler of Koinonia House (KHouse) is worthy of note, faith (Hebrews 11). There is indebtedness of the author to Ury Schecow, his Masters degree supervisor, at the University of Technology, Sydney (UTS), 15 Broadway Ultimo (NSW), 2007, Australia. The author is grateful to Tom Osborne, his Artificial Intelligence instructor; and Brian Henderson-Sellers, his Object Oriented Technology instructor; both also at UTS. The author makes mention of his colleagues at UTS; Decler Mendez, Cesar Orcando, Ricardo Lamas and Peter Milne. The author stretches his open hand to Robyn A. Lindley, his Doctorate supervisor at the University of Wollongong (UOW), NSW 2522, Australia. Theory 2004-11-10 www.JesusInTheLamb.com Part Example Commentary Sub-domain www A sub-domain defaults to www. Domain JesusInTheLamb Country code top-level domain (ccTLD) .com An abbreviation for commercial. A default domain extension. Directory and filename index.html Fragment It is not an e-mail address, since it does not include an at sign, @. It defaults to port 80. It defaults to the homepage. The issuing of this domain name may be related to commencing writing the book titled Ocean Senior. There has not been a follow-up on future artifacts. But when one reads the Bible, the book of Revelation, which starts with the letters to the 7 churches in Asia Minor, does not instigate future alteration. The Bible Database The Scripture Table The content of the Bible SQL Server database is principally the Scripture table. The Scripture table has a composite primary key , which consists of three columns; the BookID, ChapterID, and VerseID columns. The SQL statement ALTER TABLE Bible..Scripture ADD CONSTRAINT PK_Scripture PRIMARY KEY CLUSTERED ( BookID ASC, ChapterID ASC, VerseID ASC ) is for setting the primary key. There are varchar(MAX) columns which has the text for each Bible version. The Scripture Table's BookID Column Because there are sixty-six books in the Bible, the BookID ranges between 1 and 66; starting from Genesis and ending at Revelation. The SQL statement ALTER TABLE Bible..Scripture ADD CONSTRAINT CK_Scripture_BookID_Range CHECK (BookID BETWEEN 1 AND 66) will set the range restriction. The Scripture Table's ChapterID Column The ChapterID ranges between 1 and 150; the SQL statement SELECT MAX(ChapterID) FROM Bible..Scripture is for determining the upper limit. The SQL statement ALTER TABLE Bible..Scripture WITH CHECK ADD CONSTRAINT CK_Scripture_ChapterID_Range CHECK (([ChapterID]>=(1) AND [ChapterID]<=(150))) will set the range restriction. The Scripture Table's VerseID Column The VerseID ranges between 1 and 176; the SQL statement SELECT MAX(VerseID) FROM Bible..Scripture is for determining the upper limit. The SQL statement ALTER TABLE Bible..Scripture WITH CHECK ADD CONSTRAINT CK_Scripture_VerseID_Range CHECK (([VerseID]>=(1) AND [VerseID]<=(176))) will set the range restriction. The Scripture Table's KingJamesVersion Column The author would have considered placing an index on the KingJamesVersion column, but the author found out during his research that the verses in the KingJamesVersion are not unique nor distinct, and indexes are not applicable to where like query conditions with leading wildcards. The Scripture View's Testament Column The SQL statement (case when BookID <=(39) then 'Old' else 'New' end) will set this computed column. The Testament column serves as a filter, such as, in the BibleWord. The Scripture View's BookTitle Column The SQL statement dbo.udf_BookTitle(BookID) It is for determining this computed column. As expected, there is a correlation between the BookID column, and its corresponding BookTitle column; it progresses from Genesis to Revelation. Because SQL does not support arrays, the author chose to write an SQL CLR C# function for determining the BookTitle when passed the BookID. Although C# supports Design by contract assertions, the author only checks BookID range validity, and returns NULL, if the argument does not fall within this range. The author could throw exceptions, but the author does not know the side effects nor the full ramifications. Instead of writing and determining the book title using C#, an alternative is to use a database table. A table with two columns, BookID and BookTitle, will store and make extractable the sixty-six books. For example, the first book of the New Testament, the 40th book, spelling is Matthew or Mathew, double tt versus (VS) single t. An improvement on the current implementation is to use soundex to decipher the book title and the corresponding BookID. The Scripture Table's ScriptureReference Column The SQL statement dbo.udf_ScriptureReference(BookID, ChapterID, VerseID) Will calculate the conjecture of the BookTitle, ChapterID, and VerseID. Since this is a computed column, therefore, the author is not able to set its Entity Integrity; if it were not the SQL statement ALTER TABLE Bible..Scripture ADD CONSTRAINT uc_Scripture_ScriptureReference UNIQUE (ScriptureReference) Will set its entity integrity. The distinction between raw data versus computed columns is performance and space. The Scripture Table's ChapterIDSequence Column When loading data, the author decides the ChapterIDSequence column, and increments it when the BookID and ChapterID, change during loading. The ChapterIDSequence ranges between 1 and 1189, starting in Genesis 1 and ending at Revelation 22. The SQL statement SELECT BookID, ChapterID FROM Bible..Scripture GROUP BY BookID, ChapterID ORDER BY BookID, ChapterID will decide the greatest value for ChapterIDSequence. An alternative SQL statement select count( distinct cast(BookID as varchar(6)) + ' ' + cast(ChapterID as varchar(6)) ) FROM Bible..Scripture Another SQL statement ; with cte ( BookID , ChapterID ) as ( select distinct BookID, ChapterID FROM Bible..Scripture ) select cnt = count(*) from cte The SQL statement ALTER TABLE Bible..Scripture ADD CONSTRAINT CK_Scripture_ChapterIDSequence_Range CHECK (ChapterIDSequence BETWEEN 1 AND 1189) will check the range correctness. Although it is good to know the ChapterIDSequence, but it is primarily used to decide the boundaries for scripture reference queries. The Scripture Table's VerseIDSequence Column When loading data, the author calculates the VerseIDSequence column, and increments it, every time, the BookID, ChapterID, and VerseID changes during the data load. There are some Bible books that have only one chapter, such as, Obadiah, Philemon, 2 John, 3 John, Jude; therefore, the author is careful when the choice is made to increment and update the VerseIDSequence column. The SQL statement SELECT BookTitle FROM Bible..Scripture GROUP BY BookID, BookTitle HAVING MAX(ChapterID) = 1 ORDER BY BookID is for listing these one chapter, Bible books. The VerseIDSequence ranges between 1 and 31102; starting from Genesis 1:1, and ending at Revelation 22:21. The SQL statement SELECT COUNT(*) FROM Bible..Scripture will decide the greatest value for VerseIDSequence, the total number of rows, records, in the Bible..Scripture table. The SQL statement ALTER TABLE Bible..Scripture ADD CONSTRAINT CK_Scripture_VerseIDSequence_Range CHECK (VerseIDSequence BETWEEN 1 AND 31102) will do the data integrity. As said earlier, although it is good to know the VerseIDSequence, but it is primarily used to decide the boundaries for scripture reference queries. The identity functionality which auto-increments, before inserting each row is useful, for ensuring this candidate primary key, abides by the entity integrity constraint; however, The SQL statement ALTER TABLE Bible..Scripture ADD CONSTRAINT AK_Scripture_VerseIDSequence UNIQUE (VerseIDSequence) is supplementary. The Scripture_View BibleReference Column The SQL statement ((right('00'+CONVERT([varchar](2),[BookID],(0)),(2))+right('000'+CONVERT([varchar](3),[ChapterID],(0)),(3)))+right('000'+CONVERT([varchar](3),[VerseID],(0)),(3))) will combine the BookID, ChapterID, and VerseID. This is a convention for referring to Bible rows, by a unique identifier, which consists of the BookID, ChapterID, and VerseID. The leading zeros are placeholders for blocks of IDs, such as, BookID which will have two digits, ChapterID which will have three digits, and VerseID which will also have three digits. It is easier, faster, and more compact to restrict and order by numbers rather than text. Listed below, is the result set, for this SQL statement. SELECT ScriptureReference, BibleReference FROM Bible..Scripture_View WHERE BookID = 43 AND ChapterID = 1 AND VerseID = 1 ScriptureReference BibleReference John 1:1 43001001 There is a conversion page BibleReference.html. Please note, that the author has not developed this further, it is just an introduction and speculation, which others may wish to adopt. Most of the applications, extract information, and query the Scripture table. If the user chooses to, he may choose to load another Bible version, into the Scripture table and the application will still work as usual, and there will be no need to make changes to the application; thereby, achieving Separation of concerns (SoC). The Exact Table The Exact table's, primary task, is to tell, on the words that are in the Bible. Its information set include each word's first and last scripture reference occurrence(s), and count of occurrence(s). If the word, occurs only once, then the last occurrence is set to null. The incentive for writing the exact module comes from Dave Hunt, who will talk of each word's specifics, and Chuck Missler who noted that the first occurrence of the word, love is in Genesis 22:2. The exact table, is a holding area, for staging information; it could be argued that there is no need, to have this table, because it sources its information from the Scripture table, and it is available using Language Integrated Query. The reasoning of the author is that the Scripture table is static data, and it does not need processing, each time, there is a request. Speed and lower work load are the advantages of the approach of the author; its disadvantage is that the exact table needs re-population, when there is a shift to another Bible version, which the author does not project, at this time. If there is a need, to support another Bible version, then the Exact table loading procedure needs expansion to aid, this flexibility. The Exact result for the author's initials, KAA, is Karkaa, meaning floor (Joshua 15:3). Word Occurrences is dynamic, and it supports the other versions of the Bible. The Exact Table's ExactID Column The ExactID is an identity column, meaning the database, SQL Server, auto-increments its value, before insertion. There are 12891 unique words, in the Bible..Exact table. The SQL statement SELECT MAX(ExactID) FROM Bible..Exact is for determining the highest value. The SQL statement SELECT COUNT(BibleWord) FROM Bible..Exact is for determining the word count. The SQL statement ALTER TABLE Bible..Exact ADD CONSTRAINT CK_Exact_ExactID_Range CHECK (ExactID BETWEEN 1 AND 12891) is for the range restriction. For storage reason, the author has chosen, not to have a unique index, on this candidate primary key; in-spite, of it being a query item. Future implementation, may issue the SQL statement CREATE UNIQUE INDEX AK_Exact_ExactID ON Bible..Exact(ExactID) SELECT SUM(FrequencyOfOccurrence) FROM Bible..Exact is 789631; this is the count of the words in the KJV Bible. The Exact Table's BibleWord Column These are the words that occur in the Bible, in the order of their occurrences. The author sets the primary key, the constraint, by issuing the SQL statement ALTER TABLE dbo.Exact ADD CONSTRAINT PK_Exact PRIMARY KEY CLUSTERED (BibleWord ASC) The Exact Table's FirstOccurrenceScriptureReference Column This is the scripture reference where the word first occurs in the Bible. The author may set-up the relationship by issuing the SQL statement ALTER TABLE dbo.Exact WITH CHECK ADD CONSTRAINT FK_Exact_Scripture FOREIGN KEY(FirstOccurrenceScriptureReference) REFERENCES dbo.Scripture (ScriptureReference) Please note, that as discussed earlier, the author cannot have, a unique constraint, on the Bible..Scripture.ScriptureReference column, since this is a computed column; the author can not keep up the relationship, at this time. The Exact Table's LastOccurrenceScriptureReference Column This is the reference to the scripture where the word last occurs in the Bible; if there is only one occurrence, the value of this entry is null. As with the FirstOccurrence column, the referential integrity rule applies. The Exact Table's Difference Column This is to measure the word's longevity; the difference in VerseIDSequence between when it first and last appeared. The Exact Table's Occurrence Column This is the pervasiveness of the word, how often is the word used in the Bible? The WordEngineering Database The WordEngineering SQL Server database, mainly consists, of four tables - HisWord, Remember, APass, ActToGod. The HisWord Table The HisWord table is what the author heard from the source. The entries in the HisWord table are exact and representable in alphanumeric format (Numbers 12:6-8). In following, the Bible's New Testament convention, where there are translations of Hebrew words to English which is being interpreted, (Matthew 1:23, Mark 5:41, Mark 15:22, Mark 15:34, John 1:38, John 1:41, Acts 4:36); so also, there are translations of Yoruba words to English. There have been cases when the author cannot spell and fully comprehend what he heard. In such cases, and not dispose of the records, the author will partly enter what he heard. This impedance mismatch between what the speaker said and what the listener heard, rarely occurs with English words. But it is likely, in the author's native language, Yoruba, which exploits word combinations and phrases. The alphabets differ slightly between the English and Yoruba languages; Yoruba contains diacritic alphabets. The author requires a Yoruba dictionary and translator; a recent success is with the http://translate.google.com web page. The HisWord table's most important column, as the name suggests, is the word column, which is either English or Yoruba; or a mixture of both languages. The author will yield to the Holy Spirit in translating Yoruba words to English. From previous experience, this translation is not always the most right or relevant, and different words may contain the diacritic alphabets; therefore, introduce various meanings (1 Corinthians 12:30, 1 Corinthians 14). To account for the discrepancy in translation, the author sought help from the LORD: 2015-11-02T22:55:00 And, the merge, is the money, convert. 2015-11-03T02:17:00 The specifics, a language. The word column is a potential natural primary key, since duplicates are rare. When redundancies do occur, we may append the sequence to the word, to generate a unique word. We do this manually, but an insert trigger, will offer automation, and will cut the risk of primary key violation, which leads to gaps in the identity column and, loss of data. The HisWord's table, commentary column, contains implicit information. This communication is most likely non-verbal, and it is information such as creatures standing or moving towards particular locations or engaging in other visible activities. As such, from the creation account, on the first day, there is a commandment, and there may be an action/response. The commandment is in the word column God created light ( Genesis 1:3, 5 ). The action is in the commentary column; God separated the light from the darkness (Genesis 1:1-2, 4). Microsoft SQL Server generates sequential numbers for the HisWordID identity column. The goodness of this technique is that it is a candidate primary key, data loss is trackable, and it provides a sort key. The HisWordID column may serve as the primary and/or foreign key, the backbone of the Referential Integrity Constraint. The Dated column is of the DateTime type. If an insert statement does not explicitly specify a value for the dated column, then it defaults to the current date and time of the (UTC-08:00) Pacific Time (US & Canada) time zone. There is a preference for the Coordinated Universal Time (UTC) format. A relational constraint limit to a single foreign key? The author will choose either the most vivid or rare? HisWord_view The HisWord_view composes of the computed columns deducted from analyzing the Word. The two most significant computations are the AlphabetSequenceIndex, and the reliant AlphabetSequenceIndexScriptureReference, respectively. The author derives the AlphabetSequenceIndex from the word by adding the place of the alphabets in the alphabet set. In the ASCII table, the lower case alphabets are between 97 and 122, and the upper case alphabets are between 65 and 90. The lower and upper case alphabets have the same places. The AlphabetSequenceIndexScriptureReference is the books, chapters, verses separation in the scripture. The author will consider the chapter and verse place, forward and backward. Use the AlphabetSequence.html to calculate the computed values identified above. The AlphabetSequence is like Gematria, Mispar Hechrachi method. Titles of God. The Remember Table The Remember table tries to correlate the period between a prophecy and its fulfillment. " The terminus a quo DatedFrom is when the prophecy begins, and it marks the the date of issue or establishing of the prophecy. The terminus ad quem DatedUntil is when a prophecy partially or entirely comes to pass. " (Koinonia House). DateDifference.aspx is for calculating the difference between terminus a quo, versus terminus ad quem; the results are in days; biblical years, months, days; the Common Era. The inspiration for adding the Common Era comes from wikipedia.org by Jimmy Wales. To determine the HisWord and Remember entries? The author chooses to separate the particular and prompted inputs ( Luke 4:19 ). APass First, inside and last dates. ActToGod This is subjective work; the author applys intelligence to find patterns and resemblances in the Bible. Scales & Measurements Type of Scale Commentary Example of Scale Nominal Scales The numbers may serve as tags or labels which are quantitative with no values. Introduced on July 1, 1963, the ZIP Code system (an acronym for Zone Improvement Plan) traditionally contained five digits. In 1983, an ex