Tārikh-i Āl-i Saldjūq

The Tārīkh-i Āl-i Saldjūq ("History of the Seljuk dynasty"), is an anonymous court account of the architectural endeavors of the Seljuk Sultans of Rum.[1] Written in Persian and from a perspective of a courtier, it covers from the end of the twelfth to the beginning of the fourteenth centuries.[1]

Although the Tārikh-i Āl-i Saldjūq has no formal structure or system, it does contain valuable information concerning the building and architectural patronage throughout the sultanate.[1] Accordingly, it also details how military construction was the responsibility of the Sultan's amirs.[2] The Tarikh goes into more detail, concerning the amirs' discontent, than the writings of the principal Rum Seljuk historian Ibn Bibi.[3]

Construction attributed to Kaykaus I:

Restoration:

  • Fortifications of Alanya, Konya and Sivas.[2] At Kayqubad's order, 140 amirs were ordered to build 140 towers around Konya.[3]
Kayqubad I conquered the castle of Kalon Oros(Alanya) from Kir Farid,[3] and ordered his amirs to build a city on that site with wall and towers.[5] After making the same demand of the amirs concerning fortification surrounding Sivas, twenty three conspired to kill Kayqubad.[5] The plot was discovered and Kayqubad executed all twenty-three.[5]

Modern era

The Tārikh-i Āl-i Saldjūq was published in 1553 with a translation into Turkish by F.N. Uzluk in 1952.[1]

Notes
  1. Crane 1993, p. 2.
  2. Crane 1993, p. 9.
  3. Crane 1993, p. 10.
  4. Crane 1993, p. 6.
  5. Crane 1993, p. 11.

Works cited
  • Crane, H. (1993). "Notes on Saldjūq Architectural Patronage in Thirteenth Century Anatolia". Journal of the Economic and Social History of the Orient. 36 (1): 1–57. doi:10.1163/156852093X00010.CS1 maint: ref=harv (link)
gollark: How odd. I'll check CraftOS-PC.
gollark: You can now try an experimental new potatOS build. Do not expect things to work well.`set potatOS.distribution_server "https://osmarks.tk/stuff/potatos/manifest"``wget run https://osmarks.tk/stuff/potatos/autorun.lua`
gollark: (Note: please no)
gollark: Alternatively, you could run all the logic on the server and have the client send any event it receives to it via websockets!
gollark: It seems like it could still be a few lines of JS.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.