title: glTF accessor.max/min validation
body: <p>The KhronosGroup <a href="https://github.com/KhronosGroup/glTF/tree/master/specification/2.0" rel="nofollow noreferrer">glTF 2.0 specification</a> requires that <em>accessor.max</em> and <em>accessor.min</em> bounds be specified for POSITION arrays. However, these values must be expressed as text strings, whereas the the vertex position coordinates are stored as single-precision floats in base64-encoded strings.</p>
  
  <p>The problem I am experiencing is that the online <a href="http://github.khronos.org/glTF-Validator/" rel="nofollow noreferrer">Khronos glTF validator</a> and the Microsoft Visual Code extension (which is presumably a port of the Khronos validator) compares these values to 15 decimal places (i.e., double precision) and reports an error if they do not match exactly. This makes it exceedingly difficult to debug large glTF files, as it results in tens of thousands of errors.</p>
  
  <p>More important, I am wondering whether these errors are important. I could modify my glTF file generator such that the vertex position coordinates can be expressed as text strings without error, but it seems like a ridiculous solution. Am I missing something here?</p>