lpOD is a document automation platform : a high level API in different langages, to produce, consume or manipulate ODF documents, be it text, spreadsheets or presentations. This presentation by Jérôme Dumonteil took place at FOSDEM 2010.
- 1. LPOD, a library to extend ODF ecosystem Presentation of the
project LPOD http://lpod-project.org FOSDEM 2010 Jrme Dumonteil,
Ars Aperta 12:15 13:00 5 nov 2009
2. Agenda
- 1) Presentation of the LPOD project
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
- 9. Perl
10. ruby 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 on3
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
- 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
- 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 implementationof the ISO/IEC 26300 standard (and ODF
1.1, 1.2...)
30. Business needs oriented approachand 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.
- 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 documentsbeyond classical office usage .
36.
- 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 commontoolbox for
BI, data storage for web 2.0, smartphones... 40.
-
- LpOD provides an interoperability platform between OOo world
anddata miningworld 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 canextend the ODF communityto new users
and new usages,enhancing usability value of ODF documents 42. The
LPOD FAQ
Q: With good license ?
- A: dual license (user choice)
- community oriented GPL v3
43. business oriented Apache v2 44. The LPOD FAQ
- A: Yes, Code is now fully available (GIT access)
Q: Is there any documentation ?
Q: Roadmap ? Date of release ?
- A: release early, release often... monthly releases
A: full perimeter project target is end of 2010. 45. The LPOD
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...
46. The LPOD FAQ
- A: as few as possible : low level xml and other common
libraries
47. A: well, more dependencies if you use the various testing
utilities provided as examples. 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
- 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. A: Sharing a
common high level API for other project would be a success for
everyone 53. The LPOD FAQ
- Q: differences with other ODF implementations
- A: LpOD is based on a topdownarchitecture (not based on a low
level XML mapping)
54. A: LpOD implements a library, not a end user software 55. 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. 56. Unit testing suite 57. Show me the code 58. Show
me the code
