So you are arguing for being explicit about each of the routes we are creating for this?

So we get rid of any /card paths?  Well, really we don't want any controller based paths, just paths that name a card, and some cards have special handlers for some of the standard RESTful actions.

I'm fine with all that, lets spec it and make it work.