S. Ceri and R. Manthey. Consolidated specification of Chimera, the conceptual interface of Idea. Technical Report IDEA.DD.2P.004, ESPRIT Proj. 6333 Idea, 1993.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....(and consequently modify) several rule applications. Although our methods have been designed for the Starburst Rule System, we expect that they can be adapted to accommodate the syntax and semantics of many other active database rule languages, including A RDL [SKdM92] Ariel [Han92] Chimera [CM93] POSTGRES [SJGP90] Sentinel [AMC93] and others [CL92, DHW94] We also expect that our techniques should be applicable to the upcoming standard for triggers in SQL3. To apply our methods to an alternative rule language, the fundamental definitions of Section 5 (Triggers, Performs, Choose, etc. ....

S. Ceri and R. Manthey. Consolidated specification of Chimera, the conceptual interface of Idea. Technical Report IDEA.DD.2P.004, Politecnico di Milano, Milan, Italy, June 1993.

....and of instances for example, the migration of an instance from one class to another. In the latter kind of evolution, an instance modifies its own structure while maintaining the same identity. In this paper we discuss instance evolution in the context of the Chimera object oriented data model [11, 18]. However, though developed with reference to the Chimera data model, the discussion is applicable to any object oriented database system. Chimera 1 is an object oriented, deductive, active data model developed as part of ESPRIT Project Idea P6333. Chimera provides all concepts commonly ascribed ....

.... reported to the user (together with the OID of the violating object, bound to variable X) and the user can decide how to solve it (e.g. by aborting the transaction, by deleting the object, and so on) These exclusivity constraints, like other Chimera constraints, can also be expressed as triggers [11], containing not only the condition that should not be violated but also the repairing action. 5 ADDITIONAL EXAMPLES In this section we present few additional examples involving some form of object evolution. 5.1 Polygons, Squares, and Rectangles Consider the database schema in Figure 3. Class ....

[Article contains additional citation context not shown here]

S. Ceri and R. Manthey. Consolidated Specification of Chimera. Technical Report IDEA.DE.2P.006.01, ESPRIT Project 6333, November 1993.

....of object orientation is the encapsulation of data and behaviour in one object. Rules are part of the behaviour of objects. They describe what actions triggered in specific situation. Examples of object oriented DBMSs that offer encapsulation of rules in objects are SAMOS [15] and Chimera [10]. However, these systems offer a hybrid model. In both systems it is still possible to define rules separate from a class. Thus, we do not have a single place to look for the behaviour of an object. We take encapsulation to its extremes. All behaviour is encapsulated with an object. Thus, the ....

....in such a way that rules can be treated as objects themselves. A object oriented system would offer the possibility of defining a rule on an object, a facility present in, for example, SAMOS [15] Definition of rules is also possible outside a class in SAMOS however. The same is true for Chimera [10]. 5. Conclusions and Future Research 20 Chimera integrates deductive, object oriented and active databases. This means that there is a distinction between passive Datalog rules and active rules, or triggers. In our model rules are always encapsulated in objects. Because relations are objectified, ....

Stefano Ceri and Rainer Manthey. Consolidated specification of Chimera (CM and CL). Technical Report IDEA.DE.2P.006.01, IDEA, ESPRIT Project 6333, 1993. Available by FTP from rodin.inria.fr:/pub/IDEA/DE.2P.006.ps.gz.

....the integrated languages. Query power: relates to the query classes supported by the query language (FOLQ = first order queries, FIXP = fixpoint queries, HOQ = higherorder queries) Table 1 shows a comparison between the query facilities supported by DOQL and the query components of Chimera [6], Coral [16] OQL [4] OQLC [3] Noodle [12] and ROCK ROLL [1] Some important aspects of our design are: Criteria Language Bidirection Restruct. Type Query of Calls Operators System Power Chimera no unnest Chimera object model FOLQ, FIXP Coral no set group. unnest C FOLQ, ....

S. Ceri and R. Manthey. Consolidated specification of chimera (cm and cl). Technical Report IDEA.DE.2P.006.1, IDEA - ESPRIT project 6333, 1993.

....able to interpret. Phoenix has been implemented on top of Eclipse, but may be run in main memory mode (i.e. without persistent data structures) by most conventional Prolog systems as well. The Interpreter supports most of the features of Chimera as defined in the Consolidated Specification ([CM93]) but does not aim at providing particularly efficient or refined implementations of individual concepts. There are a few points where the implemented version of Chimera deviates from the version in [CM93] Apart from these points, the functionality of Chimera has been enhanced by low level ....

....most of the features of Chimera as defined in the Consolidated Specification ( CM93] but does not aim at providing particularly efficient or refined implementations of individual concepts. There are a few points where the implemented version of Chimera deviates from the version in [CM93]. Apart from these points, the functionality of Chimera has been enhanced by low level schema evolution operations for the Chimera Interpreter programming interface in order to enable basic changes of an application schema. However, we decided not to change the basic semantics of Chimera, e.g. ....

[Article contains additional citation context not shown here]

Stefano Ceri and Rainer Manthey. Consolidated specification of Chimera. IDEA deliverable IDEA.DE.2P.006.001, ESPRIT Project 6333, 1993.

....how it is possible, using the language E hhf , to define a clean and simple semantics for object oriented, deductive and active databases in a completely logical setting, that accounts for the various aspects of computation. In order to do this, we will briefly describe the semantics of Chimera [9, 19], an example of data model and language for DBMS which supports object oriented, deductive, and active database features. Keywords: higher order linear logic, abstract logic programming language, object oriented, deductive and active databases. 1 Introduction Linear logic [18] has acquired ....

.... or to enhance SQL with object oriented capabilities [14] A system, whose goal is specifically the integration of object oriented, deductive and active capabilities has been developed as part of the ESPRIT Project Idea [6, 7] In this work we shall describe the data model of Idea, called Chimera [9, 19, 8], and we shall give a semantics for it. We have chosen Chimera because it is a meaningful example of the integration of different paradigms, and, though not a commercial system, it is actually implemented. It seems important here to base the semantics of such languages on a general purpose logic ....

[Article contains additional citation context not shown here]

S. Ceri and R. Manthey. Consolidated specification of Chimera. Technical report, ESPRIT Rep.IDEA.DE.2P.006.01, November 1993.

....notation, twosided sequents nicely capture the evolution of state transitions and the proof construction corresponds to the operational computation. The paper presents a particular application of E hhf to the specification of a deductive object oriented database system called Chimera [10, 9, 23], which is an interesting example of integration among different programming paradigms. This is an interesting example to verify the power and the flexibility of the considered framework. In the next sections we shall describe the data model of Chimera [10, 9, 23] developed as part of the ESPRIT ....

....database system called Chimera [10, 9, 23] which is an interesting example of integration among different programming paradigms. This is an interesting example to verify the power and the flexibility of the considered framework. In the next sections we shall describe the data model of Chimera [10, 9, 23], developed as part of the ESPRIT Project Idea [8] and we shall give a logical semantics to it by defining an encoding in E hhf . Chimera has been chosen as a representative of modern database management systems (DBMS) These incorporate, for instance, objects modeling capabilities into deductive ....

[Article contains additional citation context not shown here]

S. Ceri and R. Manthey. Consolidated specification of Chimera. Technical report, ESPRIT Rep.IDEA.DE.2P.006.01, November 1993.

....1 , Giorgio Delzanno 2 and Maurizio Martelli 1 1 DISI Universit a di Genova, Via Dodecaneso, 35, I 16146, Italy bozzano,martelli disi.unige.it tel: 39 10 3536727 fax: 39 10 3536699 2 MPI fur Informatik, Im Stadtwald, D 66123 Saarbrucken, Germany delzanno mpi sb.mpg.de Abstract. Chimera [11] is an active, deductive, and object oriented database system which incorporates many of the most advanced technologies in the field. Our work is aimed at proposing a formalization of its computational contents by employing the language Ehhf [14] a rich linear logic programming and specification ....

S. Ceri and R. Manthey. Consolidated specification of Chimera. Technical report, ESPRIT Report IDEA.DE.2P.006.01, November 1993.

....System, and we discuss future directions of this work. 2 Related Work Numerous other active database systems have been designed and some have been implemented. The three systems closest to the Starburst Rule System are Ariel [31] the second version of the POSTGRES Rule System [42] and Chimera [12,14]. The Ariel system has a rule language and execution semantics based closely on OPS5 [9] a production rule language originally designed for expert systems. The Ariel project has focused on the design of an OPS5 like rule language for the database setting, and on methods for highly efficient rule ....

....it is our belief that for every choice of semantics it is possible to concoct a reasonable example for which that semantics is inconvenient or inappropriate. The recent Chimera active rule system addresses this issue by allowing its users to choose between a number of alternative semantics [14]. 4.3 Rule Processing Commands While end of transaction rule processing is sufficient for many applications, we have found that in some cases it is useful for rules to be processed within a transaction (for example, to verify consistency after some operations have been executed but before the ....

S. Ceri and R. Manthey. Consolidated specification of Chimera, the conceptual interface of Idea. Technical Report IDEA.DD.2P.004, Politecnico di Milano, Milan, Italy, June 1993.

.... difference) Handle special cases where PF (C) and PT (C) can optimize conditions currently not optimized (recall Section 4) Consider similar methods in the context of deductive and object oriented active database systems (e.g. we hope to use these methods in the IDEA project [5], where they should apply in a straightforward way) Investigate query optimization strategies that exploit references to very small relations, such as the delta relations used in our optimized conditions. Implement our method in the Starburst Rule System and experiment with its practical ....

S. Ceri and R. Manthey. Consolidated specification of Chimera, the conceptual interface of Idea. Technical Report IDEA.DD.2P.004, Politecnico di Milano, Milan, Italy, June 1993.

..... 96 References 97 1 Introduction This document provides the technical documentation for the Chimera Prototyping Tool (CPT) an experimental implementation of the Chimera data model and language introduced by members of the IDEA 1 consortium in 1993 [CM93, CM94, CF96]. The tool has been designed and implemented by the IDEA team at the University of Bonn. This report serves the purpose of describing the way CPT implements the object oriented Chimera data model and language on top of the active, deductive, and relational database system Phoenix [Gri95] Although ....

....combinable into sequences and transactions. Chimera does not provide a full programming language but has to be embedded into some general purpose language. For a more in depth presentation of Chimera readers are referred to the sources mentioned above, particularly the Consolidated Specification [CM93]. We do not provide any introduction or tutorial help concerning Chimera here. 1.2 Basic Characteristics of Phoenix Phoenix is an active, deductive database programming language (aDBPL) which has been developed at the computer science department of the University of Bonn as well. It runs on top ....

[Article contains additional citation context not shown here]

Stefano Ceri and Rainer Manthey. Consolidated specification of Chimera (CL and CM). Technical Report IDEA.DE.2P.006.01, Politecnico di Milano, Milan, Italy, November 1993. ESPRIT project P6333 (IDEA).

.... Project 6333 Intelligent Database Environment for Advanced Applications IDEA 1 INTRODUCTION This document provides a user manual for the Chimera Prototyping Tool (CPT) an experimental implementation of the Chimera data model and language introduced by members of the IDEA 1 consortium in 1993 [CM93, CM94]. The tool has been designed and implemented by the IDEA team at the University of Bonn during the last twelve months. CPT is a prototype system, aimed at rapid and experimental development of Chimera testcases rather than at industrial strength development of large and complex applications. This ....

....combinable into sequences and transactions. Chimera does not provide a full programming language but has to be embedded into some generalpurpose language. For a more in depth presentation of Chimera readers are referred to the sources mentioned above, particularly the Consolidated Specification [CM93]. We do not provide any introduction or tutorial help concerning Chimera here. Note, however, that there are a few features where the syntax and semantics supported by the CPT differs from the official one defined in the consolidated specification. These features have been summarized at the end ....

[Article contains additional citation context not shown here]

Stefano Ceri and Rainer Manthey. Consolidated specification of Chimera (CL and CM). Technical Report IDEA.DE.2P.006.01, Politecnico di Milano, Milan, Italy, November 1993. ESPRIT project P6333 (IDEA).

....may be several attribute values which still refer to the deleted object. Thus, a further important task we assume the system to perform is to drop from each of these attributes all OIDs referring to deleted objects. This implicit referential integrity constraint is to be enforced as proposed in [CM93]: Assume that an object O is deleted from class C, the OID of the deleted object is dropped from all attribute values which refer to O in other objects O 0 . Then: 1. If C is the type of an atomic attribute of O 0 (either defined individually or as a record component) its value is set to ....

Stefano Ceri and Rainer Manthey. Consolidated specification of Chimera (CL and CM). Technical Report IDEA.DE.2P.006.01, Politecnico di Milano, Milan, Italy, November 1993. ESPRIT project P6333 (IDEA).

....schema might result in the need to perform hypothetical updates on test data, that have to be propagated for analytical purposes as well. Chimera, the language we deal with in this paper, is a novel database language which has been designed within the context of the ESPRIT project P6333 (IDEA) [CM93]. Chimera is based on a conceptual model which provides object oriented modeling facilities. It includes data definition commands, declarative queries, procedural primitives for database manipulations, as well as deductive rules for the definition of derived data and constraints, and active rules ....

....context targeted concepts are easier to understand and should therefore be used as often as possible. In the following we will not introduce the full syntax of Chimera, but restrict ourselves to the subset required in the remaining sections. A complete specification of Chimera can be found in [CM93]. As this paper is concerned with update propagation due to the presence of derived attributes the Chimera subset required includes essentially object classes, views, and triggers. 2.1 Object Classes and Views The definition of an object class in Chimera is composed of two sections: signature ....

Stefano Ceri and Rainer Manthey. Consolidated specification of Chimera (CL and CM). Technical Report IDEA.DE.2P.006.01, Politecnico di Milano, Milan, Italy, November 1993. ESPRIT project P6333 (IDEA).

....may be several attribute values which still refer to the deleted object. Thus, a further important task we assume the system to perform is to drop from each of these attributes all OIDs referring to deleted objects. This implicit referential integrity constraint is to be enforced as proposed in [CM93]: Assume that an object O is deleted from class C, the OID of the deleted object is dropped from all attribute values which refer to O in other objects O 0 . Then: 1. If C is the type of an atomic attribute of O 0 (either defined individually or as a record component) its value is set to ....

Stefano Ceri and Rainer Manthey. Consolidated specification of Chimera (CL and CM). Technical Report IDEA.DE.2P.006.01, Politecnico di Milano, Milan, Italy, November 1993. ESPRIT project P6333 (IDEA).

....to interpret. Phoenix has been implemented on top of ECL i PS e , but may be run in main memory mode (ie, without persistent data structures) by most conventional Prolog systems as well. The Interpreter supports most of the features of Chimera as defined in the Consolidated Specification [CM93] but does not aim at providing particularly efficient or refined implementations of individual concepts. There are a few points where the implemented version of Chimera deviates from the version in [CM93] The Propagation Rule Compiler is one of three tools for schema management in Chimera ....

....supports most of the features of Chimera as defined in the Consolidated Specification [CM93] but does not aim at providing particularly efficient or refined implementations of individual concepts. There are a few points where the implemented version of Chimera deviates from the version in [CM93]. The Propagation Rule Compiler is one of three tools for schema management in Chimera currently under development in Bonn. All of them are based on the Chimera Interpreter (as a common low level interface) and share a graphics based schema editor and manipulator (as a joint high level interface) ....

Stefano Ceri and Rainer Manthey. Consolidated specification of Chimera (CL and CM). Technical Report IDEA.DE.2P.006.01, Politecnico di Milano, Milan, Italy, November 1993. ESPRIT project P6333 (IDEA).

....by the IDEA partners. In this paper, the tools developed at the University of Bonn will be introduced. They support schema design, prototyping and evolution as well as deductive rule analysis and automatic generation of triggers for analyzing updates of derived data. 1 Introduction Chimera [5, 6] is a novel database model and language combining active and deductive database concepts in a coherent object oriented context. Till now, there are only very few attempts which aim at combining both rule paradigms with an object oriented data model. At present, only the Rock Roll language [1] goes ....

....applications. The language proved to support a lot of requirements in a quite satisfactory manner, though naturally a couple shortcomings of the original design have been identified over time. Apart from the document defining the language in the form originally designed by the IDEA consortium [5], a comprehensive introduction into Chimera can be found in the book presenting the IDEA methodology [3] Chimera consists of a conceptual model (called Chimera Model, short: CM) providing object oriented modeling facilities, and of a conceptual language (called Chimera Language, short: CL) ....

[Article contains additional citation context not shown here]

S. Ceri and R. Manthey. Consolidated specification of Chimera (CL and CM). IDEA deliverable IDEA.DE.2P.006.01, Politecnico di Milano, 1993.

No context found.

S. Ceri and R. Manthey. Consolidated specification of Chimera, the conceptual interface of Idea. Technical Report IDEA.DD.2P.004, ESPRIT Proj. 6333 Idea, 1993.

No context found.

Stefano Ceri, Rainer Manthey: "Consolidated specification of Chimera". Report IDEA.DE.2P.006.01, ESPRIT Project 633 IDEA, Nov. 1993.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC