The Monkish Mysteries; or, the Miraculous Escape: Containing the History and Villainies of the Monk Bertrand, the Detection of His Impious Frauds, and Subsequent Repentance and Retribution.

Monkish Mysteries recounts the life of Edward Stanley, The son of a disgraced knight, who is taken in by Pascal and entangled in the hatred between Pascal and the son of a priest and his seduced parishioner, Bertrand, who assumes the name Mystere. One day, Pascal is taken away by four men on horseback under orders by Mystere. Edward pleads for Pascal’s release but to no avail and departs back to Switzerland, followed by Mystere. He returns to find Albina, his love, has left for Germany after being told of Edward’s death. In the meantime Mystere ingratiates himself with the Franciscans in the area. Edward goes in search of Albina and Remeau, Albina’s brother, stays behind secretly views Mystere practicing his ‘miracle’ which is really just a trick. Edward goes to the church at night and confronts him. He is discovered and is put in a cell in the abbey. Edward escapes and goes in search of Remeau and Albina. Edward, Remeau and Pascal reunite in Switzerland. Remeau has written a history of Edward that reveals Mystere’s trick and sends it to the Prince that Mystere currently advises who subsequently throws him in jail. Mystere escapes to the woods where he runs into Albina who has recently escaped from her own imprisonment. Mystere has a crisis of conscious and repents for his actions. He protects Albina from capture and helps her escape again. Mystere, prompted by a dream, repents to Edward and all go on to lead happy lives.https://epublications.marquette.edu/english_gothic/1007/thumbnail.jp

PLACES'10: The 3rd Workshop on Programmng Language Approaches to concurrency and Communication-Centric Software

Paphos, Cyprus. March 201

The business process modelling ontology

In this paper we describe the Business Process Modelling Ontology (BPMO), which is part of an approach to modelling business processes at the semantic level, integrating knowledge about the organisational context, workflow activities and Semantic Web Services. We harness knowledge representation and reasoning techniques so that business process workflows can: be exposed and shared through semantic descriptions; refer to semantically annotated data and services; incorporate heterogeneous data though semantic mappings; and be queried using a reasoner or inference engine. In this paper we describe our approach and evaluate BPMO through a use case

Spiritual and Religious Characteristics in Cancer Patients

Bio-psycho-socio-spiritual problems often appear in cancer patients; however, the spiritual and religious characteristics that appear in cancer patients have not been widely studied. The objective of this research was to analyze the spiritual and religious characteristics of cancer patients. This research consisted of a scoping review of national and international articles published in 2013-2018. The researchers searched for articles through Google Scholar, PubMed, and ProQuest with the keywords ‘cancer’, ‘spiritual’ and ‘religious’. There were 2,727 articles identified, and the 38 articles that met the inclusion criteria were reviewed. According to the results, spiritual and religious characteristics in cancer patients included the use of spirituality and religion as a coping mechanism, belief in God as a source of strength, the need for family support and spiritual or religious communities, cancer as a process of spiritual or religious maturity, and changes in spiritual or religious rituals. The results of this review can be used to complement guidelines on spiritual and religious nursing care for cancer patients. Keywords: cancer, palliative, spiritual, religious, terminal car

A Classification of BPEL Extensions

The Business Process Execution Language (BPEL) has emerged as de-facto standard for business processes implementation. This language is designed to be extensible for including additional valuable features in a standardized manner. There are a number of BPEL extensions available. They are, however, neither classified nor evaluated with respect to their compliance to the BPEL standard. This article fills this gap by providing a framework for classifying BPEL extensions, a classification of existing extensions, and a guideline for designing BPEL extensions

A compensating transaction example in twelve notations

The scenario of business computer systems changed with the advent of cross-entity computer interactions: computer systems no longer had the limited role of storing and processing data, but became themselves the players which actuated real-life actions. These advancements rendered the traditional transaction mechanism insufficient to deal with these new complexities of longer multi-party transactions. The concept of compensations has long been suggested as a solution, providing the possibility of executing “counter”-actions which semantically undo previously completed actions in case a transaction fails. There are numerous design options related to compensations particularly when deciding the strategy of ordering compensating actions. Along the years, various models which include compensations have emerged, each tackling in its own way these options. In this work, we review a number of notations which handle compensations by going through their syntax and semantics — highlighting the distinguishing features — and encoding a typical compensating transaction example in terms of each of these notations.peer-reviewe

The supernatural in European and American drama

Thesis (M.A.)--Boston University This item was digitized by the Internet Archive