Table of Contents

publication notes

Practicalz

Content organisation: design feel

Some words to spice yr appetite: So there was talk about the publication being loosely structered as a cook book…and so it will be! We like the process of cooking because it is basically about selected things coming together, preparation, care and combination under certain conditions (heat, cooking utsensils, the slicing, spicing, choice of cooking method)…ideally this leads to a wonderful dish. The raw ingredients somehow evolve or grow into a dish by performing a whole array of actions. Now this is very much conform to what txOom does as a project, but also how it came about: it is very much about getting the ingredients, mixing of flavours, blending of different disciplines and skills, and accomodating tastes, competences, creativity in this large pot. txOom as an environment, but also the working process, is very much about active participation…the same is true for cooking. This sounds as a tasty idyllic story, BUT as all the different dependency charts, workshop notes, email excerpts show, cooking up a project like this is also fragile and extremely complex. In other words; if you if you leave your cake too long in the oven it'll burn, und so weiter. So far for allegories.

Content organisation: structure

The chapers will be organised in cooking actions, which as you proceed through the book will take you from initial ingredients to the preeparation of the dish, and the dish as such. In other words, as you proceed the matter solidifies (or becomes more tangible/concrete), or the ingredients, if you will, change consistency. The more you proceed in the book the more solid, concrete, a whole it becomes. A gradual morphing from ideas to project, to put it in a mundane way. e.g. the first chapters may show very sketchy designs of the costumes/spaces, and as you proceed these designs literally start to take more form and more colour.

CHAPTERS

max. of 7 chapters (?) drawing on cooking methodology, loosely conveying the following

So eventually everything comes full circle.

SUBCHAPTERS

subchapters should be identified by icons symbolising the public event/project activity at the beginning or end of the text.

txOom is a project that had a lot of public events and development workshops. although we don't want to organise the book chronologically, or by event, it should be clear which text belongs to which event/project activity. therefore, the chapters are further divided in texts describing (sub)projects (txOom Torino, Gt Yarmouth, Maribor, workshops…) )

THREADS (was layers - but threads are a more correct term?)

there are a lot of different disciplines involved in txOom - every discipline has their own language, their own writing style. if we want this book to appeal to different audiences, we should design it so that the different types of texts (say poetic stories or technical descriptions) can be clearly distinguished throughout the book - think of maybe using different font, spacing, text formatting… for different threads. the 4 threads that we found in the existing material are: )

LAYERS

the variety of material for the book demands a layered design, showing the 'thickness' of the project. the layout might need a lot of puzzling to make the following types of material into a pleasent and consistent whole: )

lina3-small.jpg

more images on Plot Illustrations

Preliminary list material txOom Publication

The material has been grouped per project for practical reasons, but this is NOT how we want to structure the book.

Txoom Torino

P~lot )

workshop Norwich

GLUE

Txoom -Great Yarmouth

Maribor

Info-ecologies

In Betweenz - closed development workshops

Coordination meeting bxl

Visby:

Bxl hardware integration workshop

Other

Estimate word count: 70.000

from meeting 20030130 (foam/bxl)

re: book

1)
insert nat's text list