Filters not working intuitively

Maybe it is my misunderstanding, but with this data:

```
{
"a": {
"b": [{
"c": {
"d": {
"e": "foo"
}
},
"something": "bar"
}, {
"c": {
"d": {
"e": "miss"
}
}
}]
}
}
```

With the following query, nothing returns:

`a.b[*].c.d[?e == 'foo']`

But this does work:

`a.b[*].c.d|@[?e == 'foo']`

And in JSON Path (JayWay implementation for example):

`a.b[*].c.d[?(@.e == "foo")]` is the equivalent.

Is this intentional? they seem functionally equivalent but obviously are not. This fails in the playground (JavaScript), but also fails in the Java implementation.

Is this a spec issue? As designed? Common bug in all implementations? Where do we report something like this that seems to be prevalent across all of JMES?

The payload names no files or tests. Reproduce the two queries in the JavaScript playground and Java implementation, then compare their behavior with the cited JayWay JSONPath result; done requires an explicit decision about whether the filter semantics are intentional and how compliance should represent them.

Written by the indexing model from the issue text.