WWW8 Developer's Day Information
Last Update: 16 February 1998

Developer's Day 1999
Overview for Session/Track Chairs

1. Track/Session Requirements

Like many projects, this one begins with a list of requirements for sessions and presentations at WWW8's Developer's Day.. These are:

The last condition is implied by the WWW8 program, which targets accessibility to Internet resources by users with physical or other impairments as an important principle of Web development.

2. Things that Do Not Belong in DDay sessions

No Activity Reports/Summaries. The developer day presentations should not include W3C (or other organization's) activities reports or summaries, as this information is, in general, sufficiently well covered in the regular conference sessions, and does not bear repeating here
No Panels or Discussion Sessions. Please avoid having sessions that consist of panel discussions -- they tend to work poorly unless well focused, and this rarely happens at a Developer's Day. A Panel may be relevant as a discussion forum that follows-up a particularly controversial presentation or presentations.

The next sections describe how Developer's day will run, on a practical level.

3. Session Organization

Physical Organization -- Developer's day will consist of eight parallel session. Each session having it's own session chair. It will be the chair's responsibility to recruit participants to their session, and to moderate the presentations at the session. I suggest a mix of 30 and 45 minute sessions, and also suggest that at least one of these sessions be reserved for a "topical interest" discussion -- wherein a presenter provides a short (5-10 minute) presentation on a particularly controversial issue related to the session topic, with the remaining time devoted to debate on this issue.

The organization of the day is given in the associated schedule document.

Logical Organization -- Because the sessions are supposed to be timely, and based on actual software development-in-progress, it is unreasonble to have participants provide detailed abstracts or presentation papers long before their presentations. I thus propose the following model, based on the succesfull approach I have seen at several other "Developer Day" conferences:


Ian Graham
Centre for Adaptive and Academic Technology
University of Toronto
Last Update: 16 February 1999