Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page
Demo Data from EDBT 2026 / reviewers in the wild / expert

Thomas J. Parenty

dblp:08/425 · DBLP profile ↗
← Back
3ranked-venue papers
1as first author
0since 2021 · last 1995
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Security and privacy · 2 · 1 first-authorDatabases, 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
Operating systems · 100%
Network and information security
1 paper
Systems and software security · 100%

Topics — the 3 heaviest of 4, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Systems and software security
multilevel security		 0.011989
The Incorporation of Multi-Level IPC into UNIX · S&P 1989
Operating systems
interprocess communication		 0.011989
The Incorporation of Multi-Level IPC into UNIX · S&P 1989
Operating systems › operating system interface › system call
UNIX system calls		 0.011989
The Incorporation of Multi-Level IPC into UNIX · S&P 1989

Methods — techniques the papers use, named apart from their topics

system call extension · 0.0runtime library modification · 0.0
YearPublicationVenuePosition
1995 Customer Requirements for Security in Relational Database Management
Marvin Schaefer, Ronda R. Henning, Roger L. Miller, Thomas J. Parenty, Jesse C. Worthington
 DBSec4
1989 The Incorporation of Multi-Level IPC into UNIX
abstract
The author discusses the design, interface, and implementation issues that need to be addressed for Unix to support multilevel synchronized file access, pipes (FIFOs), messages, and semaphores. It is shown that, by changing some of Unix's underlying mechanisms and by making additions to system calls and the run-time library, it is possible architecturally to support more flexible sharing and communication. This increased sharing simplifies the building of multilevel applications, both trusted and untrusted, to run on top of Unix.>
Thomas J. Parenty
 S&P1
1985 A comparison of a network structure and a database system used for document retrieval
W. Bruce Croft, Thomas J. Parenty
 Inf. Syst.2