Lpod

Lpod (also written lpOD) is a project's name acronym for languages & platforms for OpenDocument. The lpOD Project develops a set of multilanguage tools around the OpenDocument Format (ODF) standard.

The project was founded by four French companies and four French public laboratories in 2008. It received funding by the French National Research Agency and was awarded the official label of the Cap Digital competitivity cluster.

Technology

The lpod project aims to develop a library implementing the ODF standard in extenso, that is, in the most complete way possible. On top of this library the project aims to build three high-level APIs, one in Python, another one in Perl and the third one in Ruby. In May 2010, the version 0,9 of the Python API and early versions of the Perl API were available.

Improvements to the ODF specification

Several members of the project are working on improvement proposals for the ODF standard, mostly in two specific areas: security and accessibility.

Potential uses

The three APIs and the ODF library are meant to be used in scientific and industrial contexts. As the library itself departs from the traditional productivity suite software it focuses on large volume data handling, enabling the development of tools for data mining specific to scientific and business intelligence uses. APIs already come with specific tools such as format conversion and styles inspection and manipulation.

Licenses

Software developed by the lpod project is available under two free software licenses, namely the GPL v3 and the Apache v2. Copyright is owned collectively by the four companies.

gollark: This should actually be less disruptive than I thought, I can just isolate the privileged stuff in a separate polychoron process instead of just shutting down all user code.
gollark: What is, the evil exploit someone made?
gollark: It's a very clever exploit - they load some trusted code via PotatOS Privileged Execution™, then send it fake HTTP responses containing code.
gollark: I've probably patched it now (hard to test, because one of my changes broke the exploit code but in a way which could be worked around), but at the cost of causing minor breakage in a mostly unused feature.
gollark: I'm having to reverse-engineer yet ANOTHER heavily obfuscated potatOS sandbox exploit.

References
    This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.