Adam Lally wrote:
Some questions I had on glossary definitions. Currently we have the
following definitions in our glossary:
---------------------
UIMA: UIMA is an acronym that stands for Unstructured Information
Management Architecture; it is a software architecture which
specifies component interfaces, design patterns and development
roles for creating, describing, discovering, composing and deploying
multi-modal analysis capabilities.
UIMA Java Framework:
A Java-based implementation of the UIMA architecture. It provides
a run-time environment in which developers can plug in and run
their UIMA component implementations and with which they can
build and deploy UIM applications.
UIMA Software Development Kit (SDK):
The SDK includes the framework plus additional components such
as tooling and examples. Some of the tooling is Eclipse-based
http://www.eclipse.org/).
I removed "UIMA SDK" from the overview chapters, and replaced it with
Apache UIMA or Apache UIMA Project. I suggest we change this to a glossary
entry for the "Apache UIMA Project" - and include refs to the web site, etc.
-----------------------
Should the definition for UIMA refer to the OASIS TC?
I think it is a good thing to refer to UIMA as undergoing
standardization within
an OASIS TC.
Should the following two terms be renamed to Apache UIMA Java
Framework and Apache UIMA SDK? And should there be a definition for
"Apache UIMA" without the "SDK" part - in which case what is the
difference, Apache UIMA is the project, and the SDK is the artifact we
produce?
Hmmm - not sure what the "following 2 terms" are?
I think that some UIMA terms should start with UIMA so people find them :-).
I would drop the UIMA SDK as a term.
-Marshall
