ACM SIGCHI General Interest Announcements (Mailing List)


Options: Use Forum View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
text/plain; charset="us-ascii" ; format="flowed"
"ACM SIGCHI General Interest Announcements (Mailing List)" <[log in to unmask]>
Peter Brusilovsky <[log in to unmask]>
Thu, 10 Oct 2002 00:39:17 -0400
Peter Brusilovsky <[log in to unmask]>
text/plain (144 lines)

         9th International Conference on User Modeling


                   June 22 to June 26, 2003
        University of Pittsburgh Conference Center
               Johnstown, Pennsylvania, USA


A workshop should yield tangible results of lasting value. Such a
workshop yields a better return on the investment of the organizers
and participants than the more frequent "miniconferences" that offer
little more than a series of loosely related, noninteractive

To this end, each workshop should have the goal of answering a
small number (e.g., 3) of questions that have been formulated in
advance by the organizers. These questions will play a key role
in focusing the workshop's organization in all phases:

1. The questions should be submitted as part of the workshop proposal.

2. Authors submitting contributions to the workshop should be
required to address at least one of the questions explicitly.

3. During the workshop, the contributions made to the questions
should be collected (for example, on a whiteboard or in the form
of slides made during the workshop).

4. The final part of the workshop (e.g., 1 hour) should be
devoted to an integrative discussion of the questions that yields
at least tentative answers.

5. At the beginning of the main conference program, the
organizers of each workshop will be given an opportunity to
summarize the results of their workshop in a presentation. This
summary should present the questions that were addressed and
summarize the answers that were worked out.

6. The web site summarizing the results of the workshop should
likewise be organized in terms of the questions and answers.

An example of a workshop organized along these lines - whose
results are still of interest 5 years later - is the workshop on
*Usability Testing of World Wide Web Sites* that was held at
CHI 97:


Each proposal should be 2-4 pages in length and should contain at least
the following information:

- *Background and Motivation:* What is the overall topic of the
workshop? Why is this topic of particular interest at this time?

- *Questions to Be Addressed:* Identify the specific questions on
which the workshop will focus (see the section *Question-Oriented
Organization* above). For clarity, each question should be
formulated explicitly as a complete sentence that ends with a
question mark. For example, for a workshop on "Learner Control in
Student Modeling", one question might be: "Which student modeling
methods make it especially difficult to provide control to

- *Format:* Give a description of the proposed workshop format,
specifying the mix of events such as position statements, invited
talks, panels, demos, and general discussion. Indicate whether
the intended duration is a half day or a full day.  State how
participants and presentations will be recruited and
selected. Make it clear that the workshop will have a
question-oriented organization and that it will not be just a

- *Potential Participants:* State your estimate of the number of
participants. If possible, give a list of tentatively confirmed

- *Organizers:* List the names and the full contact information
of each of the organizers, and give short descriptions of their
relevant expertise and experience.


The organizers of a workshop will be responsible for:

- Producing and distributing a Call for Participation. It should be
made clear that all workshop participants are required to register for
both the UM'03 conference and for the workshop.

- Selecting the workshop participants and the contributions to be
included in the workshop proceedings.

- Producing a one-page abstract for inclusion in the conference

- Scheduling and coordinating the activities of the workshop.

- Producing the workshop notes. The notes must be distributed in
printed form to the workshop participants at the conference site,
at or before the beginning of the workshop.  They must also be
made available to interested nonparticipants, both on the web and
in printed form (e.g., as a technical report).

- Presenting a summary of the workshop's results at the beginning
of the main conference program.

Creating and maintaining a web site that contains the materials
from the workshop and a summary of its results.


Proposals should be submitted electronically in a
platform-independent format (e.g., plain text or PDF) to the
workshop cochairs:

Frank Wittig, [log in to unmask]
Anthony Jameson, [log in to unmask]

All proposals will be reviewed by members of the Program
Committee. Workshop organizers are invited to submit a tentative
draft proposal by November 11th, 2002. These drafts will be used
for the advance identification of proposals with overlapping
topics.  In such cases, the organizers may invited to cooperate
and to coordinate their efforts.


November 11, 2002 Deadline for tentative workshop proposals
November 25, 2002 Deadline for final workshop proposals
December 9, 2002    Notification of acceptance
December 16, 2002  Delivery of the workshop's Call for Participation
May 12, 2003           Delivery of an electronic version of the workshop
June 22, 2003          Workshop date