Like 'HTML5' or 'hacker,' 'REST' is a totally destroyed, meaningless term. I'm attempting to be pragmatic about it. Better to effectively communicate than hold onto intellectual purity.
It's still effective communication, because you know I'm contrasting '/bets/1' with 'index.aspx?action=displayBet&bet_id=1&' (which still could be quite RESTful, actually...), and a form that POSTs to '/bets' vs. a form with method=GET request to 'index.aspx?action=addAnotherBet&=SomeValue=1&something_else=2'. And yes, there's more to it than that, but you get the idea.
Just because it makes puritains die inside doesn't make it wrong.
I'd have thought everyone understands what a clean URL is without bringing across all the extra baggage/meaning of calling it RESTful.
I'm usually discussing this more fully, as in "RESTful API vs. SOAP" or the actual nitty-gritty of POST vs PUT requests and such. "clean" works much better in this context, though, thanks. I'll file that one away...
I'm one of those puritans who cries a bit inside myself.