Guidelines for Presentations

See workshop site

The general idea is to give as much time as possible to useful discussion. The presentations are meant to trigger discussions, as well as to support them with concrete material and to help focus them. Be short, concrete and focused; give illustrations and examples.

The general scenario for a session is to have presentations, each followed by a short questions/answers time, and then a general discussion, where attendees will have the opportunity to discuss questions raised by the presentations and ask questions to all presenters together (see guidance for talk duration per session below).

The title of your session should tell you the focus for each session, to help and thus help you prepare you presentation. Here below are some suggestions for presenters in the different sessions/session types:

Getting acquainted
20 minutes per talk, including short questions. The objective is to have the different involved communities introduced to each other, with their rule usage, history, goals, vocabulary etc, so as to make sure that everybody at the workshop shares a minimum of common background about other communities from the beginning
General Requirements
15 minutes per talk, including short questions. Briefly describe and justify each requirement/family of requirements; illustrate your requirements with examples; focus on requirements for exchanging rules; scope different sets of requirements as precisley as possible (with respect to usage, kind of rules, whatever is relevant)
Standards Work
15 minutes per talk, including short questions. Explain the context briefly; tell us what the standard is about and define its scope; explain the relationship with rule exchange and interopearbility on the Web, and focus on what your standard would require from or contribute to the specification of a rule language for interoperability (if anything); tell us what are your ideas for the ideal language, from your specific point of view
Candidate Technologies
20 minutes per talk, including short questions. Tell us to why the presented technology is a candidate, what requirements it fulfills; give us a feeling for what the technology is, do not go to deep into the technical details/is about; give us a couple concrete examples of what you can do and what you cannot do with the technology; do not bother to compare with other technologies, the discussion will take care of that :-)
Use Cases
15 minutes per talk, including short questions. Explain the case briefly and as concretely as possible; focus on the rules exchange aspects and issues, focusing on the requirements for a language; tell us how you solve the problem currently, and what are your ideas for the ideal language, from your specific point of view

Please send us your slides at least an hour before the start of the session in which you are presenting, so we can have them available on the shared presentation machine. (We prefer people use this machine, to save a little setup time.) Sending them the day before is good, too! If you have networking problems, Said Tabet will have a USB storage device for transferring data. HTML and PDF slides are welcome; Powerpoint slides are acceptable, but they may lose quality in being converted to an open format for the workshop record. Send presentations and questions to

Like the accepted position papers, slides published on the public Web pages of the workshop. Submitting your slides comprises a default recognition of these terms for publication.

Christian de Sainte Maria, with Sandro Hawke
$Id: presentation-guidelines.html,v 1.8 2005/04/22 20:03:24 sandro Exp $