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

Jack P. Sanders

dblp:72/5036 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 1989
—ORCID · none

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

Computer networks · 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.

Computer networks
1 paper
Internet architecture and protocols · 100%
Software engineering, system software, and programming languages
1 paper
Services computing and microservices · 100%

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

TopicWeightPapersLastEvidence papers
Internet architecture and protocols
protocol design		 0.011989
A communications interface for systems application architecture · IEEE J. Sel. Areas Commun. 1989
Services computing and microservices › enterprise application integration
application integration		 0.011989
A communications interface for systems application architecture · IEEE J. Sel. Areas Commun. 1989

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

systems application architecture · 0.0interface design · 0.0
YearPublicationVenuePosition
1989 A communications interface for systems application architecture
abstract
The requirements for program-to-program communication that prompted the creation of the communications interface for IBM's Systems Application Architecture (SAA), the considerations that went into the design of its function, and the basic concepts of the interface are discussed. An example of two programs using the Communications Interface is also included. The authors conclude that the evolving SAA Common Programming Interface and the Communications Interface within it provide a programming environment of languages and services for development of application programs that span systems.>
Jack P. Sanders, Mel R. Jones, John E. Fetvedt, Marsha E. Ferree
 IEEE J. Sel. Areas Commun.1