10.07.2015 Views

reynolds-the-quran-in-its-historical-context-2

reynolds-the-quran-in-its-historical-context-2

reynolds-the-quran-in-its-historical-context-2

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

98 Robert G. HoylandScript/Lang.: Lihyanite (Dedaniticl 2Bib!.: JS Lihl07; Noja 1979, XVI: Script/Lang.: N abataean Aramaic. Bib!.: Al<strong>the</strong>im and Stiehl1968, p. 310; Noja 1979, XXIIThe Jews of <strong>the</strong> Hijaz <strong>in</strong> <strong>the</strong> Qur 'an 99Text:" 'Azaryah son of Asyah" ( 'z1yh br asyh)No.llPlace: ai-UiaType: GraffitoDate: c. 3rd to 1st century BCEScript/Lang.: Lihyanite (Dedanitic)Bib!.: JS Lih12; W. Caskel, Lihyan und Lihyanisch, Ki:iln: Westdeutscher Verlag,1954, 103 (no. 58); Noja 1979, XVIIText: "By Al]'ab son of Simak <strong>the</strong> one buried [here]" or "By/for Al]'ab son ofSimak is <strong>the</strong> tomb" (/- 'b'b bn smk hmqbr I hmjbr). 23No.12Place: ai-UiaType: GraffitoDate: c. 1st to 3rd century CEScript/Lang.: Nabataean AramaicBib!.: JS Nab262; Al<strong>the</strong>im and Stieh11968, 308Text: "Greet<strong>in</strong>gs/Farewell Joseph son of 'A wiyu" (slm ywsf bn \ryw).2 4Umm Judhayidh (near Tabule)· · Type: Graffito. Date: c. 1st century BCE to 1st century CE·.Script/Lang.: Nabataean AramaicBib!.: al-Theeb 2002, no. 159· ··.·Text: "May Ghanam son ofY ehiidii be remembered" ( dkyr ghnmw br yhwd' . . . ) 25Place: Umm JudhayidhType: Graffitoc. 1st century BCE to 1st century CEScript/Lang.: Nabataean Aramaic]3ibL: ai-Theeb 2002, no. 84']'ext: "May Joseph son of Ghanam be remembered well. Peace" (dkyr ywsf br· ghnmw b-tb w-slm)No.l3Place: ai-UiaType: GraffitoDate: c. 1st to 3rd century CE22 An exact floruit for <strong>the</strong> k<strong>in</strong>gdom of Libyan, whose name has traditionally been used to designate<strong>the</strong>ir script (a version of <strong>the</strong> South Arabian script), has not been determ<strong>in</strong>ed, but <strong>the</strong>y were <strong>in</strong>fluenced<strong>in</strong> <strong>the</strong>ir art by <strong>the</strong> Ptolemies of Egypt (305-31 BCE) and were ousted by <strong>the</strong> Nabataeans <strong>in</strong><strong>the</strong> course of <strong>the</strong> first century BCE (see R.G. Hoyland, Arabia and <strong>the</strong> Arabs, London: Routledge,200 I, 66-68, for fur<strong>the</strong>r discussion and references).23 These are <strong>the</strong> different read<strong>in</strong>gs of JS Lihl2 and Noja 1979, XVII (follow<strong>in</strong>g Caskel) respectively.Caskel considers Ab' ab a Jewish name, but one would of course expect it to be written with a I)ra<strong>the</strong>r than a b. Smk and Smk'l are relatively common <strong>in</strong> Safaitic. All <strong>in</strong> all, <strong>the</strong>n, <strong>the</strong> Jewish natureof this <strong>in</strong>scription is dubious.24 Jaussen and Savignac note regard<strong>in</strong>g no. 12 (JS Nab262): "It is possible that <strong>the</strong> use of bn, attested<strong>in</strong> many o<strong>the</strong>r graffiti of <strong>the</strong> region, is due to <strong>the</strong> <strong>in</strong>fluence of <strong>the</strong> Jewish colony <strong>in</strong>stalled <strong>the</strong>re"( cf. JS Nab240 and Nab 261 ).Date: c. 3rd to 5th century CEScript/Lang.: Nabataean Aramaicc Bib!.: unedited 26· ·Text: "Indeed, may Simon son of 'Adiyu be remembered" (bly dkyr sm'wn br'dyw).·. ·· 25 AI-Theeb notes i)'lnvd as an option, buffavours njwd. However, <strong>the</strong> k<strong>in</strong>k <strong>in</strong> <strong>the</strong> <strong>in</strong>itial letter makesit pretty certa<strong>in</strong> that it is a 'y' ra<strong>the</strong>r than an 'n'. The f<strong>in</strong>al word <strong>in</strong> this text is uncerta<strong>in</strong>.26 Found <strong>in</strong> <strong>the</strong> course of <strong>the</strong> Saudi-French survey ofMada'<strong>in</strong> Salih (seen. 13 above).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!