170,957 research outputs found

    Speech Acts: The Contemporary Theoretical Landscape

    Get PDF
    What makes it the case that an utterance constitutes an illocutionary act of a given kind? This is the central question of speech-act theory. Answers to it—i.e., theories of speech acts—have proliferated. Our main goal in this chapter is to clarify the logical space into which these different theories fit. We begin, in Section 1, by dividing theories of speech acts into five families, each distinguished from the others by its account of the key ingredients in illocutionary acts. Are speech acts fundamentally a matter of convention or intention? Or should we instead think of them in terms of the psychological states they express, in terms of the effects that it is their function to produce, or in terms of the norms that govern them? In Section 2, we take up the highly influential idea that speech acts can be understood in terms of their effects on a conversation’s context or “score”. Part of why this idea has been so useful is that it allows speech-act theorists from the five families to engage at a level of abstraction that elides their foundational disagreements. In Section 3, we investigate some of the motivations for the traditional distinction between propositional content and illocutionary force, and some of the ways in which this distinction has been undermined by recent work. In Section 4, we survey some of the ways in which speech-act theory has been applied to issues outside semantics and pragmatics, narrowly construed

    Ontology-based patterns for the integration of business processes and enterprise application architectures

    Get PDF
    Increasingly, enterprises are using Service-Oriented Architecture (SOA) as an approach to Enterprise Application Integration (EAI). SOA has the potential to bridge the gap between business and technology and to improve the reuse of existing applications and the interoperability with new ones. In addition to service architecture descriptions, architecture abstractions like patterns and styles capture design knowledge and allow the reuse of successfully applied designs, thus improving the quality of software. Knowledge gained from integration projects can be captured to build a repository of semantically enriched, experience-based solutions. Business patterns identify the interaction and structure between users, business processes, and data. Specific integration and composition patterns at a more technical level address enterprise application integration and capture reliable architecture solutions. We use an ontology-based approach to capture architecture and process patterns. Ontology techniques for pattern definition, extension and composition are developed and their applicability in business process-driven application integration is demonstrated

    David Lewis's Place in the History of Late Analytic Philosophy: His Conservative and Liberal Methodology

    Get PDF
    In 1901 Russell had envisaged the new analytic philosophy as uniquely systematic, borrowing the methods of science and mathematics. A century later, have Russell’s hopes become reality? David Lewis is often celebrated as a great systematic metaphysician, his influence proof that we live in a heyday of systematic philosophy. But, we argue, this common belief is misguided: Lewis was not a systematic philosopher, and he didn’t want to be. Although some aspects of his philosophy are systematic, mainly his pluriverse of possible worlds and its many applications, that systematicity was due to the influence of his teacher Quine, who really was an heir to Russell. Drawing upon Lewis’s posthumous papers and his correspondence as well as the published record, we show that Lewis’s non- Quinean influences, including G.E. Moore and D.M. Armstrong, led Lewis to an anti- systematic methodology which leaves each philosopher’s views and starting points to his or her own personal conscience
    • …
    corecore