[x3d-public] Apologies for multiple messages

[John Carlson]

I got concerned that X3DUOM would be standardized in the XML encoding
without a working x3d.py build process.  It does work on the surface, but
fouls up around classes related to X3DVertexAttributeNode and concrete
subclasses/subnodes.

x3d.py 4.0.64.4 is okay.  Building x3d.py does not work.  If someone
remains interested, I can post details, assuming nothing has changed.

I believe this change was made to support better validation in browsers.

I’m pretty sure both Andreas and I reported this when X3DUOM changed per
Holger.

The Blender exporter will proceed with an altered x3d.py.  We will attempt
to modify the name in the Blender exporter.  That is a good suggestion, Don.

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20240225/80c22d17/attachment.html>