The goal of the Okapi Framework is to allow tools developers and localizers to build new localization processes or enhance existing ones to best meet their needs, while preserving a level of compatibility and interoperability. It also provides them with a way to share (and re-use) components across different solutions. The project uses and promotes open standards, where they exist. For the aspects where open standards are not defined yet, the framework offers its own. The ultimate goal is to adopt the industry standards when they are defined and useable.
Personally, I like Okapi because it uses a common file format, XLIFF, for localization. From my work experience, I often receive materials in different formats from various departments and the result of this caused the Translation Database messy. By using one common format, it makes life easier for the translators, reviewer and linguists, as they only need to learn to handle one type of file and for the engineers to convert the file back to their native formats is just a button click away..
At the point of this post is written, Okapi is still under development, and the support for the XLIFF specification is still quite limited. It only support some tags like