Minimizing column priviliges for a select statement

Question

I want to create a view which selects one column from a table. However, the view select statement will reference two additional columns in its 'where clause'. The view and the table have different owners.

Is it possible to create the view while only granting 'select' on the one 'desired' column and still allow the query to access the other two columns in it's 'where clause' via a lesser privilege. The idea is to prevent those two columns from being viewed by any other statement which simply included them in its column list.

I'm thinking along the lines of granting 'select' on the 'desired' column and 'references' on the two predicate columns. However, I tried that and it didn't work. I'm hoping there might be some way of achieving the same?