Alexey Knyazev

@bghgary See https://github.com/KhronosGroup/KTX-Specification/issues/18#issuecomment-439462702

> it should be possible to replace this use of `allOf` with a plain `$ref` As the docs say, this behavior was introduced with `draft/2019-09`. Since we already moved to...

For consistence, I think we should upgrade the extension schemas to `draft/2020-12` (#2049) before implementing this new composition convention.

Given how glTF handles existing PNG/JPEG/Basis textures, this extension could only be used with _non-color_ texture slots (e.g. normals or ORM) for the following reason. None of the proposed pixel...

> Is there a reason why you do not think that KHR_texture_basisu can deliver the same result as ASTC? The only reason is that ASTC supports many more configurations and...

+1 on including a picture. > non-uniform texture scaling is not supported by all clients that implement this extension What's the intent of this note? Should all new implementations also...

The current GLB format has several well-known shortcomings and the 4 GiB size limitation is one of them. This will likely be addressed in the future container format revisions, be...

I expect that compression will happen in one pass: 1. use the encoder to produce a compressed mesh with morph targets as generic attributes; 2. write compressed data (excluding morph...

> However, this also means that each geometry is potentially quantized/decoded with a (albeit slightly) different level of precision, which could be a problem for applications like CAD or BIM...

Also this > MUST be initialized with zeros makes sense only for sparse accessors (as they need something to override by definition). In all other cases, it would be better...