| T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in ObjectRole Modelling. Data & Knowledge Engineering, 15:251--281, 1995. |
....single definition of roles integrating all of them. 1. A role comes vith its ovn properties and behaviour. This basic property suggests that roles are types. And indeed, only few approaches do not regard roles as types; among these are the EntityRelationship (ER) model and some of its relatives [14,17,24,33,34]. 2. Roles depend on relationships [7,15,21,30,59] As suggested by the work of Sowa and Guarino, a role is meaningful only in the context of a relationship. Although a fundamental characteristic, many definitions of the role concept do not consider it, so that the states or phases of an object ....
....However, since it defines types exclusively in terms of their instances and the roles they play, it is purely extensional and misses the distinction between natural and role types. Building on the object role model Nijssen s information analysis method (NIAM) 33] and its descendants [34] provide a deeper account of the linguistic role of roles: they employ so called fact types which are the direct equivalents of linguistic statements associating properties with and expressing the relationships of objects, as the sole data structure. Each fact type involves a number of roles which ....
[Article contains additional citation context not shown here]
T.A. Halpin, H.A. Proper, Subtyping and polymorphism in object-role modelling, Data & Knowledge Engineering 15 (1995) 251481.
....However, since it defines types exclusively in terms of their instances and the roles they play, it is purely extensional and misses the distinction between natural and role types. Building on the object role model Nijssen s information analysis method (NIAM) 33] and its descendants [34] provide a deeper account of the linguistic role of roles: they employ socalled fact types which are the direct equivalents of linguistic statements associating properties with and expressing the relationships of objects, as the sole data structure. Each fact type involves a number of roles which ....
....of their extensions resulting from a difference in the static and the dynamic viewpoint. Consequently, they regard Product (which would be a role) as a generalization of House and Car [70] and Student, which is the prototypical role, as a specialization (in the usual sense) of Person [34]. Hence, this distinction does not add to the clarification of the relationship between roles and types. The solution, clearly, lies in the separation of types and roles. If the type and role hierarchy are different hierarchies, none of the aforementioned problems related to subtyping occurs. For ....
TA Halpin, HA Proper "Subtyping and polymorphism in object-role modelling" Data & Knowledge Engineering 15 (1995) 251--281.
No context found.
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in ObjectRole Modelling. Data & Knowledge Engineering, 15:251--281, 1995.
No context found.
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in Object-Role Modelling. Data & Knowledge Engineering, 15:251--281, 1995.
No context found.
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in ObjectRole Modelling. Data & Knowledge Engineering, 15:251--281, 1995.
No context found.
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in ObjectRole Modelling. Data & Knowledge Engineering, 15:251--281, 1995.
No context found.
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in Object-Role Modelling. Data & Knowledge Engineering, 15:251--281, 1995.
No context found.
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in Object-Role Modelling. Data & Knowledge Engineering, 15:251--281, 1995.
No context found.
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in Object-Role Modelling. Data & Knowledge Engineering, 15:251--281, 1995.
No context found.
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in Object-Role Modelling. Data & Knowledge Engineering, 15:251--281, 1995.
No context found.
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in Object-Role Modelling. Data & Knowledge Engineering, 15:251--281, 1995.
No context found.
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in Object-Role Modelling. Data & Knowledge Engineering, 15:251--281, 1995.
No context found.
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in Object-Role Modelling. Data & Knowledge Engineering, 15:251--281, 1995.
No context found.
Halpin, T.A. & Proper, H.A. 1995, `Subtyping and polymorphism in Object-Role Modelling', Data and Knowledge Engineering, North-Holland (to appear).
No context found.
Halpin, T. & Proper, H. 1995, `Subtyping and polymorphism in object-role modelling', Data & Knowledge Engineering 15, 3 (June), 251-281.
....define what an ORM schema is and, even more importantly, the (linear) path expressions need to be introduced as they form the backbone of the query by navigation system. We base ourselves on the formalisation of the path expressions as provided in [HPW93] and the formalisation of ORM given in [HP95] 3.1 ORM Schemas A conceptual schema is presumed to consist of a set of types . Within this set of types two subsets can be distinguished: the relationship types , and the object types . Furthermore, let be the set of roles in the conceptual schema. The fabric of the conceptual schema is then ....
....3. Using we can define the notion of type relatedness: for object types and . This notion captures the intuition that two object types may share instances. This relation is defined by the following four derivation rules: 1. 2. 3. 4. Note that when using ORM with advanced concepts ( HPW93] HP95] such as sequence types, set types, etc. the definition of needs to be refined. 3.2 Linear Path Expressions The central aspect of query by navigation are the (linear) path expressions ( HPW93] These expressions are build from (object) types, roles, and instances. For query by navigation in ....
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in ObjectRole Modelling. Data & Knowledge Engineering, 15:251--281, 1995.
....(ORM) schemas. This article focusses on schema transformations involved in classes 2 and 3. Furthermore, we limit ourselves to ORM models. This latter limitation, however, is not a strong one as the ORM modelling technique is general enough to cater for ER based data schemas as well ( BBMP95] HP95] In [CH94] Cam94] and [CP96] it is shown how ER can be regarded as an abstraction from ORM schemas. Research is also underway (together with the authors of [BW92] to find an apt schema language to describe both data schemas as well as database schemas. This would allow us to describe the ....
....completes our discussion of a small potpourri of schema transformations. As stated before, a wider range of schema transformations can be found in [Hal89] and [Hal95] 4 Conceptual Schema Universe Even though formalisations of ORM have been published before ( Hal89] HW93] HPW93] BBMP95] HP95] we provide such a formalisation once more to be self contained. However, in this formalisation we limit ourselves to syntactical issues only. Issues regarding semantics can be found in the referenced publications. Furthermore, a related formalisation is provided in [CP96] The formalisation ....
[Article contains additional citation context not shown here]
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in Object-Role Modelling. Data & Knowledge Engineering, 15:251--281, 1995.
....language for the query by construction part will result. 3 A Conceptual Schema as a Graph For the purpose of finding a path between object types in a conceptual schema, the schema first needs to be translated to a graph. We start out from a formalisation of ORM based on the one used in ( HP95] However, since only a very limited part of the formalisation is needed, we do not cover the formalisation in full detail. A conceptual schema is presumed to consist of a set of types . Within this set of types two subsets can be distinguished: the relationship types , and the object types . ....
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in ObjectRole Modelling. Data & Knowledge Engineering, 15:251--281, 1995.
....of finding a path between object types in a conceptual schema, the schema first needs to be translated to a graph. This translation is exactly the same as provided in [Pro94b] but for reasons of completeness we provide it again. We start out from a formalisation of ORM based on the one used in ( HP95] However, since only a very limited part of the formalisation is needed, we do not cover the formalisation in full detail. A conceptual schema is presumed to consist of a set of types . Within this set of types two subsets can be distinguished: the relationship types , and the object types . ....
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in ObjectRole Modelling. Data & Knowledge Engineering, 15:251--281, 1995.
....of the ORM concepts needed. Although the example generation tool will initially be used in the context of DBCreate (value types, entity types and binary relationship types) we already allow for ORM schemas as used by InfoModeler. We start out from a formalisation of ORM based on the one used in ([HP95]) However, since only a limited part of the formalisation is needed, we do not cover the formalisation in full detail. 2.1 ORM Basis A conceptual schema is presumed to consist of a set of types . Within this set of types two subsets can be distinguished: the relationship types , and the object ....
..... Using we can define the notion of type relatedness: for object types and . This notion captures the intuition that two object types may share instances. This relation is defined by the following four derivation rules: 1. 2. 3. 4. Note that when using ORM with the advanced concepts ([HP95]) such as polymorphism, sequence types, set types, etc. the definition of needs to be refined. Instances of all non value types must be identified in terms of instances of other object types. This identification is usually provided by a so called reference schema. If denotes the set of value ....
[Article contains additional citation context not shown here]
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in Object-Role Modelling. Data & Knowledge Engineering, 15:251--281, 1995.
....One could perhaps add a derived Boolean isLarge attribute, with an associated derivation rule in OCL, and then add a final subtype definition in OCL, but this would be less readable than the ORM definition above. For a detailed ORM perspective on these and other subtyping issues see [9, 14]. Meta modeling Because of ORM s greater expressive power, it is reasonably straightforward to capture UML models with an ORM framework. Though less convenient, it is possible to work in the other direction as well. To begin with, UML s graphic constraint notation can be supplemented by textual ....
Halpin, T. & Proper, H. 1995, `Subtyping and polymorphism in object-role modelling', Data & Knowledge Engineering 15, 3 (June), 251-281.
....process was given in [18] Meanwhile, new research has led to refinements of the original PSM model. In [40, 41] a new class of constraints is proposed that allows for a reduction of the number of constructs. Research into the relationships between ORM and other information modelling techniques [7, 35, 45, 33, 27] has led to a better understanding of the underlying constructs and their mutual relationships. Finally, in [19] an Object Role Modelling version was proposed, the Conceptual Data Modelling Kernel (CDM Kernel) which tries to put all these results into perspective. A key feature of the CDM Kernel ....
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in Object-Role Modelling. Data & Knowledge Engineering, 15:251--281 (1995).
....but are ignored in UML, DFFRXQW1U DQN 3HUVRQ DQN #QDPH# FFRXQW X FFRXQW1U 3HUVRQ #FXVWQU# LV#LQ KDV LV#XVHG E XVHV UML ORM #### A comparison of UML and ORM for data modeling 11 leading to the possibility of inconsistent UML models. For further discussion on these issues see [11, 15]. ORM includes a number of other graphic constraints with no counterpart in UML. For example, ring constraints such as irreflexivity, asymmetry, intransitivity and acyclicity, may be specified over a pair of roles played by the same object type (e.g. Person is parentof Person is acyclic and ....
Halpin, T. & Proper, H. 1995, `Subtyping and polymorphism in object-role modelling', Data & Knowledge Engineering 15, 3 (June), 251-281.
....such as exclusion and totality are typically implied by subtype definitions in conjunction with existing constraints on the supertypes; these implications are captured in ORM but are ignored in UML, leading to the possibility of inconsistent UML models. For further discussion on these issues see [12, 16]. ORM includes a number of other graphic constraints with no counterpart in UML. For example, ring constraints such as irreflexivity, asymmetry, intransitivity and acyclicity, may be specified over a pair of roles played by the same object type (e.g. Person is parent of Person is acyclic and ....
Halpin, T. & Proper, H. 1995, `Subtyping and polymorphism in object-role modelling', Data & Knowledge Engineering 15, 3 (June), 251-281.
....The reason for choosing ORM over the more popular Entity Relationship (ER) Che76] family of data modelling techniques is that ORM is a richer modelling language. Meanwhile, ORM also has a well established history of formalization using different styles [Hal89, Hal90b, BHW91, HW93, BBMP95, HP95, CP96, HLF96] making it an interesting case to study. Although formalizations of the syntax of an information modelling technique are important, they tend to be relatively simple. Most information modelling techniques have a fairly straightforward syntax. Formalization of semantics, if done at ....
....two roles. In a subsequent example an example of a ternary relationship will be shown. Relationship types may also be objectified, which means that they may play roles in other relationship types. Many conceptual data modelling techniques offer concepts for expressing inheritance of properties [HP95] In the literature many forms of inheritance have been documented, and terminology is far from being standardized. In this section we only use the subtyping construct as it is used in an ORM context. Subtyping is used when specific facts are to be recorded for specific instances of an object ....
T.A. Halpin and H.A. Proper. Subtyping and Polymorphism in Object-Role Modelling. Data & Knowledge Engineering, 15:251--281, 1995.
First 50 documents
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