Marshall Schor commented on UIMA-5115:

Doing the implementation based on these "primitives" is good because you only 
do things once, and then have other things combine them. 

I think it can also be useful to help people learn an api - they learn a (few) 
primitives, and then see how they can be combined in a potentially wide variety 
of ways, some of which we support with "convenience methods with positional 

I'm imagining for example, a case where someone wanted the "single" constraint 
applied to a "between" style of boundary specification - something we might not 
have made a convenience method for, because we didn't think it was 
wanted/needed.  Another possibility is adding the capability to iterate 
backwards to any of the wide variety of possibilities. With all the variations 
possible, the convenience methods would only cover a portion... 

> uv3 select() api for iterators and streams over CAS contents
> ------------------------------------------------------------
>                 Key: UIMA-5115
>                 URL: https://issues.apache.org/jira/browse/UIMA-5115
>             Project: UIMA
>          Issue Type: New Feature
>          Components: Core Java Framework
>            Reporter: Marshall Schor
>            Priority: Minor
>             Fix For: 3.0.0SDKexp
> Design and implement a select() API based on uimaFIT's select, integrated 
> well with Java 8 concepts.  Initial discussions in UIMA-1524.  Wiki with 
> diagram: https://cwiki.apache.org/confluence/display/UIMA/UV3+Iterator+support

This message was sent by Atlassian JIRA

Reply via email to