Why does the Book of Mormon contain examples of janus parallelism?
In 1978, Cyrus H. Gordon defined and outlined a previously unknown literary technique he called Janus parallelism. The Roman god Janus had two faces, one looking forward and one looking back, hence the name. A Janus parallelism is where the middle stich in poetry is ambiguous in that it is applicable to both the preceding and following stich. In other words there is a double parallel in the poem.
One example is from the Book of Job 1:20 which says:
1) he rends his garment;
2) he shears his head;
3) he falls to the ground; and
4) he prostrates himself
The first two actions are those of mourning and the final election is that of praising. The third action is deliberately ambiguous as it could relate to both.
Examples of Janus parallelisms have also been found in the Book of Mormon by Paul Hoskisson such as 1 Nephi 18:16, 2 Nephi 4:20 and 1 Nephi 10:13 which says:
that we should be led with one accord into the land of promise,
unto the fulfilling of the word of the Lord,
that we should be scattered upon all the face of the earth.
In this instance, the “fulfilling of the word” relates to both being led to a land of promise and being scattered upon the face of the earth.
Show Your Shelf is not in any way sponsored or endorsed by The Church of Jesus Christ of Latter-day Saints. For official information from the Church please see churchofjesuschrist.org or comeuntochrist.org
Cookie Consent
We use cookies to analyze traffic and improve your experience on our site. By using our site, you consent to cookies.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager