Image
EAN-139780801047220   EAN-13 barcode 9780801047220
Product NameThe Epistle to the Ephesians (Black's New Testament Commentary)
LanguageEnglish
CategoryBook / Magazine / Publication
Amazon.comA Buy on Amazon ~ 0801047226
Price New39.95 US Dollars    (curriencies)
Price Used8.98 US Dollars    (curriencies)
Width5.86 inches    (convert)
Height1.05 inches    (convert)
Length8.41 inches    (convert)
Weight20.48 ounces    (convert)
AuthorJohn Muddiman
Page Count352
BindingHardcover
Published05/01/2004
FeaturesISBN13: 9780801047220, Condition: New, Notes: BRAND NEW FROM PUBLISHER! 100% Satisfaction Guarantee. Tracking provided on most orders. Buy with Confidence! Millions of books sold!
Long DescriptionIn this comprehensive commentary, John Muddiman begins by arguing that to be able to draw conclusions about the text of Ephesians, each scholar must take a position about its Pauline or non-Pauline authorship. He therefore offers an extensive introduction, which discusses various approaches to this question, including his own, detailing the evidence for each position. All the perspectives of major modern scholars are discussed and assessed, particularly on the question of Ephesians's relationship to Colossians. The implications of the question of authorship for evaluating Paul's theology are extensively discussed. Black's New Testament Commentary series presents a reliable and enlightening exposition of the New Testament for the modern reader. Written by highly respected biblical scholars under the editorial directorship of Morna D. Hooker, each commentary offers a paragraph-by-paragraph exposition based on the author's own, fresh translation of the biblical texts. Other features include insightful introductions to the important historical, literary, and theological issues; key terms and phrases from the translation highlighted in the commentary where they are discussed; explanations of special Greek or foreign terms; references to important primary and secondary literature; and a Scripture index.
Similar Items9780801046803: The Epistles Of Peter And Of Jude (Black's New Testament Commentary)
9780801026836: Ephesians (Baker Exegetical Commentary On The New Testament)
9780687056996: Abingdon New Testament Commentaries: Ephesians
9780567084453: Ephesians (International Critical Commentary)
9780805401288: 1 Corinthians: An Exegetical and Theological Exposition of Holy Scripture (The New American Commentary)
9780801048135: Galatians (Baker Exegetical Commentary On The New Testament)
9780801027543: Galatians (Baker Exegetical Commentary On The New Testament)
9780664221256: Ephesians (2012): A Commentary (New Testament Library)
9780664221232: Galatians (2011): A Commentary (New Testament Library)
9781565630369: The Epistle To The Galatians
View 6 more similar items
Created10-19-2013 12:55:04am
Modified05-01-2020 1:58:11am
MD5123652a5bcb56f59286bc28fdde5a903
SHA2566f09570358b7524fdc3e590b64d8987180af3100838ed99bf91f33ef686cdc94
Search Googleby EAN or by Title
Query Time0.0216742

Article of interest

With version 3.2 comes a new way to handle product images. This should give you more control over the images you display.

Prior to version 3.2, you simply had to check for the existance of the product>image property. If it existed and was not blank, you could safely display the image. 

Starting with version 3.2, you may want to check one more field before you display the product image. Many API users wanted access to the pending images. The only reasonable way to do this was to add a new property named product>hasImage which can be one of four values.

If you are displaying the product images to your users and you DO NOT want to display pending images that have not been checked, you should only display the image if product>hasImage=Yes. If you want to show production and pending images, you can simply check the product>image property if you like. We suggest using product>hasImage as your main check and only display the image if it meets your needs. Here are samples of the JSON structure.

The property product>hasImage will always be regurned even if you specified a list of properties in the "get" string that does not include the image property. The main reason for this is that it is possible to calculate the image path on your side thereby saving the bandwidth of returning the image path.

If you want to calculate the path to the image on your end instead of requesting it from us, you can do this in two ways. 

  1. If product>hasImage=Pending then simply use the path https://eandata.com/image/pending/{13_digit_EAN}.jpg
  2. If product>hasImage=Yes then it gets a little more tricky. We split the images into subfolders because there are so many of them. To calculate the path start with the 13 digit EAN and split it up like this: https://eandata.com/image/product/{1st_3_digits}/{2nd_3_digits}/{3rd_3_digits}/{13_digit_EAN}.jpg

This should make interacting with product and pending images much easier for you. Look at the example JSON shown above for working exmples of image paths.

Close

Search

Close

Share