glTF2 'sparse' object has redundancy in its indices object

[ar-visions]

... in gltf file, accessors field:
{
	"componentType":5126,
	"count":6442,
	"sparse":{
		"count":1425,
		"indices":{
			"bufferView":345,
			"componentType":5123 # <---  this, how could an index buffer ever be accessed in stride of another component type?  if its a INT16 for instance, it would always be invalid to access it by INT32 and vice versa
		},
		"values":{
			"bufferView":346
		}
	},
	"type":"VEC3"
},

The inclusion of componentType as well as the bufferView seems redundant, to me. I can't see a valid use-case for this. Is it the fault of Blender to export this? (This is Blender 4.0, which features major changes in its glTF2 export)

To me, it seems you always use the componentType of the bufferView..

[ar-visions]

Oh I didn't notice the binary nature of this bufferView -> buffer now. Closing. The bufferView does not have the componentType specified