User: louis Date: 2007-08-02 17:10:10+0000 Modified: marketing/www/ooocon2007/programme/odf_camp.html
Log: updated the page File Changes: Directory: /marketing/www/ooocon2007/programme/ =============================================== File [changed]: odf_camp.html Url: http://marketing.openoffice.org/source/browse/marketing/www/ooocon2007/programme/odf_camp.html?r1=1.8&r2=1.9 Delta lines: +4 -4 ------------------- --- odf_camp.html 2007-08-02 17:08:06+0000 1.8 +++ odf_camp.html 2007-08-02 17:10:08+0000 1.9 @@ -139,11 +139,11 @@ <p>Depending on the complexity of the document and the time allowed, we will send out a few documents, each highlighting a different issue. We would provide annotation explicating some likely overlooked points the vendors should attend to.</p> <p><strong>A week</strong> before the camp, vendors would send in their ODF files for further redistribution to the others. [Suggestions on the technology to be used?] All vendors will therefore have the time prior to the camp to review the differences in ODF implementation among the various vendors. The camp itself will then focus on identifying, in detail, the problems and, if possible, resolving them.</p> <p>Below is the schedule of the day. Prior to the actual camp we will send out PDF files</p> -<p>* Keynote: Stating the problem of interoperability for users [I have it now at 45 minutes but given the nature of this event, shortening it to 30 plus qs. seems reasonable.]</p> -<p>Morning sessions: 10:15 - 13:45 </p> +<p><strong>Keynote</strong>: Stating the problem of interoperability for users</p> +<p><strong>Morning sessions: 10:15 - 13:45 </strong></p> <p>We have set aside two morning and two afternoon sessions, but we want the structure to be fluid and accommodating to the needs at hand. Nevertheless, the morning sessions will focus on demonstrating and identifying implementation differences. We envision that vendors would demonstrate the idiosyncrasies of their implementation, explaining the issues encountered in the files creation. In this manner we could work through the array of files, noting new problems in detail per implementation. As needed, there will be session leaders.</p> -<p>Lunch</p> -<p>Afternoon sessions: 15:00 - 18:30 </p> +<p><strong>Lunch</strong></p> +<p><strong>Afternoon sessions: 15:00 - 18:30 </strong></p> <p>These sessions are meant for coding fixes, if possible, and for demonstrating solutions. The wrap-up session at the end will give us the occasion to discuss our next steps, as well as the feasibility of establishing guidelines for future implementation interoperability.</p> <p> </p> <h3>Disclaimer</h3> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
