[x3d-public] X3D Standards Working Group list of standards under revision

[Michalis Kamburelis]

John, as for the endianess, good point.

Of course, endianess for binary data has to be spelled out in the
specification so that all models are compatible. Just like glTF spec does :

"""
All buffer data defined in this specification (i.e., geometry attributes,
geometry indices, sparse accessor data, animation inputs and outputs,
inverse bind matrices) MUST use little endian byte order
"""

(From https://registry.khronos.org/glTF/specs/2.0/glTF-2.0.html )

Regards,
Michalis

pt., 10 sty 2025, 18:03 użytkownik John Carlson <yottzumm at gmail.com>
napisał:

>
>
> On Fri, Jan 10, 2025 at 6:13 AM Michalis Kamburelis via x3d-public <
> x3d-public at web3d.org> wrote:
>
>>
>> - An (optional of course) way to specify mesh data as binary blobs, in
>> a way compatible with glTF:
>> https://github.com/michaliskambi/x3d-tests/wiki/Binary-meshes
>
>
> While I appreciate performance and size improvements, I come from an era
> of big-endian, little-endian issues:
>
> https://en.m.wikipedia.org/wiki/Endianness
>
> The suggestion is to use “network order” as defined in Internet standards.
>
> AFAIK, HTML was never designed for 2D images that were actual numbers, so
> no surprise that meshes should be binary as well.   UTF-8 should also
> remain a supported option though.
>
> John
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20250111/7af6f040/attachment.html>