Workshop Goals and Scope

The Web is undergoing dramatic change with the promise of faster mobile communications and richer means of interaction. This workshop will examine the trends and bring together people involved in the disparate areas relevant to the convergence of the Mobile Web and Interactive Voice Response systems.

The workshop will seek to discuss questions such as:

• What are the opportunities for convergence between W3C and WAP standards as we move forwards to third generation mobile networks?
• What can we learn from WML and VoiceXML? Is a common dialog modeling language needed?
• What architectures will be appropriate for multimodal systems where users can interact via a mixture of speech (recognition and synthesis), audio, displays, keypads and pointing devices (point and speak). How will these address accessibility concerns?
• What is the relationship between dialog modelling and synchronized multimedia presentations (SMIL)? What opportunities do mobile systems offer for scalable vector graphics, animation and streaming media?
• What approaches make sense for application state management? How does this relate to other Web applications such as VoiceXML and XForms?"
• What is the relationship between the browser and the application? How does this relate to user preferences? Is there a need for standardization to avoid problems with porting applications developed for one vendor's phones to another's?
• The display capabilities are expected to vary significantly. What kinds of changes (if any) may be appropriate in order for W3C's Cascading Style Sheets language to meet the challenge? Is there a role for simple constraint-based layout?
• What is needed to ensure that applications are accessible to people with disabilities, and how can this be facilitated via Web content guidelines?

Expected audience

We expect several groups will be interested in the workshop:

• Experts in mobile systems, who wish to explore the challenges presented by the convergence of Mobile and Interactive Voice Response systems.
• Experts in Interactive Voice Response systems with an interest in how these can exploit mobility and the opportunities for multimodal systems.
• Experts in synchronized multimedia presentations, interested in how these can be supported in mobile applications
• Experts in style sheet languages who are interested in the issues arising from an emerging new class of mobile devices.
• Experts in WAI guidelines and related tools (WAI Evaluation and Repair groups), including expert users with disabilities.
• WAP engineers working on transformation of generic Web content to WAP devices (e.g WML).

Registration and rules for participation

Registration has closed!

Draft Agenda

We have prepared a draft agenda, which attempts to balance the time we have available across presentations, break-outs and plenary sessions. We hope to generate ideas on how existing or new standards committees/working groups can solve the major issues identified by the workshop, and to suggest future actions.

Position Papers

Here is a list of position papers and statements that we have received as of 17th August 2000.

All attendees should review the position papers PRIOR to the workshop. A "10 minute summary" consists of a five minute presentation followed by 5 minutes of clarifying Q&A.

Position papers are a springboard for discussion at the workshop and we expect that the dialog should go well beyond what is in the position papers. You should submit one to the Program Committee prior to registering.

A position paper is usually short, around 1 to 4 pages (there is a maximum of five pages, or 27000 characters) and summarizes:

• What are the needs of your company/organization that you would like to have addressed in the Workshop.
• What are your general expectations on the final outputs of the workshop
• Your potential contributions to the discussion, related ideas, and suggested solutions. In the case of a well-defined technical contribution, this may be accompanied to the position paper as a separate paper, that may exceed the 5 pages limit.

Position papers will be published on the public Web pages of the workshop, so position papers and slides of presentations must be available for public dissemination. Submitting a position paper comprises a default recognition of these terms for publication.

All participants will be asked to briefly introduce their interest statement orally during the workshop.

The Programme Committee will ask the authors of particularly salient position papers to explicitly present their position at the workshop to foster discussion. In this case, the authors are also required to make the slides of the presentation available on the workshop Web site.

It is required that every member or organization represented at the workshop submit a position paper. Position papers should be submitted via email to the Workshop Program Committee prior to registering. Allowed formats are HTML and ASCII. Papers in other formats will be returned, with a request for correct formatting. Good examples of position papers can be seen in the QL'98 workshop.

Workshop organization

The workshop will last for two days. The first day will consist of presentations setting out the technology and business directions. The second day will focus on what steps are needed to take the ideas further in the W3C and the WAP Forum.

Hotel Details

The meeting will take place in Island Shangri-La, Hong Kong. If this is full, you may find rooms at the nearby JW Marriott.

Island Shangri-La Hong Kong
Pacific Place, Supreme Court Road
Central, Hong Kong
852 2877 3838 Direct Hotel Number
852 2820 8517 Reservation Number (ask for Nouvelle Ho)
852 2918 4820 Fax Reservation Number

JW Marriott Hotel Hong Kong
Pacific Place, 88 Queensway
Central, Hong Kong
(852) 2841 8366 Direct Hotel Number
(852) 2845 0707 Direct Fax Number

About the Programme Committee

Dave Raggett is a W3C Fellow on assignment from Hewlett Packard. He is the W3C activity lead for work on HTML, XForms, Voice Browsers and Math. Dave has been closely involved in Web standards since 1992, and is an author of several books on HTML as well as maintaining W3C's open source tool for repairing HTML (HTML Tidy).

Alastair Angwin chairs the WAP Forum's Application Environment committee, working on assignment from IBM.

Daniel Dardailler joined the W3C team in July 1996 and is the Technical Manager of W3C's Web Accessibility Initiative. He is also the site manager of the W3C INRIA-Sophia Antipolis team and site.

Jim Larson chairs the W3C Voice Browser working group which is developing markup languages for speech dialog, grammar, text to speech, natural language semantics, multimodal dialogs, and reusable dialog modules. Jim also manages Advanced Huan I/O at Intel Architecture Labs, and teaches courses in building speech applications at Oregon Graduate Institute and Portland State University.

Andrew Scott leads the WML Generic Content Authoring Guidelines (GCAG) effort within the WAP Forum's Developer Group (WDG). He is based at Telstra's Research Labs, and has worked on WAP-related activities since 1997. In addition to WAP, he has worked on transcoding generic web content, voice browsers, and with the usability team at Telstra.

Johan Hjelm is a W3C Fellow working on assignment from Ericsson. Johan chairs the W3C's CC/PP working group, which is trying to define a universal profile mechanism for information appliances and contextual information.

Hidetaka Ohto is a W3C Fellow working on assignment from Matsushita Electric Industrial Co.,Ltd(a.k.a Panasonic) in Osaka. He graduated from the University of Osaka in Japan with his master degrees of Computer Science in 1989. His area of interests is the adaptation of Web technologies for home appliances such as mobile terminals and TV sets.

Further Reading

• Information about the WAP Forum
• W3C's home page
• W3C's HTML activity
• W3C's voice browser activity
• W3C's work on next generation forms (XForms)
• W3C's synchronized multimedia activity
• W3C's style sheet activity
• W3C's graphics activity
• Web Content Accessibility Guidelines Recommendation
• Authoring Tools Accessibility Guidelines Recommendation
• User Agent Accessibility Guidelines Recommendation
• WAI Quicktips
• XML Guidelines

Also look at the HTML 4.0 Guidelines for Mobile Access