Demo Data from EDBT 2026 / reviewers in the wild / expert
Markian M. Gooley
dblp:76/4416
· DBLP profile ↗
2ranked-venue papers
2as first author
0since 2021 · last 1989
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Databases, data management, data science and information retrieval · 2 · 2 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.
| Software engineering, system software, and programming languages
2 papers |
Compilers and program optimization · 50% Programming languages and type systems · 50% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Programming languages and type systems
logic programming |
0.0 | 2 | 1989 | Efficient Reordering of Prolog Programs · IEEE Trans. Knowl. Data Eng. 1989 Efficient Reordering of Prolog Programs · ICDE 1988 |
Compilers and program optimization
logic program optimization |
0.0 | 2 | 1989 | Efficient Reordering of Prolog Programs · IEEE Trans. Knowl. Data Eng. 1989 Efficient Reordering of Prolog Programs · ICDE 1988 |
Methods — techniques the papers use, named apart from their topics
mode inference · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1989 | Efficient Reordering of Prolog ProgramsabstractProlog programs are often inefficient: execution corresponds to a depth-first traversal of an AND/OR graph; traversing subgraphs in another order can be less expensive. It is shown how the reordering of clauses within Prolog predicates, and especially of goals within clauses, can prevent unnecessary search. The characterization and detection of restrictions on reordering is discussed. A system of calling modes for Prolog, geared to reordering, is proposed, and ways to infer them automatically are discussed. The information needed for safe reordering is summarized, and which types can be inferred automatically and which must be provided by the user are considered. An improved method for determining a good order for the goals of Prolog clauses is presented and used as the basis for a reordering system.> Markian M. Gooley, Benjamin W. Wah |
IEEE Trans. Knowl. Data Eng. | 1 |
| 1988 | Efficient Reordering of Prolog ProgramsabstractThe authors show how reordering of Prolog clauses, and especially goals, can prevent unnecessary search. They characterize the restrictions on reordering and show how they may be detected. They design a system of calling modes for Prolog, geared to reordering and discuss ways to infer them automatically. They present an improved method for determining a good goal order for Prolog clauses, and use it as the basis for a reordering system, showing how it can be guided by information about modes and restrictions to generate reordered Prolog that behaves correctly.> Markian M. Gooley, Benjamin W. Wah |
ICDE | 1 |