organizing committee for the
International World Wide
Web Conference invites proposals for participation
Day. Friday, April 11, 1997, will be a day of activities
relevance to developers. And we are encouraging you to propose
which you would like to participate creating the activities of this
objective of the conference is to foster development of the World
Web by providing a forum for the exchange of ideas about the underlying
technology. The conference is intended for those exploring the leading
of this technology, including researchers, developers, content
and users. The conference will focus on substantial
contributions in the
form of original research results and ideas,
striking new software, innovative
applications, and scholarly critique
Visit the other areas of this site to learn more
about the overall conference.
- Call for
Participation: December 20, 1996
- Developer's Day
participation submission deadline: February
(extended from earlier deadline of 2/3/97)
- Notification of acceptance: March 5, 1997
- Final Version Due: March 21, 1997
Do you have something of interest to developers? Are you
interested in hearing from developers?
We tailor the
activities of Developer's Day to appeal primarily to the
organizations who make the technology and tools that make it
ultimately, for content developers and end-users to use and experience
the World-Wide Web.
Whether protocol designer or browser
implementer; developer of tools
for other developers, or of special
end-user effects plug-ins these people
and their organizations are the
makers of the technology and tools.
And in this day they seek to get
and give information that will help them
achieve their objectives.
But this is no small audience or simply a Super BOF! Attendence at
Day in the last two conferences is reported at 60% of the
And expectations are high for great content.
We encourage you
to propose any activity you feel may be of special interest
The Technical Program (Tuesday through Thursday) is a
for presenting complete, novel, new and previously
un-published work. Developer's
Day, however, strives to provide, for
- Detailed information about new developments --
elaborations of Technical
Program content beyond what was appropriate
in those sessions
- Updates on past developments, presentations,
including those presented
at other recent conferences
histories and discussions regarding WWW standards existing or
- Case histories, especially demonstrating and comparing alternative
implementations of technologies or tools
- Information about research
and developments in methodologies parallel
to, extending, optimizing,
or in competition with, the WWW
- Inter-disciplinary research and
developments - in, for example, HCI,
advice and information about the challenges and methods of development
- Advance information about pending or new technologies
and experiences in funding, mergers, and acquitisitions; evaluations
about market and industry structures
- Facts about industry programs
Visit the Call for
and Posters page to see specific suggestions regarding
Here are some suggestions for the type of activities you
further note about Developer's Day. These folks are the experts and
expect top notch content and sessions. To help assure this, the
Committee and the Developer's Day team will provide tools for
of audience interactions, for recording (on computer) the
the session, and for the publishing of that content.
- Technical Paper
discussed above, unlike papers submitted to the Technical
papers that have previously been published and papers that are
currently being considered for publication by another journal or
are eligible (as far as your other commitments
allow!) in the
Developer's Day program. let us know what's been
happening since the earlier
publication, give us the additional
Is there a pressing or
contentious issue which you and a few partners feel
Want to guess the future? Think you have a map on how
help content providers and end users? This isn't a time
though-- you've got an interested and intelligent audience,
how can you
advance this issue?
- Design Briefing
Review a design in detail. Compare two or more designs. Do this at the
code levels, package levels, interface levels. Compare class libraries,
threading technologies, development tools. Let your colleagues know
challenges you faced, the decisions you took (right or wrong!), the
impact on your audience and customers and the your conclusions. Consider
including important team members, vendors, and customers. Show it all.
A dry paper
presentation may not be the right way to report on your work.
what how other developers may benefit from, or how you and others
you may benefit from other developer's learning about, your work.
you're an exhibitor at the WWW6 conference, consider how a detailed,
technical demonstration to senior industry-leading developers may assist
them, or you.
- Workshop or Symposium
you've been working with a group of developers on a particular subject
or technology a Developer's Day session may be an excellent place to draw
others in or to present the an update of the work to the developer
Proposals for non-technical workshops (on, for example,
issues) are welcome too. In your proposal be
sure to identify the primary
group who's been active on the subject and
the prior meetings and activities.
A forum might be a good place to begin a discussion on a subject. Not
well enough to be a panel, with no group involved in
a forum might be the format to explore what is
important about the subject.
In your submission tell us how you intend
to recruit interested developers
to consider the question and prepare
for the discussion in advance of the
- Extended Tutorial
Perhaps your idea for a
tutorial is too advanced for Tutorial Day (Monday),
or is specifically
addressed to developers. This is the place to suggest
a tutorial by
experts in a field to experts in the field.
If you are conducting a WWW6 Workshop or a
Tutorial, or are associated
with an exhibitor which will have
exhibition activities specifically addressed
to developers, this is the
place to make a report. Tell us what happened.
Include pictures, sound,
action! But definitely give a condensed and pointed
presentation of the
achievements, conclusions, and your evaluation of the
future of the topic.
- Contests and Awards
We would like, during the week, to have several contests
developers. Developers developing. Propose a contest, tell us
might be managed, reviewed and judged (in the full light of other
developers - on the web and in sessions), and how the results would be
presented on Friday, Developer's Day. This is a great opportunity to
the Accessibility theme of the conference. The contest
results would be published with the other Developer's
Day conference materials.
- Industry or Vendor
We welcome specific and detailed presentations from
new and established
vendors and industry representatives. Tell
developers where you are heading,
what progress you've made recently,
what you think will be happening. Teams
are especially desired. Ask
developers for guidance and direction; get
them involved. Of special
interest are developer support programs, tools,
international activities. In you proposal identify
the people who would
be speaking and be clear about the significance of
their involvement in
the organization or industry. Include a biography
of each person.
In addition to the main participants, two sorts of people will be
to the success of your session.
This is a person or persons who will
be using the tools we provide to record
the content of the session. If
desired this content would be projected
during the session. Ideally
this person would be familiar with your content.
Less like the idea of a defendant
in a legal proceeding, and not quite
a narrator, this person's job is
to help you involve and engage the audience,
to ask the pointed
question (of the audience and of the speakers/presenters).
you to identify and nominate someone. Give them questions to
out to them the issues you want to press. Ideally for these types
sessions this person would be capable of acting independent of your
point-of-view. Contact a customer, another developer, an independent
another paper presenter, a standards organization member.
We encourage you to nominate these people in your proposal. If you
it the Developer's Day team will assure these roles are filled
for your session.
In either case, these people will participate in
pre-session briefings with you
and the conference staff. Let us know if
you will want to work with them in
advance of the conference.
To submit a
Developer's Day paper or proposal, please see the
www6conf.slac.stanford.edu/devday/submit.html. If you have questions,
send email to
the Developer's Day chair at
As with the Technical Program
content, eventually you will be required to
submit a copyright form that
you must sign and mail back to the Developer's
In your proposal, clearly state the category or type of session which
you are proposing. Include a summary description of the topic and
for the session and a summary biography of each proposed
material should be complete enough to serve as the
basis of our consideration,
and suitable (after an editorial exchange,
perhaps) for publication in the
schedule and proceedings. All submitted
papers will be reviewed for correctness
to the conference, and for quality of presentation.
Developer's Day submissions must be in English. Maximum length (excluding
references) is 10 pages single-spaced. All submissions must use
correct HTML 3.2 (no frames please). To make the
Proceedings more attractive,
it is important that submitted papers follow
the guidelines as closely as
possible. The Editors cannot reformat
contributions for publication.
Your submission should detail any
special technology (hardware, software,
network) or in-room arrangements
All submissions must clearly and specifically
identify a contact for
coordination. Please provide telephone, facsimile,
and email addresses.
In addition to being published in the
Developer's Day Proceedings, these
materials will be made available over
the World-Wide Web prior to the conference.
The success of your proposal,
and of your eventual session, will be enhanced
if you tell us how you
intend to collect pre-conference questions from registered
Day attendees and incorporate them in your session.
Embargoed Materials: Clearly identify any
that must be embargoed. We also suggest you contact the
administrator prior to submitting any such material.
The activities of
Developer's Day will be included in a collected proceedings.
like to include as much of the actual material used in the sessions.
includes any example code, screen shots, snippets, documentation. It
includes animated content and cold-linked sites. Tell us if these kinds
of results are a possibility for your session.
General questions about proposals
for participation in Developer's Day program may be
addressed to email@example.com.
If you would like to attend Developer's Day
activities and participate in the on-line
then visit the WWW6 Conference registration site at: