There are a couple of properties of the JointMotion class, namely
which I think ought to have different names. The word "rotation" implies an ACTION, as in "rotate the object from this angle (or maybe whatever is the current angle) to this other angle". But what's actually being specified (or accessed) via these two properties are ANGLES, not rotations. The rotationValue actually sets what ANGLE you want the object to be at, and returns the current angle of it. The rotationLimits specify the RANGE of angles at which the object can be set. It actually says nothing about any kind of visual rotation operation that the script my attempt (as in doing a for-loop that successively increments the angle of the Joint) .
Now, no doubt changing those parameter names would likely break a lot of existing scripts, but at the very least I think that the descriptions of those parameters should be changed to make it clearer that what you're specifying are ANGLES and the range of valid specifiable angles, and it really has nothing to do with the rotation of the joint.
So far I've only worked with Joint control, but this issue of confusing an action with a position may well exist with other kinds of Joints.
