You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2015/04/29 12:56:06 UTC

[jira] [Updated] (TINKERPOP3-650) Reconsider has step 'within' and 'inside' terminology

     [ https://issues.apache.org/jira/browse/TINKERPOP3-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette updated TINKERPOP3-650:
----------------------------------------
    Component/s: process

> Reconsider has step 'within' and 'inside' terminology
> -----------------------------------------------------
>
>                 Key: TINKERPOP3-650
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-650
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: process
>            Reporter: Bryn Cooke
>            Priority: Minor
>
> 'within' and 'inside' are confusing. They are practically interchangeable in British English. For instance:
> .has('time', within, [10, 50])
> //The runner had a time within 10 and 50 seconds
> Possibly we could use set theory terminology
> .has('time', intersects, [10, 50])
> //The runners time intersects the bag of [10,50]
> or get rid of the distinction altogether and just have in and not_in
> .has('time', IN, range(10, 50))
> .has('time', NOT_IN, range(10, 50))
> .has('time', IN, [10, 50])
> .has('time', NOT_IN, [10, 50])
> Give it a range and the query behaves as a range. Give it a collection and the query acts accordingly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)