OOoCon Lpod


Published on

LPOD is a odf processing of scripts

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

OOoCon Lpod

  1. 1. LPOD, a library to extend ODF ecosystem Presentation of the project LPOD Jérôme Dumonteil Luis Belmar-Letelier LPOD Founding members 12:15 – 13:00 5 nov 2009
  2. 2. Agenda <ul><li>1) Presentation of the LPOD project </li><ul><li>Objectives
  3. 3. Members
  4. 4. Technical principles
  5. 5. Why the LPOD project ?
  6. 6. Quick FAQ </li></ul><li>2) “show me the code” part </li></ul>
  7. 7. LPOD project <ul><li>“Langages et plateformes Open Document” : lpOD </li></ul>
  8. 8. The LPOD project objectives <ul>LpOD is an ongoing project developing an OpenDocument library for several languages <ul><li>Python
  9. 9. Perl
  10. 10. ruby </li></ul></ul>
  11. 11. The LPOD project objectives <ul><li>The lpOD project aims both: </li><ul><li>Providing a common API for those languages for OpenDocument
  12. 12. Implementing and validating a high level business intelligence oriented API
  13. 13. Technical architecture based on 3 layers : </li><ul><li>XML, ZIP, VFS abstraction
  14. 14. ODF abstraction
  15. 15. Business oriented high level API </li></ul></ul></ul>
  16. 16. The LPOD project members <ul><li>LpOD is a project supported by </li><ul><li>french National Research Agency (ANR)
  17. 17. Paris area clusters of companies acting in open source and innovation. </li></ul><li>Strength of the project : </li><ul><li>a bridge between open source, market ad research needs. </li></ul></ul>
  18. 18. The LPOD project members <ul><li>4 companies : </li><ul><li>Ars Aperta (ODF expertise and market analysis)
  19. 19. Itaapy (Python and architecture expertise)
  20. 20. Pierlis (Ruby and smartphones expertise)
  21. 21. Talend (Perl and BI expertise) </li></ul><li>4 Public research laboratories : </li><ul><li>Museum of Louvre (massive multimedia datas)
  22. 22. ParisTech (Security analysis)
  23. 23. Univ. du Littoral (massive research datas)
  24. 24. UPMC (accessibility analysis) </li></ul></ul>
  25. 25. The LPOD tech principles <ul><li>Fundamentals : </li><ul><li>Definition of a Free Software API implementing the ISO/IEC 26300 standard.
  26. 26. Development and validation of an ODF implementation for higher level use cases. </li></ul></ul>
  27. 27. The LPOD tech principles <ul><li>Plurilinguistic approach: </li><ul><li>Definition of a common feature set before the development starts </li></ul><li>Validation of advanced users' needs: </li><ul><li>scientific laboratories, industrial scale users </li></ul><li>Project management: </li><ul><li>Short iterations, XP-style programming
  28. 28. Free Software development methods. </li></ul></ul>
  29. 29. The LPOD tech principles <ul><li>Strict implementation of the ISO/IEC 26300 standard (and ODF 1.1, 1.2...)
  30. 30. Business needs oriented approach and validation for the higher level features
  31. 31. Topdown architecture (not based on a low level XML mapping)
  32. 32. RESTful architecture and style of development. </li></ul>
  33. 33. <ul>Why the LPOD project ? </ul><ul>OpenDocument Format: <ul><li>is the ISO standard for office documents
  34. 34. handles both semantics and presentation separately
  35. 35. avoids the lock-in of the format by specific tools </li></ul><li>ODF, as a standard, can manage documents beyond classical office usage . </li></ul>
  36. 36. <ul>Why the LPOD project ? </ul><ul>By providing new development tools suitable for BI oriented documents, LPOD wants to extend ODF usage towards : <ul><li>computer generated documents,
  37. 37. automated processes,
  38. 38. REST web technologies,
  39. 39. Thus becoming a common toolbox for BI, data storage for web 2.0, smartphones... </li></ul></ul>
  40. 40. <ul>Why the LPOD project ? </ul><ul><ul><li>LpOD provides an interoperability platform between OOo world and data mining world based on ODF,
  41. 41. LpOD extends ODF ecosystems to new kind of datas and enhances ODF value as a pivot format and as a repository format, </li></ul><li>Thus, as a library, lpOD can extend the ODF community to new users and new usages, enhancing usability value of ODF documents </li></ul>
  42. 42. The LPOD FAQ <ul><li>FAQ </li><ul><li>Q: Is it open source ? </li><ul><li>A: Yes. </li></ul><li>Q: With good license ? </li><ul><li>A: dual license (user choice) </li><ul><li>“community oriented” GPL v3
  43. 43. “business oriented” Apache v2 </li></ul></ul></ul></ul>
  44. 44. The LPOD FAQ <ul><li>FAQ </li><ul><li>Q: Can we see the code ? </li><ul><li>A: Yes, get the released snapshots. </li></ul><li>Q: Is there any documentation ? </li><ul><li>A: Yes. </li></ul><li>Q: Roadmap ? Date of release ? </li><ul><li>A: release early, release often... monthly releases 0.8,0.85, ....
  45. 45. A: full perimeter project target is end of 2010. </li></ul></ul></ul>
  46. 46. The LPOD FAQ <ul><li>FAQ </li><ul><li>Q: Can we contribute to the project ? </li><ul><li>A: Not yet. But comments are welcome. </li></ul><li>Q: JAVA, C++, .Net ? </li><ul><li>A: current contractual roadmap only includes python, perl and Ruby. </li></ul><li>Q: Can you integrate new languages, new needs ? </li><ul><li>A: With relevant founding and reasonable scheduling... </li></ul></ul></ul>
  47. 47. The LPOD FAQ <ul><li>FAQ </li><ul><li>Q: Code dependencies ? </li><ul><li>A: as few as possible : low level xml and other common libraries </li></ul><li>Q: Code customization ? </li><ul><li>A: Level 0 made to be adapted to specific high performance needs
  48. 48. A: Level 2 mde to be adapted to specific business needs
  49. 49. A: It's free software :-) </li></ul></ul></ul>
  50. 50. The LPOD FAQ <ul><li>FAQ </li><ul><li>Q: ODF Toolkit Union ? </li><ul><li>A: Progressive integration of lpOD to ODF Toolkit is planned, to centralize ODF libraries and community management. </li></ul><li>Q: OOo and other implementations interoperability? </li><ul><li>A: Interoperability, both on ODF and API, is strategic for lpOD.
  51. 51. A: Collaboration started with ODF Tk. </li></ul></ul></ul>
  52. 52. The LPOD FAQ <ul><li>FAQ </li><ul><li>Q: differences with other ODF implementations </li><ul><li>A: LpOD is based on a topdown architecture (not based on a low level XML mapping)
  53. 53. A: LpOD implements a library, not a end user software
  54. 54. A: LpOD is not “document” oriented, but “data” oriented. LpOD is not bounded to the desktop paradigm. LpOD provides an abstraction layer for ODF use. </li></ul></ul></ul>
  55. 55. “Show me the code” Code key dates <ul><li>2009-02-10 : launch of the project website
  56. 56. 2009-02-18 : first code commit of lpOD.
  57. 57. 2009-10-30 : </li><ul><li>project started 8,5 months ago
  58. 58. lpOD got 739 commits </li></ul><li>2009-10-30 : lpOD v.0.7 released </li></ul>
  59. 59. Unit testing suite
  60. 60. “Show me the code”
  61. 61. “Show me the code” <ul><li>Demo (v 0.7) </li></ul>