You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by sc...@apache.org on 2017/10/20 20:30:05 UTC
svn commit: r1812788 -
/uima/uv3/uimaj-v3/trunk/uima-docbook-v3-users-guide/src/docbook/uv3.overview.xml
Author: schor
Date: Fri Oct 20 20:30:05 2017
New Revision: 1812788
URL: http://svn.apache.org/viewvc?rev=1812788&view=rev
Log:
no jira clarify typePriority non-use by default in select
Modified:
uima/uv3/uimaj-v3/trunk/uima-docbook-v3-users-guide/src/docbook/uv3.overview.xml
Modified: uima/uv3/uimaj-v3/trunk/uima-docbook-v3-users-guide/src/docbook/uv3.overview.xml
URL: http://svn.apache.org/viewvc/uima/uv3/uimaj-v3/trunk/uima-docbook-v3-users-guide/src/docbook/uv3.overview.xml?rev=1812788&r1=1812787&r2=1812788&view=diff
==============================================================================
--- uima/uv3/uimaj-v3/trunk/uima-docbook-v3-users-guide/src/docbook/uv3.overview.xml (original)
+++ uima/uv3/uimaj-v3/trunk/uima-docbook-v3-users-guide/src/docbook/uv3.overview.xml Fri Oct 20 20:30:05 2017
@@ -151,6 +151,11 @@ under the License.
both forwards and backwards while iterating, moving to specific positions, and doing various kinds
of specialized Annotation selection such as working with Annotations spanned by another annotation.
</para>
+ <para>By default, when sorted iterators are set up by the select framework, they ignore typePriorities;
+ this addresses a need of many use cases, and makes operation when there are many annotations spanning
+ the same begin and end more reliable. Each select can specify to use typePriority as
+ part of the ordering when required.</para>
+
<para>This user's guide has a chapter devoted to this new framework.
</para>
</listitem>