Complaints
- lack of referential integrity
- undetected failures
- no control over quality of service
Observations
- dynamic quality of services
- complex interaction
Requirements
- uniformity, openness, flexibility, orthogonality, layered
Behavior
- reliable, configurable, monitoring, notification, thread-safe
Answers
slide: Requirements for APIs
Actions
- define a distributed model of computation that suits the Web.
- define canonical (language-independent?) object models for ... resources, application domains ...
Perspectives
- servers - extensions
- browsers - clients, viewers, configuration
- agents - e.g. payment
Interests
- distributed objects
- plugin components
- formalization of requirements and solutions
slide: Dimensions of APIs
- intelligent navigation and information retrieval,
- information and document maintenance,
- user interfaces for Web-aware applications,
- dynamic documents with user-defined applets,
- declarative descriptions of agent behavior based on user preferences,
- declarative modeling of coordinated and cooperative behavior of software agents, and
- programming single and multi-agent systems.
- modeling the behavior of cooperating agents,
- generic means for realizing actual agents in a Web-aware context,
- architectural support for programming agent-based systems.
Framework components
Web-aware agents
- a methodology for developing agent-based applications, as well as
- a logical foundation for modeling agent behavior; and in addition
- guidelines for realizing actual agent applications, and
- software components that can be used as building blocks, including
- a language for programming agent behavior.
slide: Framework components