User: louis Date: 2007-09-10 13:53:30+0000 Modified: marketing/www/ooocon2007/programme/odf_camp.html
Log: updated with keynote info 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.13&r2=1.14 Delta lines: +4 -8 ------------------- --- odf_camp.html 2007-09-10 11:01:13+0000 1.13 +++ odf_camp.html 2007-09-10 13:53:28+0000 1.14 @@ -141,16 +141,12 @@ <p> </p> <h3>Proposed Schedule--Details<a name="details"></a></h3> <p>This inaugural ODF Camp will focus on interoperability among ODF implementations, in particular regarding text documents. The "ODF" refers of course to the OpenDocument Format, and the matters at hand, resolving differences among implementations and establishing guidelines for future interoperability, is vital to the format's continuing success. Accessibility issues, as they pertain to interoperability, will also be attended to. We anticipate that this camp will be but the first in a series. There will also not be nearly enough time to do what we would want, and so we will start before the actual camp commences.</p> -<p><strong>Three weeks</strong> prior to the camp we will send out (or otherwise make available for downloading) a few PDF files illustrating sample documents. Upon receipt, each participant would attempt to replicate that document to the best of their application's abilities. They would then save the document in ODF format. They would have two weeks in which to do this.</p> -<p>An example document might be to replicate the first page of this PDF:</p> -<ul> - <li><a href="https://www.socialsecurity.be/foreign/en/employer_limosa/infos/documents/pdf/act_mb_28122006.pdf";> https://www.socialsecurity.be/foreign/en/employer_limosa/infos/documents/pdf/act_mb_28122006.pdf</a>.</li> -</ul> -<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. Because of the limitations of time and because we want to have some satisfactory accomplishments, we are limiting the documents to examine to those created by ODF implementations. 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><strong>We have made available for download </strong> a few PDF files illustrating sample documents, each highlighting a different issue. Upon receipt, each participant should try to replicate that document to the best of their application's abilities. They should then save the document in ODF format. </p> +<p>* <a href="InteropCamp.zip">sample documents</a> </p> +<p> Because of the limitations of time and because we want to have some satisfactory accomplishments, we are limiting the documents to examine to those created by ODF implementations. 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><strong>Keynote</strong>: Stating the problem of interoperability for users</p> -<p><strong>Morning sessions: 10:15 - 13:45 </strong></p> +<p><strong>Morning sessions: 10:00 - 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><strong>Lunch</strong></p> <p><strong>Afternoon sessions: 15:00 - 18:30 </strong></p> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
