Accessor min+max should have double precision

[microsoft]

Accessor min+max should have double precision

[JeanPhilippeKernel]

Can I take it ? , how I can work on it ?

[donno]

Is this issue valid? For glTF 2.0, based on the following paragraph from the specification it seems it isn't. That is to say, they shouldn't have double precision.

accessor.min and accessor.max properties are arrays that contain per-component minimum and maximum values, respectively. Exporters and loaders must treat these values as having the same data type as accessor's componentType, i.e., use integers (JSON number without fractional part) for integer types and use floating-point decimals for 5126 (FLOAT). - Reference

The implementation note that follows also mentions in JavaScript the recommendation is to round to the nearest 32-bit single precision float.

If accessor.componentType could be a double-precision float then it should be able to have double precision min and max but that isn't allowed.

[bghgary]

I tend to agree. This doesn't seem like something we should support.