Thesis (M.A.)--Trinity Evangelical Divinity School, 1975. / Includes bibliographical references (leaves 96-105).

Thesis (M.S.)--University of Michigan, 1986.

This study examines the concept of rest in Mesopotamian literature (ML), the Deuteronomistic History (DH), and Chronicles. In the ML, the concept is expressed in four ways: 1) rest as a symbol of divine authority; 2) rest as a benefit offered to those being ruled; 3) the temple as the resting place of deities; and 4) the provision of rest to deities. A paradigm is formulated through which one may view the concept as a “cycle of rest,” where a state of rest moves from the provider (deity) downward to the recipient, and then back upward to the initial provider. “Noise” is the metaphorical disrupter of rest. In the DH, various rest-terms are employed by the Deuteronomist to express specific aspects of rest: 1) the noun menûḥâ demarcates the arc of the promise and fulfillment in Deut 12:9 and 1 Ki 8:56, and it is a spatial concept (land of inheritance and the temple); 2) the technical formula (nûaḥ hiphil (1) + l) portrays the divine provision of rest; 3) alternative words that mean rest such as šqṭ are used to express periods of rest and unrest; 4) the secondary use of the verb nûaḥ (hiphil (2)) depicts the placing of the ark or cultic vessels/objects. 1 Chronicles 22:9 is programmatic for the concept in Chronicles. The focus in Chronicles is on a proper relationship with YHWH (instead of the spatial emphasis in the DH) due to a post-exilic understanding that the inheritance had already been lost. In contrast to the monarchic period narrated in Kings, cycles of rest emerge in Chronicles with post-Solomonic kings and is more comparable to Judges. The end of Chronicles portrays an era similar to Judges, when the nation is en route to a new political arrangement with YHWH—similar to the Chronicler's post-exilic circumstances.

Thesis (Ph. D.)--Columbia University, 1927. / Vita. "Reprinted from Archives of psychology ... no. 90."

Thesis (M.A.)--Talbot School of Theology, Biola University, 2008. / Includes bibliographical references (leaves 183-189).

Thesis (M.A.)--Talbot School of Theology, Biola University, 2008. / Includes bibliographical references (leaves 183-189).

Thesis (M. A.)--Trinity Evangelical Divinity School, 2009. / Abstract. Description based on print version record. Includes bibliographical references (leaves 72-79).

