1. Technology Chair Peter Kriens aQute.se

2. Issues No standardized process for chairs to handle publication tasks Waterfall model Publications contain the same information but maintained separately Ad-hoc reuse of material/experience. Inconsistencies Indexes : too few and wrong

3. Publications demonstrations educators panels designfest doctoral educators posters exhibits tutorials workshops speakers operations Advance Program Final Program Palmguide PocketGuide Signage Web site Companion Addendum

4. Goals Minimize the overhead work a chair has to do More features in the publications –Indexes No errors Make changes easy until very late in the process

5. How? Derive all publications from chair maintained files (XML) Daily build for all publications Offer a committee web site

6. Publication Process Demonstrations <> Demonstrations information <> XSLT XSL style sheets Publication Demonstrations information <>

7. Web site Generation of HTML pages Needs close work with Steve Watson Demonstrations <> Demonstrations information <> XSLT XSL style sheets Publication Demonstrations information <> HTML Static HTML and images HTTP

8. PalmGuide/PocketGuide Will be based on HTML Will use Plucker in Palm Demonstrations <> Demonstrations information <> XSLT XSL style sheets Publication Demonstrations information <> HTML Static HTML and images PLUCKER palm

9. Advance + Final Program Need formatting and indexing Choice for Framemaker or XSL:FO Tutorials <> Posters information <> XSLT XSL style sheets MIF file Demonstrations information <> MIF file MIF file Static FM file BOOK file Template file FM Program

10. What is in the XML file Program AuthorEvent LocationAuthorItem Author TitleAbstract TitleAbstract

11. How to maintain the XML We need versioning and document management CVS TortoiseCVS (www.wincvs.org) takes the pain out CVS Checking in data will trigger a build

12. Issues Framemaker or FOP Technical Program: 3 chairs? Or Panels, Technical Program and … Scope? Can we work with CVS?