Our rules say that acronyms and abbreviations should not be used unless they are part of the commonly understood business language.  When they are used, they are all upper case.  Our bible also says, element names are UpperCamelCase, while attributes are lowerCamelCase, referring to the initial letter.  Really, no matter which convention you follow, you just need to document the rules and ask everyone to follow them. 

There are bound to be cases where someone forgets or deliberately steps outside the rules, so remember: this is not the most important part of what you’re doing.

My main beef w/camel case is what to do w/abbreviations (like LOL).  Should it be CamelCaseLol; not really - oughta be CamelCaseLOL I think.  You see this often with XML, which often gets rendered as Xml.  But if you try to make it look "right" to a human eye, by upper-casing, then software (like wikis) that interpret camel case tend to get it wrong.

Also, for programmer ease, it is sometimes good to have your software recognize the boundary within the symbol.  I find I often want to Alt-F to skip to the middle of the symbol, rather than right over it.

On 2/4/2012 3:31 PM, Alex Muir wrote:

LOL okay maybe it is

--

Some fantastic African/Canadian Fusion  http://bafila.bandcamp.com/