separate token for the view

use a token with correct type for the fall-back case of using a candidate view as an input.

@Dr15Jones 
Chris, if I say "consumes" or "mayConsume" for a product that doesn't exist (that's the case for my mayConsume here), what are the implications on the framework side?
In the current default 72X setup the code runs ok, or if there is a miss it fails on the event itself (not before event processing starts).