What is UIMA?
Major Changes in this Release
How to Get Involved
How to Report Issues
List of JIRA Issues Fixed in this Release
Unstructured Information Management applications are software systems that analyze large volumes of unstructured information in order to discover knowledge that is relevant to an end user. UIMA is a framework and SDK for developing such applications. An example UIM application might ingest plain text and identify entities, such as persons, places, organizations; or relations, such as works-for or located-at. UIMA enables such an application to be decomposed into components, for example "language identification" -> "language specific segmentation" -> "sentence boundary detection" -> "entity detection (person/place names etc.)". Each component must implement interfaces defined by the framework and must provide self-describing metadata via XML descriptor files. The framework manages these components and the data flow between them. Components are written in Java or C++; the data that flows between components is designed for efficient mapping between these languages. UIMA additionally provides capabilities to wrap components as network services, and can scale to very large volumes by replicating processing pipelines over a cluster of networked nodes.
Apache UIMA is an Apache-licensed open source implementation of the UIMA specification (that specification is, in turn, being developed concurrently by a technical committee within OASIS, a standards organization). We invite and encourage you to participate in both the implementation and specification efforts.
UIMA is a component framework for analysing unstructured content such as text, audio and video. It comprises an SDK and tooling for composing and running analytic components written in Java and C++, with some support for Perl, Python and TCL.
Version 3.1.0 is a minor update to 3.0.2, mainly bug fixes. The major version was updated because the generated JCas classes now include for FSArrays, the generic type of the component, if known.
When migrating from v2, if non-built-in JCas cover classes are being used, a one-time regeneration or migration step is required for these. Please read the Version 3 users guide located in the docs directory for information on these changes and the migration tool which can aid in migrating existing JCas class definitions.
A very brief summary of version 3 vs version 2:
Please read the Version 3 users guide for more details.
Specific changes in release 3.1.0 versus 3.0.2 include
There is an API compatibility report covering the non-internal APIs; see change report for the list of API changes since version 3.0.2.
Please use the mailing lists ( http://uima.apache.org/mail-lists.html ) for feedback.
The Apache UIMA project really needs and appreciates any contributions, including documentation help, source code and feedback. If you are interested in contributing, please visit http://uima.apache.org/get-involved.html.
The Apache UIMA project uses JIRA for issue tracking. Please report any issues you find at http://issues.apache.org/jira/browse/uima