Demo Data from EDBT 2026 / reviewers in the wild / expert
Stewart Nickolas
dblp:84/3868
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 1996
—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 |
Requirements engineering and software design · 100% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Distributed systems · 100% |
Topics — the 3 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Requirements engineering and software design › software architecture
component-based software engineering |
0.0 | 1 | 1996 | Components on the Internet (Panel Session) · OOPSLA 1996 |
Requirements engineering and software design
software architecture |
0.0 | 1 | 1996 | Components on the Internet (Panel Session) · OOPSLA 1996 |
Distributed systems › distributed system architecture
client-server systems |
0.0 | 1 | 1996 | Components on the Internet (Panel Session) · OOPSLA 1996 |
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1996 | Components on the Internet (Panel Session)abstractThe explosive emergence of the Internet forces us to rethink the traditional roles for client, server, and objects. Component technology has emerged as the way objects and frameworks are packaged for flexible object integration. In particular, components allow users who are not programmers to do their own integration. Up until now, components have mainly focused on object integration on end-users desktops and on a client: compound documents, application assembly, etc.Existing component models like OpenDoc and Microsoft's OLE/OCX/COM provide function for compound documents, persistence, scripting, inking, and code management (registration). A series of Internet scenarios are emerging that demand new kinds of components. These scenarios are thin clients (Internet terminals), virtual reality/rich multimedia clients, collaboration, and business data access. Each panelist will explore one of these scenarios for it's requirements on an Internet component model. Jeffrey Bonar, Nancy Lehrer, Kelly Looney, Stewart Nickolas, James Russell, Randy Schnier, Ted Selker |
OOPSLA | 4 |