>>In addition,
>>DateFORMAT DDMonthYYYY hh:mm:ss !timezone? (22Jul1996 16:00 MET)
>>is mentioned in
>>http://72.14.203.104/search?q=cache:8OU-KvfbF6oJ:archiv.tu-chemnitz.de/pub/1996/0020/doc.ps+%22ddMonthYYYY%22+protocol&hl=en&gl=us&ct=clnk&cd=1
>
>My framework has a lot of data function for formatting date values based on the client requests so this is why naming them in a proper way it important. There are so many date formats that this is getting extremely confusing after a while.

I agree. And people used to use the protoclols approved for their company. But basically, it all is based on common sense. I would not invent something new for this, but apply something that was already used somewhere.
However the proper name is very important to be recognized in the code. And it would be good to have a name that does not require further explanation, the name that reflect the format as close as possible.