Add information to the files explaining how the URI string was created.

[sambaPython24]

Hello,

It is almost impossible to understand this tutorial without an explanation of how the core of all the example files—the uri string—was created.

The explanations about accessors and buffer views do not make sense if it is not clear which part of the data they are actually referencing.

Please add a script or description showing how the data string was created for each example.

[javagl]

How the data was converted from its binary form into a base64 string does not matter. The important point is that this base64 string in the data URI is just some representation of raw, binary data.

In Python, raw data can be encoded into such a string with https://docs.python.org/3/library/base64.html#base64.b64encode
In Java, it can be done with https://docs.oracle.com/javase/8/docs/api/java/util/Base64.Encoder.html#encodeToString-byte:A-
It should be a functionality that is available in basically all libraries.

However, maybe some of the "data layout" images can be helpful: For some of the examples that are part of the tutorial, I added images in the README of the corresponding glTF-Sample-Assets models - for example, for the AnimatedTriangle: https://github.com/KhronosGroup/glTF-Sample-Models/tree/main/2.0/AnimatedTriangle#data-layout

So that obscure data URI in the embedded version of this asset represents the data that is labelled as the "geometryBuffer" in that image.