Is there a best practice for choosing between "yes/no" vs. "true/false" vs. "1/0" (haha, that last one is undefined)?
Of course, there may be some constraints imposed by external technologies like your database.
I've noticed that in cf tags you will sometimes see thisAttribute = "yes/no" or thisAttribute = "true/false".
Is there a reason why one would be used over the other? I'm not even sure why the choice exists.
It looks like the latest documentation is going with the yes/no approach for tag attributes in general. There are still some consistency problems with some of the functions. For example, xmlNew() uses true/false to indicate case sensitivity, whereas xmlParse() uses yes/no for the same thing.
I think I'm leaning toward the yes/no approach. It's still clear, it's a little shorter, and it seems like it is used most in the cf docs. I'll probably tend to still use the 1/0 approach for anything relating to sql or web services. It just seems to work more reliably that way.