W3C home > Mailing lists > Public > www-di@w3.org > April 2005

CFP: Workshop on Device Independent Web Engineering

From: Lauff, Markus <markus.lauff@sap.com>
Date: Mon, 25 Apr 2005 16:46:36 +0200
Message-ID: <AE47510E478E7B419B622C671E70EF390221BF13@dewdfe23.wdf.sap.corp>
To: undisclosed-recipients:;undisclosed-recipients:;

2nd Workshop on
Device Independent Web Engineering <http://www.myclipboard.net/icwe05/>
(DIWE'05 <http://www.myclipboard.net/icwe05/> )
26. July 2005
in conjunction with
5th International Conference on Web Engineering
<http://www.icwe2005.org/>  (ICWE2005), Sydney

On this page: Objective - Motivation - Goals - Topics - Expected
Audience - Submission - Organizers - Deadlines


The objective of the workshop is to survey and analyze current web
engineering approaches and research concepts to create content and
applications for delivery across many kinds of presentation device. The
workshop also aims to capture best practices and to identify missing
components for the development of context-aware device independent
content and applications.


While the range of devices that are used to access the web continues to
grow, web applications are often developed having a specific delivery
context (incl. capabilities of the access mechanism, user preferences)
in mind. Based on the large variety of devices it is unreasonable to
expect that a web application that has been developed for this
configuration can be delivered in an acceptable way in another delivery
context, such as other kinds of devices (e.g. printers, phones, PDAs,
TVs, in-car systems) or voice-oriented systems.

To get an acceptable result, that takes into account the capabilities of
the  delivery context, the developer may end up creating multiple
versions of the  application. However, the cost of multiple authoring
for different configurations is high. 

The early binding of the targeted delivery context influences the
development in many areas: 

*	The functionality of the application (simple applications for
mobile devices and complex applications for desktop computers) 
*	The navigational/interaction structure (multidimensional,
hierarchical or sequential navigation) 
*	The layout and graphical representation (desktop, laptop, mobile
landscape or portrait) 
*	The markup language (based on the language supported by the

The disadvantage of most today's approaches is that the pre-selection 

*	limits the number of users (the ones who have the selected
*	shortens the lifetime of the application (as technology advances
pretty fast and the application can not benefit from these advances), 
*	delivers limited usability on other "compatible" devices, 
*	raises the need that the developers have to be trained for every
new device/markup/development environment and finally limits the number
of business cases for mobile web applications. 

While (coming from HTML) the ideal might be that a single version of
some content can be the basis for creating suitable presentations,
applications have to be adapted in multiple dimensions (e.g.
functionality, interaction paradigm, supported modality).

The 'single-authoring' ideal becomes a greater challenge given the
increased complexity and scope of interactive and multimedia websites.
Many developers try to maintain the quality of their application. The
challenge is to minimize development cost, maximize re-use, but still
ensure the user acceptance.  


The goals of this workshop are as follows:

*	To discuss the issues to be faced in development for multiple
delivery contexts and the techniques that can be used to address them 
*	To understand how existing standards can be used to achieve
greater device independence 
*	To identify areas where new concepts and further standards may
be needed in order to support greater device independence when
developing web applications 


Whereas last year, the Workshop on Device Independent Web Engineering
tried to get a broad overview on the various aspects, this year the
special focus of the workshop is on usability. Topics of the workshop

*	Web Engineering Modeling and Development of context aware
web-based applications 
*	Concepts for the (semi-)automatic measuring of usability 
*	Conceptual Modeling of adaptive/device independent (multimodal)
User Interfaces 
*	(META-) Markup languages supporting Device Independent
Application Development 
*	Development environments and tools supporting the technology
independent development and multi-channel deployment 
*	Advanced 
*	Reports on practical experience and reports investigating in the
usability of device independent applications 

Expected Audience

*	Researchers from Academia and Industry 
*	Representatives of Standardization Groups 
*	Content Management System Developers 
*	Web Information Systems Developers 
*	Web Engineers and Integrators 
*	Web Services Providers 
*	Web e-commerce Systems Developers 
*	Web Systems Network Designers 
*	Context Information Providers 

Submission Details

Prospective workshop participants are invited to submit a Position Paper
related to one (or more) of the workshop topics or an Interest

Position papers will be reviewed by the program committee as a basis for
selecting invited presentations to inform and initiate discussion at the
workshop. Position Papers should be at least 4 and no more than 10 pages
in length.

Submitted Position Papers must be written in English and not published
or submitted elsewhere. The submissions will be fully reviewed by two
reviewers and will be judged on the basis of originality, contribution,
technical and presentation quality, and relevance to the workshop. 

Workshop proceedings will be published in 2 formats: print and CD-ROM.
Print proceedings for the ICWE workshops will have ISBN numbers. 

Position Papers should be in IEEE Computer Society conference
proceedings format. Post workshop publication of accepted position
papers is being planned via a journal special issue. 

Interest statements should contain of a brief (maximum 500 word) text
description of the contribution you could make to the workshop,
including the topics you wish to see discussed.

Position Papers (in PDF) and Interest Statements (in plain text or PDF)
should be submitted via e-mail to Markus.Lauff@SAP.com
<mailto:markus.lauff@sap.com?subject=ICWE DI Workshop Submission>  no
later than May 9th, 2005.

Workshop Co-chairs

*	Dr. Markus Lauff
	SAP AG - SAP Research (Markus.Lauff@SAP.com) 
*	Dr. Thomas Ziegert
	SAP AG - SAP Research (Thomas.Ziegert@SAP.com
<mailto:Markus.Lauff@SAP.com> ) 

Program Committee

*	Stephane Boyera (W3C, France, W3C DI WG) 
*	Roland Merrick (IBM UK, Emerging Technology) 
*	Prof. Alexander Schill (University of Dresden, Germany) 
*	Axel Spriestersbach (SAP Research, Germany) 
*	Prof. Jean Vanderdonckt (University catholique de Louvain,

Important Dates

*	Paper submission: 9th May 2005 
*	Notification: 6th June 2005 
*	Camera ready paper submission: 20th June 2005 
*	Workshop: 26th July 2005 


The terms "Access Mechanism" and "Delivery Context" are defined in the
"Glossary of Terms for Device Independence
<http://www.w3.org/TR/di-gloss/> " (W3C Working Draft 18 January 2005)

	Access Mechanism 
	A combination of hardware (including one or more devices
<http://www.w3.org/TR/di-gloss/#def-device>  and network connections)
and software (including one or more user agents
<http://www.w3.org/TR/di-gloss/#def-user-agent> ) that allows a user
<http://www.w3.org/TR/di-gloss/#def-user>  to perceive and interact
<http://www.w3.org/TR/di-gloss/#def-interaction>  with the Web using one
or more modalities <http://www.w3.org/TR/di-gloss/#def-modality> .
(sight, sound, keyboard, voice etc.) 
	Delivery Context 
	A set of attributes that characterizes the capabilities of the
access mechanism <http://www.w3.org/TR/di-gloss/#def-access-mechanism> ,
the preferences of the user <http://www.w3.org/TR/di-gloss/#def-user>
and other aspects of the context into which a web page is to be

More information can be also found on the web pages of the W3C
Interaction Domain "Device Independence" <http://www.w3.org/2001/di/> .
Received on Monday, 25 April 2005 17:22:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:54:24 UTC