• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Presentation of lpOD (ODF automation platform) at FOSDEM 2010
 

Presentation of lpOD (ODF automation platform) at FOSDEM 2010

on

  • 1,142 views

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 ...

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.

Statistics

Views

Total Views
1,142
Views on SlideShare
1,133
Embed Views
9

Actions

Likes
0
Downloads
1
Comments
0

3 Embeds 9

http://www.itaapy.com 7
http://www.slideshare.net 1
http://itws1.demo.itaapy.com 1

Accessibility

Categories

Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Presentation of lpOD (ODF automation platform) at FOSDEM 2010 Presentation of lpOD (ODF automation platform) at FOSDEM 2010 Presentation Transcript

    • LPOD, a library to extend ODF ecosystem Presentation of the project LPOD http://lpod-project.org FOSDEM 2010 Jérôme Dumonteil, Ars Aperta 12:15 – 13:00 5 nov 2009
    • Agenda
      • 1) Presentation of the LPOD project
        • Objectives
        • Members
        • Technical principles
        • Why the LPOD project ?
        • Quick FAQ
      • 2) “show me the code” part
    • LPOD project
      • “Langages et plateformes Open Document” : lpOD
      http://lpod-project.org
    • The LPOD project objectives
        LpOD is an ongoing project developing an OpenDocument library for several languages
        • Python
        • Perl
        • ruby
    • The LPOD project objectives
      • The lpOD project aims both:
        • Providing a common API for those languages for OpenDocument
        • Implementing and validating a high level business intelligence oriented API
        • Technical architecture based on 3 layers :
          • XML, ZIP, VFS abstraction
          • ODF abstraction
          • Business oriented high level API
    • The LPOD project members
      • LpOD is a project supported by
        • french National Research Agency (ANR)
        • Paris area clusters of companies acting in open source and innovation.
      • Strength of the project :
        • a bridge between open source, market ad research needs.
    • The LPOD project members
      • 4 companies :
        • Ars Aperta (ODF expertise and market analysis)
        • Itaapy (Python and architecture expertise)
        • Pierlis (Ruby and smartphones expertise)
        • Talend (Perl and BI expertise)
      • 4 Public research laboratories :
        • Museum of Louvre (massive multimedia datas)
        • ParisTech (Security analysis)
        • Univ. du Littoral (massive research datas)
        • UPMC (accessibility analysis)
    • The LPOD tech principles
      • Fundamentals :
        • Definition of a Free Software API implementing the ISO/IEC 26300 standard.
        • Development and validation of an ODF implementation for higher level use cases.
    • 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
        • Free Software development methods.
    • The LPOD tech principles
      • Strict implementation of the ISO/IEC 26300 standard (and ODF 1.1, 1.2...)
      • Business needs oriented approach and validation for the higher level features
      • Topdown architecture (not based on a low level XML mapping)
      • RESTful architecture and style of development.
      • Why the LPOD project ?
        OpenDocument Format:
        • is the ISO standard for office documents
        • handles both semantics and presentation separately
        • avoids the lock-in of the format by specific tools
      • ODF, as a standard, can manage documents beyond classical office usage .
      • Why the LPOD project ?
        By providing new development tools suitable for BI oriented documents, LPOD wants to extend ODF usage towards :
        • computer generated documents,
        • automated processes,
        • REST web technologies,
        • Thus becoming a common toolbox for BI, data storage for web 2.0, smartphones...
      • Why the LPOD project ?
        • LpOD provides an interoperability platform between OOo world and data mining world based on ODF,
        • 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
    • The LPOD FAQ
      • FAQ
        • Q: Is it open source ?
          • A: Yes.
        • Q: With good license ?
          • A: dual license (user choice)
            • “community oriented” GPL v3
            • “business oriented” Apache v2
    • The LPOD FAQ
      • FAQ
        • Q: Can we see the code ?
          • A: Yes, Code is now fully available (GIT access)
        • Q: Is there any documentation ?
          • A: Yes.
        • Q: Roadmap ? Date of release ?
          • A: release early, release often... monthly releases
            • 0.8,, 0.9 ....
          • A: full perimeter project target is end of 2010.
    • 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...
    • The LPOD FAQ
      • FAQ
        • Q: Code dependencies ?
          • A: as few as possible : low level xml and other common libraries
          • 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
          • A: Level 2 mde to be adapted to specific business needs
          • A: It's free software :-)
    • 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.
          • A: Collaboration started with ODF Tk.
          • A: Sharing a common high level API for other project would be a success for everyone
    • 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)
          • A: LpOD implements a library, not a end user software
          • 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.
    • Unit testing suite
    • “Show me the code”
    • “Show me the code”
      • Demo (v 0.9)