To be more specific, since I wasn't in GP... It's not clear what you should do when for example you want to see if 0.3f is a "multiple of" 0.1f (due to the whole 0.30000000000004 thing)
If the implementation wants to account for some floating point errors I think that's fine too. If they want to codify it though, maybe add an epsilon param so the user can specify how close they want it to be.
Having said that most implementations don't use decimal floating points to represent these.
1 == "1"; // true
1n == "1"; // true
1n == "1n"; // falseWhether your JSON parser will preserve the precision correctly is another story. For JavaScript/ECMAScript, you'll need to use a library.
The point is JSONschema could take a stand and say for example, "this filter will always fail when the operand is not the number representation of an exact integer".