This paper reports on a small experiment, which although relatively simple, raises important issues about ProcessModel User Interfaces. It outlines an approach to the exploitation of the World Wide Web by Process-centred Software Support Environments. It concludes that there is great advantage to be gained from designing process systems so that they are more reactive and rather less prescriptive than the current generation of such systems.

Reflection has been used to address many different problem areas, and the term reflection has itself been used to describe several distinct processes. This paper identifies three simple operations, generation, raising and dynamic rebinding, which may be composed to yield several varieties of reflection. These can be used to allow a self-contained programming system to evolve, through the incorporation of new behaviour into either the application programs or the interpreter which controls their execution. Reflection is a powerful mechanism and potentially dangerous. Used in the context of persistent programming systems, safety is an important consideration: the integrity of large amounts of data may be at stake. This has led to the use of type checking in conjunction with reflection in such systems to provide some guarantees of safety. The paper describes the nature of reflection in persistent systems and identifies some example applications. 1