Suggestion: "end user programming languages for the web" top-level section really contains systems chapters.  They should be refiled in with the other systems chapters under "Systems and Applications".

Suggestion: divide chapters by whether they are about data or interaction.

Original proposal:

0. Introduction

Cypher – History of EUP

Miller – Why users customize

I. End User Programming Languages for the Web

Little – Sloppy Programming

Van Kleek – AtomsMasher

Jung – PLOW

Miller – Chickenfoot (system)

Faaborg – Creo (system)

II. Systems and Applications

Mashups

Wong – Mashup Lens

Fujima – Clip, Connect, Clone (system)

Wong – Marmite (system)

Ennals – MashMaker (system)

Task Assistance

Lau – CoScripter (system)

Brandt – d.mix (system)

Nichols – Highlight (system)

De Roure - Taverna / myExperiment.org

Visualization

Lunzer – Subjunctive Interfaces

Dontcheva – Web Summaries (system)

Adar – Zoetrope (system)

Accessibility

Bigham – Accessibility

Borodin – Social Accessibility

III. Data Management and Interoperability

Karger – Common Data Model

Haines – Cross-application

Lieberman – Commonsense knowledge

IV. User Studies

Studies of End Users

Zang – Mashup Users

Jones – Debugging Mashups

Studies of Communities

Budweg – How EU communities evolve

Scaffidi – Code ReUse

Barbosa – Co-operation