Introspected REST ist ein neuer Ansatz für die Entwicklung von Web-APIs, welcher auf REST aufbaut. In der vorliegenden Arbeit wird dieser neue API-Stil mit REST, GraphQL und gRPC hinsichtlich der Performance, Evolvierbarkeit und Komplexität bzw. Benutzbarkeit verglichen. Die Performance der untersuchten Introspected-REST-API liegt dabei im gleichen Bereich wie die der REST-API, welche ihrerseits von gRPC und GraphQL übertroffen wird. Auch die Evolvierbarkeit ist gleich gut im Vergleich zu REST. Die Verwendung von Introspected REST trägt vor allem zu einer besseren Benutzbarkeit der API bei.:1. Einleitung 2. Grundlagen von Web-APIs 2.1. Definition und Einteilung 2.2. Der Architekturstil Representational State Transfer (REST) 2.2.1. Grundlagen des Webs 2.2.2. REST-Prinzipien 2.2.3. Ablauf der Interaktionen zwischen Client und Server 2.3. Die Abfragesprache GraphQL 2.4. Das gRPC-Protokoll 2.5. Zusammenfassung 3. Introspected REST 3.1. Definition und Hauptbestandteile 3.1.1. Datenmodell 3.1.2. Probleme von REST 3.1.3. Das Introspection-Prinzip 3.1.4. Microtypes 3.2. Prototypische Implementierung 3.2.1. Ein Container-Mediatype für Microtypes 3.2.2. Content-Negotiation für Microtypes 3.2.3. Introspection durch HTTP-OPTIONS 3.2.4. Implementierung in ASP.NET Core 3.3. Zusammenfassung 4. Kriterien für den Vergleich der API-Stile 4.1. Performance 4.1.1. Performancemetriken für Web-APIs 4.1.2. Experiment zur Erfassung der Metriken 4.1.3. Validität und Übertragbarkeit der Ergebnisse 4.1.4. Verwandte Arbeiten 4.2. Evolvierbarkeit 4.2.1. Definition und Einteilung für Web-APIs 4.2.2. Durchführung eines Evolvierbarkeit-Vergleichs für API-Stile 4.2.3. Validität und Übertragbarkeit der Ergebnisse 4.2.4. Verwandte Arbeiten 4.3. Komplexität 4.3.1. Arten der Komplexität bei Web-APIs 4.3.2. Bewertung der Benutzbarkeit einer Web-API 4.3.3. Validität und Übertragbarkeit der Ergebnisse 4.3.4. Verwandte Arbeiten 4.4. Zusammenfassung 5. Vergleich der API-Stile 5.1. Performance 5.1.1. Ermittlung von Requestanzahl und Nachrichtengrößen 5.1.2. Ermittlung der Antwortzeiten 5.2. Evolvierbarkeit 5.3. Komplexität 5.3.1. Heuristiken für die Erlernbarkeit 5.3.2. Heuristiken für das Vorbeugen von Fehlern 5.3.3. Heuristiken für Einfachheit 5.3.4. Heuristiken für Konsistenz 5.3.5. Zusammenfassung 6. Diskussion 6.1. Performance 6.2. Evolvierbarkeit 6.3. Komplexität 6.4. Zusammenfassung 7. Fazit und Ausblick Literatur A. Ergebnisse der Performancemessungen B. Codebeispiele / Introspected REST is a new approach to the development of web APIs. It builds upon the REST architectural style. In this thesis, Introspected REST is compared to REST, GraphQL, and gRPC in terms of performance, evolvability, and complexity/usability. The results show that the performance of Introspected REST is in the same order of magnitude as the performance of REST. Both are in turn outperformed by gRPC and GraphQL, respectively. The evolvability rates similarly to REST’s evolvability, too. Using Introspected REST for an API does most notably improve its usability.:1. Einleitung 2. Grundlagen von Web-APIs 2.1. Definition und Einteilung 2.2. Der Architekturstil Representational State Transfer (REST) 2.2.1. Grundlagen des Webs 2.2.2. REST-Prinzipien 2.2.3. Ablauf der Interaktionen zwischen Client und Server 2.3. Die Abfragesprache GraphQL 2.4. Das gRPC-Protokoll 2.5. Zusammenfassung 3. Introspected REST 3.1. Definition und Hauptbestandteile 3.1.1. Datenmodell 3.1.2. Probleme von REST 3.1.3. Das Introspection-Prinzip 3.1.4. Microtypes 3.2. Prototypische Implementierung 3.2.1. Ein Container-Mediatype für Microtypes 3.2.2. Content-Negotiation für Microtypes 3.2.3. Introspection durch HTTP-OPTIONS 3.2.4. Implementierung in ASP.NET Core 3.3. Zusammenfassung 4. Kriterien für den Vergleich der API-Stile 4.1. Performance 4.1.1. Performancemetriken für Web-APIs 4.1.2. Experiment zur Erfassung der Metriken 4.1.3. Validität und Übertragbarkeit der Ergebnisse 4.1.4. Verwandte Arbeiten 4.2. Evolvierbarkeit 4.2.1. Definition und Einteilung für Web-APIs 4.2.2. Durchführung eines Evolvierbarkeit-Vergleichs für API-Stile 4.2.3. Validität und Übertragbarkeit der Ergebnisse 4.2.4. Verwandte Arbeiten 4.3. Komplexität 4.3.1. Arten der Komplexität bei Web-APIs 4.3.2. Bewertung der Benutzbarkeit einer Web-API 4.3.3. Validität und Übertragbarkeit der Ergebnisse 4.3.4. Verwandte Arbeiten 4.4. Zusammenfassung 5. Vergleich der API-Stile 5.1. Performance 5.1.1. Ermittlung von Requestanzahl und Nachrichtengrößen 5.1.2. Ermittlung der Antwortzeiten 5.2. Evolvierbarkeit 5.3. Komplexität 5.3.1. Heuristiken für die Erlernbarkeit 5.3.2. Heuristiken für das Vorbeugen von Fehlern 5.3.3. Heuristiken für Einfachheit 5.3.4. Heuristiken für Konsistenz 5.3.5. Zusammenfassung 6. Diskussion 6.1. Performance 6.2. Evolvierbarkeit 6.3. Komplexität 6.4. Zusammenfassung 7. Fazit und Ausblick Literatur A. Ergebnisse der Performancemessungen B. Codebeispiele

