should ac:metadataLanguage camel case match xap:MetadataDate

[GoogleCodeExporter]

It's more traditional to start camel case property names with lower case, but 
there is no choice for xap:MetadataDate since Adobe XAP specified it.
We should follow that for ac:metadataLanguage

Pros: 
1. Easier to remember camel case of xap:MetadataDate if it matches the required 
 metadata language tag. 

Cons: 
1. metadata language tag would be the only ac native term not following 
traditional.  If all of them are changed, there might still be conflicts with 
other terms' camel case. 
2. tags are generally machine generated, so any confusion has to only be 
resolved once.

Original issue reported on code.google.com by morris.bob on 27 Aug 2012 at 8:11

[GoogleCodeExporter]

Case of ac terms should be internally consistent, not depending on the most 
similar other terms

Original comment by g.m.hage...@gmail.com on 10 Oct 2012 at 2:42

[GoogleCodeExporter]

Following consensus and leaving as is.

Original comment by morris.bob on 12 Oct 2012 at 3:19

• Changed state: WontFix

[GoogleCodeExporter]

Original comment by morris.bob on 8 Jun 2013 at 7:31

• Added labels: Milestone-Release1.0