Demo Data from EDBT 2026 / reviewers in the wild / expert
Fehime Nihan Kesim
dblp:40/1345
· DBLP profile ↗
1ranked-venue papers
1as 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 · 1 first-author
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.
| Theoretical computer science
1 paper |
Logic in computer science · 100% | |
| Databases, data mining, and information retrieval
1 paper |
Spatial and temporal data management · 77% Data models and query languages · 23% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Spatial and temporal data management
temporal databases |
0.0 | 1 | 1996 | A Logic Programming Framework for Modeling Temporal Objects · IEEE Trans. Knowl. Data Eng. 1996 |
Logic in computer science › knowledge representation and reasoning › knowledge representation
event calculus |
0.0 | 1 | 1996 | A Logic Programming Framework for Modeling Temporal Objects · IEEE Trans. Knowl. Data Eng. 1996 |
Logic in computer science
logic programming |
0.0 | 1 | 1996 | A Logic Programming Framework for Modeling Temporal Objects · IEEE Trans. Knowl. Data Eng. 1996 |
Data models and query languages › schema management
schema evolution |
0.0 | 1 | 1996 | A Logic Programming Framework for Modeling Temporal Objects · IEEE Trans. Knowl. Data Eng. 1996 |
Methods — techniques the papers use, named apart from their topics
negation as failure · 0.0event calculus · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1996 | A Logic Programming Framework for Modeling Temporal ObjectsabstractWe present a general approach for modeling temporal aspects of objects in a logic programming framework. Change is formulated in the context of a database which stores explicitly a record of all changes that have occurred to objects and thus (implicitly) all states of objects in the database. A snapshot of the database at any given time is an object-oriented database, in the sense that it supports an object-based data model. An object is viewed as a collection of simple atomic formulas, with support for an explicit notion of object identity, classes and inheritance. The event calculus is a treatment of time and change in first-order classical logic augmented with negation as failure. The paper develops a variant of the event calculus for representing changes to objects, including change in internal state of objects, creation and deletion of objects, and mutation of objects over time. The concluding sections present two natural and straightforward extensions, to deal with versioning of objects and schema evolution, and a sketch of implementation strategies for practical application to temporal object-oriented databases. Fehime Nihan Kesim, Marek J. Sergot |
IEEE Trans. Knowl. Data Eng. | 1 |