Present: John U., Stefan, Stan, Matt K., Amit, Loretta, Catherine, Bob Taylor, John Smith, and (Toronto) Michelle D'Souza, Shaw-Han, Barbara Glover.

About Fluid:

• Library of components, as well as a user toolkit.

• Toolkit: reusable items such as scenarios, personas, and walkthroughs. A "design pattern" is a template for building interactions; cf. Christopher Alexander's work on architecture.

• Augmenting earlier generations of interfaces in Sekai.

• Components: J-query base library; first component is dragndrop widget;

How much is server side interaction vs. client side; MONK relies on a client side library with interface widgets and a data access layer on top; client vs. server is still in flux with Fluid;

How many components are there? One component and one library service; design team is now planning several more components; content management component; tag cloud component; portal favorites; file ticker; inline editing component; these are all about a year out.

"Component": a Fluid component might consist of a number of widgets, user workflow

Amit and Stefan described MONK components.

Consensus on keeping conversation going.