Why:
Exactly for the first argument you brought. Also because "CommonDataValues" sounds even more like it only contains DataValue implementations in my ears, while there is other stuff inside (parsers, etc.). It also just came to me that "common" might be quite meaningless, what does it refer to, what do these implementations have in common, or why do they come in common? The answer is, they are complex. So "ComplexDataValues" could also be a possibility if you don't like "DataValueImplementations".
Your argument against "DataValueImplementations" is no good for me, the name does not really imply that it could be the only component with implementations.
2013/9/7 Jeroen De Dauw jeroendedauw@gmail.com:
Hey,
I would prefer "DataValueImplementations" over "CommonDataValues".
Why?
One argument for this is that it will be more consistent with the Composer package name, which will be in the form of data-values/something.
An argument against is that CommonDataValues better describes the package (it does not contain all implementations, just the "common" ones), and is probably easier to understand when you've not come across it before.
Cheers
-- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 --
Wikidata-tech mailing list Wikidata-tech@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-tech