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

Eric Harslem

dblp:73/3176 · DBLP profile ↗
← Back
2ranked-venue papers
1as first author
0since 2021 · last 1982
—ORCID · none

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

Computer networks · 1Software engineering, systems software and programming languages · 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
Software maintenance and evolution · 100%

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution
software evolution
0.011982
A Retrospective on the Development of Star · ICSE 1982
Internet architecture and protocols
ARPANET
0.011972
An Experimental Service for Adaptable Data Reconfiguration · IEEE Trans. Commun. 1972
Internet architecture and protocols
protocol design
0.011972
An Experimental Service for Adaptable Data Reconfiguration · IEEE Trans. Commun. 1972

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

interpreter · 0.0domain-specific language · 0.0compiler · 0.0
YearPublicationVenuePosition
1982 A Retrospective on the Development of Star
Eric Harslem, LeRoy E. Nelson
ICSE1
1972 An Experimental Service for Adaptable Data Reconfiguration
abstract
The ARPA computer network (ARPANET) is a nationwide network of diverse autonomous computers connected via a message-switching store-and-forward communications subnet using leased wide-band (50-kbit/s) telephone lines. A primary objective of the ARPANET is to share preexisting programs and data. Many of the difficulties of using remotely generated programs and data are found to be simple format incompatibilities requiring data manipulations like character set conversion, header prefacing and stripping, packing and unpacking of repeated data, generating counters and flags, and field transposition. The data reconfiguration service (DRS) is an attempt to provide a convenient way of performing these data manipulations in order to mediate between superficially incompatible data streams connecting existing programs in the ARPANET. Desiring to match two incompatible input-output streams, an applications programmer specifies a data stream transformation (called a form) written in the data reconfiguration language (DRL). Associating the appropriate form name with the connection between his two programs, the programmer causes the DRS to follow his instructions on how the specified data streams are to be manipulated in the communication required to make the two programs cooperate over the ARPANET. Components of the DRS include the specification of its special-purpose data reconfiguration language, a form compiler to translate forms into fast-running transformation programs, an interpreter to perform high-speed data transformations at application program run time, and a standard set of ARPANET protocols for the routine handling of connections and form specifications between operating systems.
Vint Cerf, Eric Harslem, John F. Heafner, Robert Metcalfe, James E. White
IEEE Trans. Commun.2