Shishaq

From Wikipedia, the free encyclopedia

(Redirected from Shishak)
Jump to: navigation, search

Shishak (Hebrew: שישק, Tiberian: [ʃiʃaq]) or Shishaq (=striker[citation needed]) is the biblical Hebrew form of the first ancient Egyptian name of a pharaoh mentioned in the Bible.

Contents

In the very early years after the decipherment of Egyptian hieroglyphs, on chronological, historical, and linguistic grounds, nearly all Egyptologists identified Shishaq with Shoshenq I. This position was maintained by most scholars ever since, and is still the majority position.

However, the Egyptologist David Rohl, controversially proposed a massive revision of the traditional chronology of the ancient Near East, and attempted to identify Shishaq with Ramesses II. A few scholars, such as Peter James, who accept Rohl's criticism of identifying Shishaq with Shoshenq I while not his other theories, have sought to identify Shishaq with one of the other Ramesseses of this period with varying success. The so-called "James" chronology was first developed by Michael Sanders [1] and published in "Catastrophism and Ancient History" [2] in 1985 many years before James published his revision.

David Rohl, and other followers of the New Chronology, assert that the identification of Shishaq as Shoshenq I is based solely on a reading made by Jean-François Champollion of the text of Shoshenq’s Triumphal Relief near the Bubastite Portal of the temple of Karnak at Thebes. There, in a list of cities Shoshenq I had boasted he conquered, Champollion had read the 29th city from the list as y-w-d-h-m-r-k. He then surmised that this could mean Yhuda Malkhut (Hebrew: יְהוּדָה מַלְכוּת, Tiberian: [jəhuðɔh malxuθ]), that is, "Judah Kingdom" — an unlikely Hebrew phrase, Malkhut Yhuda would be more natural — and concluded this list referred to the biblical Shishaq's invasion of Judah. However, Max Müller (building on a related proposal by Heinrich Brugsch) later showed that y-w-d-h-m-r-k (yud-he-merek) should be read in Hebrew as Yad Ha-Melekh (יַדְ־הַמֶּלֶך, Tiberian: [jað hamːɛlɛx] meaning "Monument (lit. "hand") of the King", to the king of Judah.

Further, much controversy has resulted because from the list of cities in this inscription it appears that the target of Shoshenq's campaign was not the heartland of the kingdom of Judah (which is what the Bible seems to imply), but the northern cities that became the kingdom of Israel. Many of the cities listed are known today and their order clearly indicates the progression of a military campaign. The conquest of Jerusalem would have been given pride of place, not buried between two insignificant hill-towns hundreds of miles away. It could be Shoshenq only listed the cities he either destroyed, or whose garrisons he defeated in support of the break-away kingdom of Israel. It may be, however, that the text only lists cities that the Egyptians regarded as under their political control, and so not intended to be read as an itinerary or list of directly conquered cities at all, which would be in line with similar lists from elsewhere in Egypt.

Rohl further argued that Shishaq does not properly equate to how the Egyptian name Shoshenq would have been spelled by the contemporary Hebrews, and put forth his own identification of Shishaq with Ramesses II, based on the hypocoristic form sysw which he claimed was used to refer to Ramesses and abused by the Hebrews into sysq (which Rohl claims is a pun on verbal root שׁקק šqq, the Hebrew word for "to attack, fall upon, storm").

In order for the name Shishaq to be read as Shoshenq, the "n" must be dropped—which automatically happens in Biblical Hebrew before a consonant—but for it to agree with sysw, a "q" must be added, which does not correspond to any known phonological rule in Biblical Hebrew other than puns, which are a bit more rare than Rohl seems to suggest. In Northwest Semitic languages (such as Hebrew) /š/ is usually used to record Egyptian /š/ and rarely /s/ after a certain point (as would be the case for sysw), though it has been shown, by Édouard Naville, that it was used in a number of cases, such as in Goshen, which derives from the Egyptian gsm.[1] This does not hold for East Semitic languages such as Akkadian, where confusion between /s/ and /š/ is evident. Rohl seems to suggest in his thesis that any "Semitic" evidence (such as Akkadian) will support his theory with very little caution.[2]. Though Akkadian was used quite often throughout many ancient empires in correspondence, for this to be fully supported, one would probably need to assume his New Chronology is correct.

In response to Rohl's theory, Egyptologists such as Kenneth Kitchen have pointed out that no other known king of Egypt fits the identification as well as Shoshenq I. Setting the reign of Ramesses II three centuries later would not only cause complications with the date of the Battle of Qadesh, it would also conflict with the chronology of Hittite history and with the very solid chronology of Assyrian history.

He is best known for his campaign through Palestine, as recorded in the Bible (1 Kings 11:40; 14:25; 2 Chronicles 12:2-9). Shishaq had provided refuge to Jeroboam during the later years of Solomon's reign, and upon Solomon's death, Jeroboam became king of the breakaway tribes in the north, which became the kingdom of Israel. In the fifth year of Rehoboam's reign (commonly dated between 926 and 917 BC), Shishaq swept through the kingdom of Judah with a powerful army, in support of his ally. According to 2 Chronicles, he was supported by "the Lubim, the Sukkiim, and the Ethiopians." Shishaq captured a number of cities of that kingdom, including Jerusalem, where he pillaged the temple and the royal palace, and carried away the shields of gold which Solomon had made. Although Judah was humbled, hostilities still continued between the two kingdoms; yet this was the only recorded intervention of a third party into the affairs of these two kingdoms during Rehoboam's reign.

Texts written in various ancient languages seem to indicate that the first vowel was both long and round, and the final vowel was short. For example, the name is written in the Hebrew Bible as שישק [ʃi:ʃaq]. The variant readings in Hebrew, which are due to confusion between the letters < י > Yod and < ו > Vav that are particularly common in the Masoretic Text, indicate that the first vowel was long and received emphasis in pronunciation. The Septuagint uses Σουσακιμ [susakim], derived from the marginal reading שושק [ʃu:ʃaq] of Hebrew. This indicates during the 2nd century BC Hebrew-speakers or Alexandrian Greek-speakers pronounced the name with an initial long close back rounded vowel [u].

  1. ^ Muchiki 1999:315.
  2. ^ Rohl 1995:162

  • Muchiki Yoshiyuki (1999). Egyptian Proper Names and Loanwords in North-West Semitic. Atlanta: Society of Biblical Literature. 
  • Rohl, David M. (1995). Pharaohs and Kings: A Biblical Quest. New York: Crown Publishers, inc.. 
Advanced Search
Included Web Search Engines


Safe Search

close

Top Matching Results

Occasionally Search.com will highlight specialized results that are based on the context of your query. Examples of specialized results include specific links to news, images, or video.

Top Matching Results may highlight information from other Search.com pages, content from the CNET Network of sites, or third party content. The listings are based purely on relevance. Search.com does not receive payment for listings in this section but our partners that provide this data may get paid for listing these products.

Sponsored Links

This section contains paid listings which have been purchased by companies that want to have their sites appear for specific search terms and related content. These listings are administered, sorted and maintained by a third party and are not endorsed by Search.com.

Search Results

Search.com sends your search query to several search engines at one time and integrates the results into one list which has been sorted by relevance using Search.com's proprietary algorithm. You can customize the list of search engines included in your metasearch from the preferences.

The search engines that are used in your metasearch may allow companies to pay to have their Web sites included within the results. To view the Paid Inclusion policy for a specific search engine, please visit their Web site. Search.com does not accept payment or share revenue with any search engine partner for listings in this section.