Rationale
The workshop was intended to focus on
concepts and requirements for high-level API
suitable for developing Web-aware applications.
An explicit goal of the workshop was to publish
state of the art references to existing APIs.
The papers that were submitted covered a wide range of interests,
including computation models, applications and user
requirements, software architectures and libraries
as well as heuristics and guidelines for API developers.
Rationale
- Computation Models
-
[Model], [DOOWWW], [CAMEO], [HIPPO], [V6]
- Applications and Users
-
[Meta], [UOD], [URA], [VAPIS], [VEMMI] , [Tele]
- Software Architecture
-
[W3CReference], [V6],
[Broker], [CAMEO], [DejaVu], [Jigsaw], [FastCGI]
- Heuristics and Guidelines
-
[W3CReference], [Configure], [VAPIS]
slide: Rationale
As can be expected opinions diverged
on many of the issues, even the need for APIs
to exist at all.
To get the flavor of the positions presented
by the participants, some of the points put forward
are listed below:
- APIs should be layered, open-ended, thread-safe,
platform-independent, ...
- Configuration must be part of API.
- APIs must provide support for monitoring, notification
and triggering.
- APIs should be avoided -- instead filter composition
devices should be used.
- APIs should provide for callbacks, plug-ins, ...
slide: Positions
A summary of the papers can be found
together with the list of
participants.