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.
The behavior of the selectFS API changes in this release, in particular with respect to the handling of zero-width annotations (those that have the same start and end position). The behavior has been made to align with the new annotation predicates, the details of which are described in the UIMAv3 User's Guide.
The shifted operation can no longer be used to expand a selection beyond its
selection boundaries. Consider the following example:
t1 = new Token(0,1)
t2 = new Token(2,3)
t3 = new Token(4,5)
t4 = new Token(6,7)
t5 = new Token(8,9)
In previous versions, was also possible to use a negative shift with a bounding operator such as
following, coveredBy, etc. and it would call moveToPrevious
on the internal iterator of the selection operation, causing it to return annotations occurring
before the bounds e.g.:
select().shifted(-1).following(t3) => {t3, t4, t5}
This was found to be inconsistent behavior. The iterator used for the selection (which can also be
obtained by calling fsIterator()) should respect the bounds.
As of this UIMA version, using shifted with a negative argument in conjunction with
a bounding operator will trigger a warning in the logs and return an empty result.
select().shifted(-1).following(t3) => {}
select().following(t3) => {t4, t5}
In previous versions, the using the moveTo operation backwards iterators obtained
through SelectFSs did never ignore type priorities - even though SelectFSs
by default should ignore them.
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