Can we do that if/when we have a 1.5 spec? It seems like a reasonable solution for now, when there are only two different versions...

That said, brian was mentioning to me that he wishes he could refactor this whole validator to be more object-oriented, in which case I could totally imagine there being separate classes for 0.5 and 1.0 badges (and future ones) that each have their own respective methods. But it seems like the best way to do that is through a big ol' refactor that refactors the whole shebang, rather than just changing `doesRecipientMatch`.