Scripture taken from the Holy Bible, NEW INTERNATIONAL VERSION®, NIV® Copyright © 1973, 1978, 1984, 2011 by Biblica, Inc.® Used by permission. All rights reserved worldwide.
Detailed Part 3a · Full supporting tables · 6 October 2026 · v2
These tables accompany Solomon’s Temple and Prophetic Time. They preserve the original study’s symbolic date model alongside the ordinary Temple chronology. The short introduction and its compact appendix remain the accessible starting point.
The arithmetic below is exact once its displayed operands are selected. An exact result does not by itself establish a historical calendar, a prophetic event assignment or a particular theological interpretation. The novel Temple projections remain part of this study even where the Canon has not adopted them.
Direct tables: Counting rules · Five datums · Calendar phase · Historical links · Christ comparisons · Four-datum matrix · Parallel strips · Cross-table relations · Bookends · Jared/Cainan · 1260 gain · Anniversaries · Boundary proposals · Interpretation.
1. Numbered days, elapsed intervals and signed coordinates
The Temple table begins from numbered day 32, the second day of the second thirty-day month. Its primary numbered-day operator is:
n = 30 × (month − 1) + day.
For month 2, day 2, n = 32. From the beginning of month 1, day 1, 31 complete days have elapsed. That second operation is e = n − 1. The original Temple projection deliberately promotes the numbered label n to its symbolic coordinate. The Ezekiel matrix separately derives an elapsed point from a Julian-day scalar. These are named operations, not an unnoticed one-day change to a single operation.
The archive’s broad rule selects the New Year preceding or associated with an event, with a near-New-Year exception for the Jeconiah exile epoch. The selected Temple-Tishri row also uses a retrospective direction: its autumn datum lies later than the spring foundation in the same displayed Nisan year. A preceding autumn would instead produce a different, positive coordinate. The methodology explains the wider datum engine; its elapsed-point rules do not automatically erase the Temple table’s explicitly numbered-day construction.
Crossing BC and AD does not itself invoke the Mirror. No central Temple comparison here reflects a date through an axis or reverses a phase suffix. Files 00 §3.9 and 09 Appendix A control those distinct operations. Likewise a balanced interval such as 2150 + 2150 is a bisection; it does not become a formal Mirror merely because its ends lie on opposite sides of BC/AD.
2. The complete five-datum table
Begin with the source’s AD 25–32 envelope. Its five offsets are −180, 0, 1110, 1290 and 1470. Add the offset to both boundaries, then add the chosen 2730 construction register to obtain the completion envelope.
2730 = 2700 + 30 = 7 × 390. Each matching start/completion boundary in all five rows preserves that span, including the civil crossing in T1. See Figure 6.
The source’s phrase “fourth year” offers the three-completed-years-plus-current-year selection; four completed years is a different cardinal selection. Both source rows are retained. Their coordinate arithmetic is not evidence that each represents the same physical accession date.
There is also a 364-day product, 7.5 × 364 = 2730, and a priestly product, 7.5 × 336 = 2520. Those are calendar comparisons. Equality of the first number with 2700 + 30 does not make a 364-day year and a 360-day year with an insertion the same calendar. The reader’s construction section retains all three registers.
3. Which leap months are being counted?
The reconstructed calendar is fixed to the 1446n Exodus phase. The block 1006n→966n BC closes six six-year units and a four-year unit at:
1000, 994, 988, 982, 976, 970 and 966n BC.
The next block closes at 960, 954, 948, 942, 936, 930 and 926n BC. A close inserts thirty days before the following cycle begins. The opening boundary’s previous insertion must not be counted twice. These are the same arithmetic rules used for the 606n Ezekiel cycle, not a newly attested ancient leap-month list. File 12 §7A controls the reconstructed scheme.
The 1110 row follows the source’s 1470 − 360 = 1110 = 1080 + 30 transfer and is therefore a declared 1080 + 30 source register, not the unique physical count of every leap month between the stated 970 and 967 boundaries. The author’s earlier ordinal alternative transfers the thirty-day component along with the symbolic row. Naming that selection preserves its argument without silently redating an insertion.
Similarly, 2730 is the selected one-insertion construction register throughout the five-row model. If 967 is merely an adjacent ordinal representation, it need not open an independently shifted physical window; if it does open such a window, the table above shows that two closes can fall inside it. An omitted-insertion register can still retain 2700. A counted register may have 2730 or 2760, depending on phase and selection. The source alternatives are not discarded because those rules offer more than one legitimate count.
The corresponding seven-year Ezekiel base is 2520. General zero/one/two-insertion comparisons give 2520/2550/2580. The specific Tammuz call→Av Temple window is different: 2520 + 30 ordinary month + 30 counted leap month = 2580. It is not evidence for two leap months in that particular call-to-Av interval.
The chosen 2730 call-to-refugee register is 2700 + 30, while the omitted-insertion register is 2700. The original month/day headings, Julian-day scalar, common week start and exact narrated day are kept separately in the shared charts. Optional inclusion of an insertion is a choice of calculation register; it does not change the declared cycle phase.
4. Ordinary and schematic anchors meeting the symbolic rows
The foundation itself remains 966 BC in the ordinary cardinal display and 967 in the selected ordinal display. The 1016 node is a schematic Kings-ledger position; it does not change the historical foundation. Nor does a +50 schematic route replace the historical restoration reference of 536 BC. See Files 08, 18, 19 §§10.4–10.6 and the reader’s original reign ledger.
The two later accession-row steps are 1135→1315→1495 = 180 + 180. Their sixfold units are 430→460→490, increasing by thirty each time. For the middle unit, 460 = 20 × 23; 2300 = 5 × 460. Its sixfold span yields 2800 by 70/69 or 3000 by 25/23. Those are alternative outputs with gains of forty and 240, respectively.
5. Completion rows transferred to Christ’s birth and ministry comparison
The source compares the symbolic completion rows with the Creation-linked birth envelope 6 BC→AD 2 and the AD 25 conception-count ministry node. Seven elapsed years separate the matching birth-envelope boundaries, just as seven separate each Temple envelope’s endpoints.
Each row uses corresponding boundaries; it does not mix the beginning of one envelope with the end of another. The thirty-year difference between 6 BC and AD 25 supplies the paired contrast. AD 1315–1322→AD 25–32 separately gives 1290 at both matching ends.
I interpret the transfer from Exodus/Tabernacle beginnings to Christ through the Temple’s bodily meaning in John 2:19–21. The Temple-start and completion columns form related comparisons with birth, ministry and atonement; the arithmetic is not a new historical dating of Jesus’ death. File 13 controls the permitted AD 25 conception-count comparison and AD 27 ministry target, while retaining preferred AD 33n and possible AD 30n Passion states. The original’s broad identification of AD 25–32 with the complete historical ministry and crucifixion is narrowed accordingly.
6. The four-datum Ezekiel matrix used by the Temple comparison
The preserved Exile edition has 18 rows and four datum columns, or 72 supplied coordinate cells. Datum scalars are A = 1503251.5; B = 1503431.5; C = 1507271.5; D = 1507451.5. For the same event, the projected coordinates are linked by fixed offsets: q_A − q_B = 180; q_A − q_C = 4020; q_B − q_D = 4020; q_C − q_D = 180. These are differences between event coordinates; the datum scalars themselves have the opposite subtraction order.
Download the complete Exile CSV · Machine-readable source and computed points (JSON, ZIP). The shared chart page supplies the wider data context. The separate Return edition is also included as CSV and JSON (ZIP); it does not replace the Exile edition used in these Temple equations.
The Return download preserves two source-only sign slips in column A: its Nisan-datum row prints −210 where the supplied Julian-day difference is +210, and its final Tishri-datum row prints −4050 where the difference is +4050. The JSON displays both raw and computed values; these two Return cells are not inputs to the Temple equations.
The raw display retains its original date labels, alternatives, braces and asterisks. The JSON also retains each exact Julian-day difference and its selected whole-day coordinate. Thus a source value such as B = 4145 can be a floor of 4145.25, rather than the exact narrated Temple-destruction day. A containing week is a shared unit, not a claim that the ninth, seventh and tenth dates in different biblical narratives are all literally the fifth. The source’s visible “5th–12th” and “15th–22nd” windows require seven elapsed intervals; their endpoint labels can number eight when both are included.
The original’s six-month/day15 completion label contains a parenthetical “12th” slip. The active explanation uses the established 15th–22nd containing window, while the raw matrix and archive preserve what was printed. Siege and fall dates described as alternative years remain labeled alternatives. They do not silently change the regular canonical anchors of 588/586 BC.
7. Two 2730 strips offset by 2300
For the first row: 2456 − 156 = 2300; 2449 − 149 = 2300; 2575 − 275 = 2300; 2582 − 282 = 2300. Its two strips each cross the civil boundary: 2456 + 275 − 1 = 2730 and 156 + 2575 − 1 = 2730. The second row gives the same equalities with its shifted operands. See Figure 7.
In the chart, the call’s D coordinate −2455 renders as 2456 BC and C coordinate −2275 as 2276 BC. They are symbolic renderings of chart coordinates, not claims that Ezekiel historically lived in those BC years. The seven-interval source envelope is attached to call and refugee alike.
The inner partition gives 2730 = 430 + 2300. From the call’s selected start point, the enacted 430 ends before the refugee by 2300 in this counted register. File 17 §13A.4 supplies that partition. Daniel’s 2300 evenings and mornings (Daniel 8:14) supplies the sanctuary-restoration association; the Temple cross-table rectangle is this study’s further model interpretation, not an equation explicitly stated by Daniel.
Ezekiel’s restricted and reopened speech provides the narrative bookends: the overwhelmed seven days precede his commission; the speech restriction follows; later God relates the refugee’s arrival to the opening of his mouth, and Ezekiel records its opening before the refugee arrives (3:15, 26–27; 24:25–27; 33:21–22). This is the reason for carrying a seven-year envelope through both symbolic strips. It does not relocate every narrated speech episode onto one exact day.
8. The 430/860 family and its translations
The last two third points are derived translations, not additional narrated events. They display the original assertion that adding 2730 to both sides carries the same relation to the strip ends. The narrower directly supplied 430 relation is 1135→1565 = 3865→4295 = 430. The further 860 relation is 1135→1995 = 3865→4725 = 860. A common translation keeps a span fixed; it does not manufacture independent evidence.
Two Temple row differences also give 1290: 156 BC→AD 1135 and AD 25→AD 1315. The ordinary historical Egypt-entry→Temple-fall span is 1876 − 586 = 1290. Those equalities motivate comparing the structures, while their event and coordinate classes remain different.
The original says the call→dated siege start→Temple fall divides into 1290 + 1290. Its total is indeed 2580, but its printed siege rows do not occupy the equal-half point:
The A columns give the same partitions after adding 180. 2855 is a derived midpoint, not a supplied literal siege date. The intended two-half form is retained as a structural bisection. The source’s assignment of its center to the historical siege is corrected; no cell is silently moved. File 17’s separately dated call-to-siege calculation has its own premises and must not be substituted without opening that frame.
9. Equal halves, 430 cycles and the theological transfer
The first two are matching seasonal symbolic families. AD 1995/2175 represent the completed enacted siege; AD 4145/4325 represent the chart’s selected boundary for the historical Temple’s destruction. “Historical” describes the event represented, not a literal destruction in the symbolic AD year. The third comparison joins historical Egypt entry to the symbolic construction and destruction points. 3010 = 7 × 430, with the final AD 4146 typo corrected to 4145. Figure 9 illustrates both centers.
The spine that explains the transfer is 2091→1876→1446→1016→586→156 BC. Its first interval is 215; the following four are 430 each. Another 430 after 156 BC reaches AD 275 under civil counting. The 1876 nexus identifies the ordinary Egyptian sojourn; 2091 names Abraham’s Haran-to-Canaan call, and 1016 names the schematic Temple pivot. None is interchangeable with a differently selected departure, foundation or datum merely because a nearby number is useful.
The source advances the Solomon and Ezekiel symbolic tables together by 180. This preserves their separations and carries the Temple-Tishri foundation 156–149 BC to the Temple-Nisan AD 25–32 envelope. I interpret the transfer as a relation between Ezekiel’s enacted bearing of Israel and Judah’s iniquity and Christ’s atonement. The 430 structure persists while its symbolic sanctuary point shifts. This is the positive theological reason for the seasonal translation, not a free adjustment made after finding an attractive total.
The two 3010 halves also recall the two sevens of Joseph’s plenty and famine. Jacob’s Egypt entry comes during the famine, two years into it (Genesis 45:6); the comparison does not put his entry at the first day of both fourteen years. The narrative association concerns the sevenfold form, not an equation of those fourteen ordinary years with 6020 historical years.
10. The cumulative Creation span and two seven-year bookends
Select the close of the actual cumulative MT Adam envelope 14011–14004 BC and the beginning of the accession-Tishri symbolic envelope AD 1315–1322. Their inner span is:
14004 + 1315 − 1 = 15318 = 666 × 23 = 222 × 69.
The seven-year bookends are added after expansion of the inner span. Expanding the entire 15332 would be a different calculation. The two numeric halves 7777 + 7777 do not by themselves establish a dated historical center for the expanded interval.
The original repeatedly prints 14021–14004 while describing a seven-year envelope. That range spans seventeen. Files 09 and 18 supply 14011–14004 for the actual cumulative MT envelope. The active calculation corrects that transcription explicitly; the archive remains unchanged. No Rounded 14006 coordinate is silently substituted into this actual cumulative calculation.
I interpret the change from 666 to the paired sevens as an image of redemption. Revelation 13:18 explicitly supplies 666; the perfection reading of 7770/7777 is this study’s numerical interpretation. The ratio’s exact effect remains visible without making the symbolism a mathematical definition. Figure 10 separates this operation from Cainan’s variant.
11. Jared’s 460 interval, cubic sixes and restored Cainan
The original’s 4768 is corrected to 4968. The increase to 5040 is 72, while the smaller 1656 increases by 24 to 1680. The threefold input relationship, 4968 = 3 × 1656, survives either ratio. The original associates 72 with nations; that is a symbolic association, not an exclusive meaning or a claim that every ancient textual tradition counts the nations identically.
6³ = 216; 7³ = 343. Neither is the decimal number 666 or 777. The source juxtaposes the written repeated digits with cubic repeated factors as related imagery; the active explanation keeps their values distinct. 5400 = (7.5 + 7.5) × 360 and 5040 = (7 + 7) × 360 supply two doubled construction/sevenfold forms.
Regular Jared’s birth, 3654 BC, is 460 after Creation 4114 BC. 1 Enoch 6:6 places the Watchers’ descent in Jared’s days; it does not supply an exact BC date for that descent on his birthday. The chapter’s Semyaza and oath setting provide the literary association.
The restored-Cainan operation adds 460 = 130 + 330 to cumulative lifespan stacking. The Greek Genesis inputs are separately accessible in Brenton Genesis 11, while Luke 3:35–36 names second Cainan without supplying that lifespan. MT and SP Genesis omit him. A regular restored begetting chain adds 130; cumulative restoration adds 460; native LXX chronology already containing him must not insert him again. File 18 controls these states.
This cumulative variant changes 14004→14464 BC and 15318→15778. Its 25/23 result is 17150 = 35 × 490 = 50 × 7³. The original AI response incorrectly divides the final cubic expression by two; (50 × 7³)/2 = 8575, not 17150. The author’s correct 17150 expression is retained.
Jubilees 8:1–4 connects Cainan with discovering and copying the Watchers’ teaching. That extra-biblical story supports the source’s contrast between forbidden learning and redemption; it does not authorize confusing the two chronological insertion rules. The source says “the Gospels” broadly; the explicit Gospel witness to this name is Luke.
12. The 1260 gained by a separate 460-length displacement
The source gives another equation:
14004 + 460 = 14464; 14464 BC→AD 27 = 14490 = 630 × 23.
14490 × 25/23 = 15750; 15750 − 14490 = 1260.
It calls the added 460 “Jared’s.” That can identify the regular Creation-to-Jared interval, 4114 − 3654 = 460, used here as an analogical displacement of a cumulative coordinate. It is not Jared’s lifespan. The cumulative Cainan insertion reaches the same scalar head, but uses a different operand identity and rationale. Both associations are preserved; they are not silently merged.
AD 27 is the selected ministry/baptism comparison target supported in File 13, not an exact date supplied in Luke’s age notice alone. The source interprets the 1260 gain in connection with Revelation 12’s child and ascension setting and the woman’s wilderness protection. The 1260 days are explicitly assigned to the woman’s care in verse 6; their numerical resemblance does not make them a stated duration of the child’s ascension.
13. Daniel’s three weeks and the Temple foundation anniversary
Daniel 10 supplies three full weeks and an appearance on the first month’s twenty-fourth day. The source reconstructs a start at the end of the third day / beginning of the fourth. With a thirty-day month, its selected sequence is:
The source associates its Nisan 4 beginning with the Enochian Wednesday/fourth-Creation-day New Year. That is a comparison between calendrical structures; Nisan 4 is not automatically the New Year’s first day in the other register. Its connection belongs with the explicitly named 364-day calendar framework, not a silent conversion of the Temple’s 360-day month grid.
The three weekly blocks meet the restoration Temple’s Passover celebration after its completion in Adar (Ezra 6:15, 19–22). I read the interlocking anniversaries as the day-scale counterpart of the larger restoration comparisons. Their theological meaning does not turn an unstated Ezra foundation day or a selected Red Sea anniversary into explicit Scripture.
Daniel 9’s first-year Darius setting and Daniel 10’s third-year Cyrus setting remain distinct (Daniel 9:1; 10:1–4). This study can compare their numbers without assigning both chapters one convenient foundation date.
14. Restoration restarts and proposed sanctuary boundaries
The controlled restoration chain is 586→537→516 BC = 49 + 21 = 70. Its ordinary adjacent foundation display uses 536, giving 50 + 20, also seventy, when the fall and completion anchors stay fixed. The source adds a forward continuation:
537→516→467 BC = 21 + 49 = 70.
The original also supplies the adjacent-label alternative 536→515→466 BC = 21 + 49 = 70. Its 515 completion label is a retained source alternative; it does not replace the ordinary canonical completion in 516 BC. With the ordinary 536 foundation and 516 completion kept together, the span is twenty, not twenty-one. The original 537/536→516/515 pairs are therefore shown as paired alternatives, not freely interchangeable single nodes.
It also compares 1446→466 BC = 980 = 490 + 490. Those terminal labels differ: 1446 − 467 = 979. Both proposed rows are retained with their actual arithmetic. The 467 continuation cannot be called the 466 Exodus endpoint without an explicitly selected adjacent-state adjustment.
I interpret the reversed 49/21 divisions as a pattern capable of continuing through human resistance and renewed decrees. The source reads Cyrus’s authorization followed by three further restoration authorizations as related restarts. File 17 §7.5 distinguishes Cyrus’s Temple authorization, Darius’s confirmation, Artaxerxes’s Ezra/Law authorization and Artaxerxes’s Nehemiah/wall authorization. Their textual settings extend beyond Ezra 4–6: see Ezra 1, 6, 7 and Nehemiah 2. The source’s decree-restart reading preserves continuity of the prophetic pattern amid human failings; it does not identify all royal acts as one historical decree or replace Daniel 9’s text with a reconstructed event sequence.
The intended sanctuary-start/completion symmetry is also retained:
The older study says “or very near” when introducing its completion symmetry. Preserving that proposal with its unresolved boundary is more faithful than either suppressing it or presenting the one-year adjustment as already established. Files 63 and 64 develop related sanctuary structures, but their separate controlled endpoints do not automatically validate this old construction.
The Jacob endpoint and the 5980 scalar
The original combines three descriptions that do not agree: Jacob’s death in 1859 BC, a position 483 before the Exodus, and a 5980 span to AD 4052.
Current File 63 §7.3 identifies 1929 BC as Jacob’s age-77 Bethel/Haran call, while 1859 remains his death. The 5980 comparison can therefore be reconstructed with a controlled call coordinate, but it must be introduced as that corrected comparison, not silently relabeled “Jacob’s death.” The transcript’s original intended biographical identification remains historically documented in the archive.
15. Fall, sanctuary and redemption: the preserved interpretation
The numerical argument is deliberately theological. I connect the Temple’s body symbolism with a broader reading of Creation, the Watchers, Revelation and Christ’s atonement. The source’s two major rebellion images are Adam’s fall and the Watchers’ descent in Jared’s days. Their selected spans to the symbolic AD 1315 node yield 666 × 23 and 6³ × 23, respectively. The associated Key operations convert them to related sevens, construction quantities and prophetic periods.
Revelation 12 provides the literary setting: a woman and ancient serpent recall Eden; the swept-down stars invite comparison with fallen angels; the male child and throne point to Christ; and the woman’s wilderness care supplies 1260. Revelation 13 then names 666. These connections are interpretive correspondences. Genesis does not itself name Enoch’s Watchers, and Revelation does not date them to Jared’s birthday.
Revelation 12:1–17 — preserved NIV2011 quotation
Read Revelation 12 in the New International Version. Scripture text is presented separately from the study’s interpretation.
1A great sign appeared in heaven: a woman clothed with the sun, with the moon under her feet and a crown of twelve stars on her head.
2She was pregnant and cried out in pain as she was about to give birth.
3Then another sign appeared in heaven: an enormous red dragon with seven heads and ten horns and seven crowns on its heads.
4Its tail swept a third of the stars out of the sky and flung them to the earth. The dragon stood in front of the woman who was about to give birth, so that it might devour her child the moment he was born.
5She gave birth to a son, a male child, who “will rule all the nations with an iron scepter.” And her child was snatched up to God and to his throne.
6The woman fled into the wilderness to a place prepared for her by God, where she might be taken care of for 1,260 days.
7Then war broke out in heaven. Michael and his angels fought against the dragon, and the dragon and his angels fought back.
8But he was not strong enough, and they lost their place in heaven.
9The great dragon was hurled down—that ancient serpent called the devil, or Satan, who leads the whole world astray. He was hurled to the earth, and his angels with him.
10Then I heard a loud voice in heaven say: “Now have come the salvation and the power and the kingdom of our God, and the authority of his Messiah. For the accuser of our brothers and sisters, who accuses them before our God day and night, has been hurled down.
11They triumphed over him by the blood of the Lamb and by the word of their testimony; they did not love their lives so much as to shrink from death.
12Therefore rejoice, you heavens and you who dwell in them! But woe to the earth and the sea, because the devil has gone down to you! He is filled with fury, because he knows that his time is short.”
13When the dragon saw that he had been hurled to the earth, he pursued the woman who had given birth to the male child.
14The woman was given the two wings of a great eagle, so that she might fly to the place prepared for her in the wilderness, where she would be taken care of for a time, times and half a time, out of the serpent’s reach.
15Then from his mouth the serpent spewed water like a river, to overtake the woman and sweep her away with the torrent.
16But the earth helped the woman by opening its mouth and swallowing the river that the dragon had spewed out of his mouth.
17Then the dragon was enraged at the woman and went off to wage war against the rest of her offspring—those who keep God’s commands and hold fast their testimony about Jesus.
This reading is “fractal” in the source’s explanatory sense: related themes and proportions recur on more than one chronological scale. The term here is an analogy for self-similarity, not a demonstration of a formal mathematical fractal with a proved dimension. The ordinary years establish the large structure; day-based symbolic coordinates explore its finer relationships. Arithmetic and narrative jointly serve the proposed interpretation.
I also retain the source’s aim of allowing several theological perspectives to recognize related aspects of the same Christ-centered pattern. A passage can speak to more than one scale without requiring every proposed fulfillment to be simultaneous or every eschatological interpretation to agree in detail. Unity is an interpretive purpose; it is not a statistical conclusion from the numbers.
The numerical transformation from sixes to sevens is read as redemption and reversal of the curse, particularly beside the Temple’s body and Ezekiel’s sign of bearing iniquity. The 1260 gained by the 14490 expansion connects with the same Revelation setting. These are the original study’s own arguments. They are preserved here without modifying the separate protected Revelation or palindrome series.
16. Related Temple material and source controls
The separately titled Solomon’s Temple as Chronological Template is a related study, despite its historical “Part 5” label. It is distinct from the Birth-of-Jesus Part 5 series. Its broader treatment includes day-32 construction, Creation/Adam offsets, MT–LXX–SP comparisons and additional numeric transformations. Those arguments retain their own premises and evidence; this Part 3a does not claim to replace that entire companion.
The Temple comparison here preserves its own twenty-eight substantive families rather than sending the reader to a different example as a substitute. Shared Exile/Return data and definitions are written once in the series foundations and supplied as machine-readable tables. The five ordinary supporting tables in the main reader remain intact.
No Canon or control file is changed by preserving these novel model developments. The quoted/scalar source corrections are documented in the publication record, with the original retained unchanged. Return to the detailed reader, introductory article, or original version.
Scripture taken from the Holy Bible, NEW INTERNATIONAL VERSION®, NIV® Copyright © 1973, 1978, 1984, 2011 by Biblica, Inc.® Used by permission. All rights reserved worldwide.