True. Trouble is, a `false` value is not enough to indicate why validation has failed. We'd want to know the context of the failure, so that we can pass that down to the error view. Specifically, the authentication method that is bound to the spec validation object. 

I certainly could change the API to return more than just a boolean. This seemed simpler. Would rather not change method signatures as much as possible. Made sense at the time that perhaps validation failure may might better be indicated in the context of an exception, rather than just a DTO. But, we can certainly rethink this approach.