Your SlideShare is downloading. ×
OOoCon Lpod
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

OOoCon Lpod

1,809

Published on

LPOD is a odf processing of scripts

LPOD is a odf processing of scripts

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,809
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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

×