Demo Data from EDBT 2026 / reviewers in the wild / expert
Brigitte Röck
dblp:03/3515
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 1996
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Databases, data management, data science and information retrieval · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Programming languages and type systems · 100% | |
| Databases, data mining, and information retrieval
1 paper |
Data models and query languages · 100% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Data models and query languages
object-oriented database |
0.0 | 1 | 1996 | Extending Object-Oriented Systems with Roles · ACM Trans. Inf. Syst. 1996 |
Programming languages and type systems
object-oriented programming |
0.0 | 1 | 1996 | Extending Object-Oriented Systems with Roles · ACM Trans. Inf. Syst. 1996 |
Programming languages and type systems › object-oriented programming
inheritance and polymorphism |
0.0 | 1 | 1996 | Extending Object-Oriented Systems with Roles · ACM Trans. Inf. Syst. 1996 |
Programming languages and type systems
type systems |
0.0 | 1 | 1996 | Extending Object-Oriented Systems with Roles · ACM Trans. Inf. Syst. 1996 |
Methods — techniques the papers use, named apart from their topics
implementation · 0.0class hierarchy · 0.0class hierarchies · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1996 | Extending Object-Oriented Systems with RolesabstractIn many class-based object-oriented systems the association between as instance and a class is exclusive and permanent. Therefore these systems have serious difficulties in representing objects taking on different roles over time. Such objects must be reclassified any time they evolve (e.g., if a person becomes a student and later an employee). Class hierarchies must be planned carefully and may grow exponentially if entities may take on serveral independent roles. The problem is even more servere for object-oriented databases than for common object-oriented programming. Databases store objects over longer periods, during which the represented entities evolve. This article shows how class-based object-oriented systems can be extended to handle evolving objects well. Class hierarchies are complemented by role hierarchies, whose nodes represent role types an object classified in the root may take on. At any point in time, an entity is represented by an instance of the root and an instance of every role type whose role it currently plays. In a natural way, the approach extends traditional object-oriented concepts, such as classification, object identity, specialization, inheritance, and polymorphism in a natural way. The practicability of the approach is demonstrated by an implementation in Smalltalk. Smalltalk was chosen because it is widely known, which is not true for any particular class-based object-oriented database programming language. Roles can be provided in Smalltalk by adding a few classes. There is no need to modify the semantics of Smalltalk itself. Role hierarchies are mapped transparently onto ordinary classes. The presented implementation can easily be ported to object-oriented database programming languages based on Smalltalk, such as Gemstone's OPAL hierarchies are complemented by role hierarchies, whose nodes represent role types an object classified in the root may take on. At any point in time, an entity is represented by an instance of the root and an instance of every role type whose role in currently plays. Georg Gottlob, Michael Schrefl, Brigitte Röck |
ACM Trans. Inf. Syst. | 3 |