Marshall Schor commented on UIMA-5115:

 I think I may have caused this confusion by leaving off the spec of how the 
boundary constraint is used.  It should have read, for example, 
  at(location).sameBeginAndEnd().single() or
  at(location).coveredBy().singleOrNull(), etc.

And as before, for ease of reading, it's perfectly OK to combine the 
at(spec).coveredBy() into coveredBy(at-spec).

I just break them apart for clarity in examining all the variants...

I have imagined a slightly more augmented abstraction. (Again, for convenient 
API use, some of these ought to be combined...)

  BOUNDARY-CONSTRAINT.          at(fs), at(begin, end) between(fs1, fs2)
  USE-OF-BOUNDARY-CONSTRAINT.  boundedBy, bounding, sameBeginAndEnd
  CARDINALITY-CONSTRAINT + Getter, or TERMINAL      single, singleOrNull, or 
iterator, etc.

> 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