It's isn't unnecessary.
0.0 is the floating point zero and 0 is the integer zero.
<0,0,0,1> uses 20 bytes while <0.0, 0.0, 0.0, 1.0> uses 16.
The definition of ZERO_ROTATION is <0.0, 0.0, 0.0, 1.0>
Before you edit the technical content of a page know what you are talking about.
I know one doesn't NEED to add ".0" after every god damn number to make it work as a rotation! Wasteful ineffeciency... Oh and if you think 0,0,0,1 uses more bytes than 0.0,0.0,0.0,1.0 you're on crack.
Eep, the .0 notation emphasizes the point that the constant is composed of floating point values. In a reference material/documentation such as this, you dont need to make things more efficiant, you need to make them less ambiguous and more understandable.
Christopher is correct. Denoting the components as integers affects the page's accuracy and reduces comprehension. A discussion of floats vs. integers as vector or rotation components is more appropriate for their respective pages, not on that of an arbitrary constant. I notice that both vector and rotation gloss this detail over, and even float is somewhat ambiguous. I suggest starting there.