...
The UIMA project's mission says in part it's related to the "spec" in OASIS which was more a spec about a wire-format (i.e., serialization format) for UIMA, based on XMI (XML Metadata Interchange) standard. XMI has not caught on very well. This topic is to flesh out from a data interchange point of view what the important things are.
Topic is here.
Framework interoperability
...
Some new capabilities may benefit from specifying boundary actions. Some possible actions:
- If a PEAR defines an external resource for use within the pear, it could put the impl classes within the PEAR classpath boundaries. see
Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key UIMA-4499 - If a component defined some customization of JCas for some types, and we implement this via hooks, the hooks could be inserted/withdrawn at the boundaries. This is similar to switching JCas implementations at PEAR boundaries, but applies outside of PEARS and on finer grain size (e.g., just one component).
- A component uses some adapter(s) for type system differences, within the component boundaries
...