Jump to ContentJump to Main Navigation
Aksum and NubiaWarfare, Commerce, and Political Fictions in Ancient Northeast Africa$
Users without a subscription are not able to see the full content.

George Hatke

Print publication date: 2013

Print ISBN-13: 9780814760666

Published to NYU Press Scholarship Online: March 2016

DOI: 10.18574/nyu/9780814760666.001.0001

Show Summary Details

Conclusion

Conclusion

Chapter:
(p.167) 6. Conclusion
Source:
Aksum and Nubia
Author(s):

George Hatke

Publisher:
NYU Press
DOI:10.18574/nyu/9780814760666.003.0006

This book has explored the history of Aksumite–Nubian relations based on the available archaeological, epigraphic, and literary evidence. For the period before the rise of Aksum, there is good evidence of commercial and even political contact between Nubia and the Horn of Africa. By the turn of the first millennium BCE, however, the two regions seem to have gravitated toward two different axes: a Nile Valley axis in the case of Nubia and an Ethiopian Highlands–Red Sea axis in the case of Ethiopia. Thus for the Nubian kingdom of Kush, the most obvious point of contact with the outside world was Egypt. The book concludes by raising three important points. First, ancient Northeast Africa was not an integrated region politically, economically, or culturally. Second, political fictions played an important role in Aksumite royal ideology. Third, it is not clear whether Aksum's invasions of Nubia in the fourth century were the end result of strained political relations between them.

Keywords:   political contact, Nubia, Ethiopia, Kush, Egypt, Northeast Africa, political fiction, Aksum, invasion, political relations

NYU Press Scholarship Online requires a subscription or purchase to access the full text of books within the service. Public users can however freely search the site and view the abstracts and keywords for each book and chapter.

Please, subscribe or login to access full text content.

If you think you should have access to this title, please contact your librarian.

To troubleshoot, please check our FAQs, and if you can't find the answer there, please contact us.