Jose Fandos of Andekan posted again in his continuing theme of content related posts. He suggests that worrying about a family naming standard, an all-encompassing one at least, isn't our biggest priority. I agree, I've always preached consistency instead of specifics. Every firm I've met over the years has their own position about file and folder naming for every kind of software they use.
He (Jose) predicts that how we find content in and out of Revit will only get better as we move forward so the actual name of a Revit family may become less important as a means to find one. For example, the add-in Family Browser allows us to organize content logically and the name isn't really the focus (while it, a standard, does help organize the folder the content is in perhaps).
If by some chance everybody could agree on a standard strategy it wouldn't hurt us. I don't think it is a fundamental or major priority over actually having content created. If it gets made with a "bad" name, I can always rename it when it hits "my" library anyway. ;)