Demo Data from EDBT 2026 / reviewers in the wild / expert
Todd Matson
dblp:04/3563
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 1973
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 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 |
Concurrent programming · 67% Empirical software engineering · 33% | |
| Artificial intelligence
1 paper |
Knowledge representation and reasoning · 100% |
Topics — the 3 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Concurrent programming › concurrency models
actor model |
0.0 | 1 | 1973 | Actor Induction and Meta-Evaluation · POPL 1973 |
Concurrent programming
message passing |
0.0 | 1 | 1973 | Actor Induction and Meta-Evaluation · POPL 1973 |
Empirical software engineering › software engineering research methodology
meta-evaluation |
0.0 | 1 | 1973 | Actor Induction and Meta-Evaluation · POPL 1973 |
Methods — techniques the papers use, named apart from their topics
actor model · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1973 | Actor Induction and Meta-EvaluationabstractThe PLANNER project is continuing research in natural and effective means for embedding knowledge in procedures. In the course of this work we have succeeded in unifying the formalism around one fundamental concept: the ACTOR. Intuitively, an ACTOR is an active agent which plays a role on cue according to a script. We use the ACTOR metaphor to emphasize the inseparability of control and data flow in our model. Data structures, functions, semaphores, monitors, ports, descriptions, Quillian nets, logical formulae, numbers, identifiers, demons, processes, contexts, and data bases can all be shown to be special cases of actors. All of the above are objects with certain useful modes of behavior. Our formalism shows how all of these modes of behavior can be defined in terms of one kind of behavior: sending messages to actors. An actor is always invoked uniformly in exactly the same way regardless of whether it behaves as a recursive function, data structure, or process. Carl Hewitt, Peter Boehler Bishop, Irene Greif, Brian Cantwell Smith, Todd Matson, Richard Steiger |
POPL | 5 |