While studies have explored and analyzed the concept of rest in a variety of literary works in the Hebrew Bible (HB) and the Ancient Near East (ANE), attention given to its theological significance and rhetorical function in the literary context of Genesis 1–11 has been wanting. This thesis thus examines how the concept contributes to the thematic development and rhetorical design of Genesis 1–11. It is an exegetical and theological reflection that approaches Genesis 1–11 as a unified textual unit with a coherent literary message. In this light, the primary method to explicate the significance of rest from this literary context is by means of exegesis or a “close reading” of the text. The concept of rest in the ANE signifies not mere inactivity, but rather, the ideal conditions in which another activity or state of being is engaged or experienced. Rest thus includes both elements: cessation from one activity or state of being (rest from) and the engagement of another activity or state of being (rest for). The concept of rest (expressed in a wide variety of lexical terms and associated ideas) within the HB can be broadly described as the ideal conditions (characterized by stability, security, and order) intended for blessing, holiness, and justice within the covenantal relationship with YHWH, that in turn results in the worship of YHWH and the flourishing of his created order. In this light, the provision of rest functions as a powerful soteriological symbol, in which the act of providing rest is regularly expressed as movement (or transition) from particular circumstances or situations (i.e. rest from) to an ideal state for an intended purpose (i.e. rest for). This conceptual pattern can be portrayed as: rest from (particular conditions) → rest to (ideal state) → rest for (purpose). At the same time, a state of unrest indicates the result of God's judgment for rebellion and the fracturing of his relationship with his people, which also has adverse effects on the created order. The concept of rest can be expressed with a broad semantic field of lexical terms, but is most prominently expressed with the terms, שׁבת and נוח . Although scholars have tended to isolate these terms into separate “traditions,” they share a close semantic, conceptual, and theological relationship that is expressed in several passages throughout the HB, which demonstrates the ability to utilize these terms as a coherent literary motif. This understanding is crucial to appreciate the utilization of the rest motif in Genesis 1–11, for the goal of creation is initially expressed with שׁבת but is thematically developed with נוח (along with associated terms and ideas). The rhetorical function of the concept of rest as a literary motif is understood in the light of the overarching theme of Genesis 1–11, which may be expressed as Rest–Unrest– vi Comfort. This theme effectively articulates the development of Genesis 1–11, in which the essential goodness and the intended purposes of God's created order (Rest) are affected by human rebellion that results in the destructive flood (Unrest) but leads to a new reality that humanity must face the enduring consequences of sin with the enduring hope of God's grace (Comfort). Thus, along the contours of this thematic development, the rest motif is traced: the goal of creation is expressed as the rest of God on the seventh day, in which humanity is intended to participate and to provide to the created order. The undoing of creation is expressed with concepts of unrest such as humanity's exile, wandering, wearisome toil, and oppression that culminates with the destructive flood. Finally, the renewal of creation— characterized as a mixture of rest and unrest, blessing and curse—is aptly portrayed as mere comfort (Genesis 5:29) forcing humanity to long for (and even anticipate) the fulfillment of God's intended purposes for his created order. In this light, the concept of rest not only informs the thematic development of Genesis 1–11, but also provides further clarity and greater complexity to its overall rhetorical design and theological message.

Smartphones are used by incredibly many people, and in 2011 there where a total of 491.4million units soled worldwide. Smartphones are known as advanced phones, or personal digital assistants (PDAs). This makes a relevant technique for performing dietary studies when the test patients are on the move. This thesis shows how to create a back end environment for an Android application with existing techniques linked together, using MSSQL database, Visual Studio Web Service, web pages and C# classes and ASP.NET security.The back end development is used in a dietary study on Gothenburg University, but could be applied on many similar back end projects using databases and server development.Techniques used in this thesis are: REST (Representational State Transfer) -clientimplementation and development inside the Android application, using HTTP methods toset and get information from the server and database, and JSON-format to read and transfer information in an easy and understandable way, both from the Android application and from the database. FileMaker is also used in this project as a third part programme to visualise the information in the database.