Added version
Added data + type
Bounds checking could have been broken in some cases (models having
negative upper-bounds), apparently Float.MIN_VALUE is almost 0 instead
of -Float.MAX_VALUE

Conflicts:
	BimServer/src/org/bimserver/ClashDetector.java
	BimServer/src/org/bimserver/servlets/Bounds.java