User: louis Date: 2007-08-02 17:08:08+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.7&r2=1.8 Delta lines: +26 -8 -------------------- --- odf_camp.html 2007-07-31 22:33:59+0000 1.7 +++ odf_camp.html 2007-08-02 17:08:06+0000 1.8 @@ -88,7 +88,7 @@ </tr> <tr> <td width="11%" class="timebox">10:15-11:00</td> - <td class="keynotebox" colspan="2">Session 1 </td> + <td class="keynotebox" colspan="2">Session 1 : Review of documents </td> </tr> <tr> <td class="breakbox"> </td> @@ -97,36 +97,54 @@ <tr> <td class="timebox">11:15-13:45</td> - <td width="89%" class="sessionbox"><div align="center">Session 2 </div></td> + <td width="89%" class="sessionbox"><div align="center">Session 2 : Review and analysis of documents </div></td> </tr> <tr> <td class="breakbox"> </td> <td class="breakbox" colspan="2">Lunch Break</td></tr> <tr> <td class="timebox">15:00-16:45</td> - <td class="sessionbox"><div align="center">Session 3 </div></td> + <td class="sessionbox"><div align="center">Session 3 : Coding </div></td> </tr> <tr> <td class="breakbox"> </td> <td class="breakbox" colspan="2"><div align="center">Break</div></td> </tr> <tr><td class="timebox">17:00-18:30</td> - <td class="sessionbox"><div align="center">Session 4 </div></td> + <td class="sessionbox"><div align="center">Session 4 : Coding, solutions </div></td> </tr> <tr><td class="timebox">18:40-19:00</td> - <td class="sessionbox"><div align="center">Wrap up</div></td> + <td class="sessionbox"><div align="center">Wrap up and next steps </div></td> </tr> </tbody> </table> <br /> <h3>About this ODF Camp</h3> -<p>The ODF Camp, run in parallel with OOoCon, which is graciously hosting this first camp, is meant to be a focused workshop for ODF and XML developers interested in identifying and when possible resolving differences among key implementations of the ODF. The focus will be on interoperability among the implementations. The <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">OpenDocument format (ODF)</a> is independent of OpenOffice.org and is maintained by <a href="http://www.oasis-open.org/home/index.php">OASIS</a>. OOoCon is hosting this camp, along with the sponsorship of OASIS, and other camps are planned, for instance at the next aKademy, the KDE conference, and at other relevant events. Because this camp is being held in conjunction with OOoCon, all participants must be registered with the Conference. </p> +<p>The ODF Camp, run in parallel with OOoCon, which is graciously hosting this first camp, is meant to be a focused workshop for ODF (OpenDocument Format) and XML developers interested in identifying and when possible resolving differences among key implementations of the ODF. The focus will be on interoperability among the implementations. The <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">OpenDocument format (ODF)</a> is independent of OpenOffice.org and is maintained by <a href="http://www.oasis-open.org/home/index.php">OASIS</a>. OOoCon is hosting this camp, along with the sponsorship of OASIS, and other camps are planned, for instance at the next aKademy, the KDE conference, and at other relevant events. Because this camp is being held in conjunction with OOoCon, all participants must be registered with the Conference. </p> <p>If you wish to participate, please consider that:</p> <ul> <li>this is for ODF developers; and </li> <li>our space is limited.</li> </ul> -<p>To learn more, <a href="mailto:[EMAIL PROTECTED]">send us an email</a>. We have to find the right room and have anticipated about 20-25 people. </p> +<p><strong>All participants (and would-be participants) are strongly encouraged to read the <a href="#details">detailed explanation</a> of the camp below. You will need to do things before the actual camp!</strong></p> +<p>To learn more, <a href="mailto:[EMAIL PROTECTED]">send us an email</a>. We have to find the right room and have anticipated about 25-30 people. </p> +<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. [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>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>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]
