This page describes the WWW8 developer day tracks, along with contact information for the track chairs -- if you have a proposal for a presentation, please send it to the appropriate chair(s).. As time progresses, some of these tracks may disappear, and others emerge -- I must keep the number at 8 or below. To do this, some sessions may only run for half the day, while others may be merged into another session
This session will examine the implementation issues arising from these specifications, as previously high-end features such as antialiasing, true transparency, image filtering and clipping, and color management move into the mainstream and meet standard Web technologies such as XML, XLink, CSS and XSL to produce the high quality hypergraphics of tomorrow's Web.
One part of this track will be run jointly with the Style Sheets and Formatting track, to cover style sheets applied to vector graphics.
One part of this track will be run jointly with the Graphics track, to cover style sheets applied to vector graphics.
Contributors to this session will address these and related questions on the basis of their own development experiences and prospects, with balanced attention to the costs and liabilities of the technologies they employed. The format for presentation is flexible; we can schedule slots as short as ten minutes, and as long as forty-five, if justified.
Presenters need to be prepared to field questions on the WWW8 theme of "accessibility", that is, availability of Web work to "users with physical or other impairments as an important principle of Web development."
The range of topics pertinent to this Forum is wide; other possibilities include:
Scripting might appear on client- or server-side; it might have such different developmental life cycles as are typical with
It might even be useful to talk about projects which reveal limits to scripting's applicability. In all cases, though, it's crucial to make clear how a language technology makes a difference. A bare report that a recent deployment used PHP is not sufficient; interpretation of PHP's role in a successful delivery is likely to make a good talk, though.
What constitutes barrier free access for emerging technologies or evolving standards is not well defined. Although the general principles of barrier free design are well documented, there is no systematic prescriptive process in place for designing accessible leading edge software. By necessity this is a ongoing participatory process.
This day long session will grapple with accessible design of emerging web-based standards and software. Developers are encouraged to present unsolved or partially solved access challenges for input or discussion during the session. Presenters are invited to discuss techniques that result in barrier free web-based products and case studies of successful or unsuccessful development strategies or business practices that are directed at barrier free design.
If you are interested in presenting please submit a proposal for a 30 to 45 minute presentation. Please specify the access challenge, what sector you represent, will you be discussing the process of creating barrier free software or specific techniques and design decisions? Please frame your presentations for developers: talk in specific technical terms not in generalities. A panel of barrier-free design experts will be available to respond to sessions seeking input.
From the hype and press attention one might think that Open Source software will cure cancer and bring world peace. Well, not anytime soon; but not only has the open-source approach to development helped create a rich set of world-class applications for the Web, it has also helped ensure the interoperability of Web software through adherence to common, open protocols. Thus, it's important to consider open-source approaches to software development for any type of Web application. However, the OSS approach is not without its limitations or pitfalls, both for technological and for organizational reasons.
This day-long session will dive into the technical and operational aspects of an Open Source approach to software development for the Web. Project developers will give overviews and details of various projects, both on the Web client and Web server side; as well as discuss strategies for OSS development that have worked, or not worked, for their development teams.
We invite anyone involved to a significant degree in an active open-source project to submit a proposal for a 30-45 minute presentation on the above topics. In your presentation, be clear to show how an OSS approach either helped, or hurt, the goals for the project. We would like a broad set of projects represented, as well as a variety in project models."
The sessions are only as good as the presentations they contain -- and that factor is entirely decided by you! The session chairs will be (and are already are) actively soliciting presenters, but you can, if you wish, contact them yourself if you have something interesting you would like to present. The criteria for presentations are:
If you're interested in presenting, please contact the relevant session chair directly. Their email addresses are provided above.
If you have additional ideas and/or suggestions for W3C, please contact ian.graham@utoronto.ca.