Problem with "not"-Filter about resource-server

[tkrille]

Here's an example by @sputnik27 that works: https://gist.github.com/fwilhe/5f29604ab7770e824969

The question is now: should we change the behaviour of the eq operator or should we create a new, custom operator called in?

[dacrome]

I like the custom operator in.

[wallner]

can you give an example query for both options, so we are all clear what we are talking about?

[tkrille]

@wallner Something like:

groups eq "Department 1"
groups in "Department 1"

Or what do you mean?

[tkrille]

Ok: groups in "Department 1" reads odd, because of the obvious wrong order of operands. Maybe groups hasItem "Department 1" is more appropriate.

[tkrille]

The opposite would then be:

not (groups hasItem "Department 1")

But this reads kind of odd, too.

[tkrille]

Ok, this has been verified as a bug by the people of SCIM: http://www.ietf.org/mail-archive/web/scim/current/msg02497.html and the answer: http://www.ietf.org/mail-archive/web/scim/current/msg02498.html. This means, that we have to change every implementation of each operator. As we can only solve this issue by adding sub-selects, this could also lead to a slight performance degradation. @sschum @timopick @tpick What do you think?

[dacrome]

Moved to osiam/osiam#61