<div style="font-size:inherit"><p style="font-size:inherit;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:18px;margin-top:0px;font-style:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(43,45,49)" dir="auto">On a whim, I had AI review X3D 4.1 CD.  Most of these we already know!  Some problems are evident due to retained strike-thru text retained for tracking, which could be used in future prompts.   I would just skip section 1, 2 and 4 below.  Section 3 appears to be where focus should rest,    Good luck!</p><p style="font-size:inherit;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:18px;margin-top:0px;font-style:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(43,45,49)" dir="auto"><br></p><p style="font-size:inherit;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:18px;margin-top:0px;font-style:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(43,45,49)" dir="auto">Based on a technical review of the current <strong style="font-family:inter,sans-serif">X3D Architecture v4.1 Committee Draft (ISO/IEC 19775-1:202x)</strong> and cross-referencing it with recent Web3D Consortium issue trackers, mailing lists, and schema changelogs up to early 2026[<a href="https://www.google.com/url?sa=E&q=https%3A%2F%2Fvertexaisearch.cloud.google.com%2Fgrounding-api-redirect%2FAUZIYQG3e7urPGBVEHmkvJ2YamxfB0kGnAOFRXBxMISidWWUurL5XyI7E-8Pw56fz9-SgeYMR8VldVL1JH_-KU59N9HIE23Fkq7MwoZbe0K1XMbE938jbU3Ggp0kzWiALpzxdehbTGHPq9yuDmP-Z2YXhS5I7LQzZ2uTgThY6xRrWbTKt4c%3D" style="font-weight:500;text-decoration:none;font-family:inter,sans-serif">1</a>][<a href="https://www.google.com/url?sa=E&q=https%3A%2F%2Fvertexaisearch.cloud.google.com%2Fgrounding-api-redirect%2FAUZIYQFBblIKFKWTIPSeDEBazJ130zJ1cQi4q2u8uwKyDYfnsxCbZVoJHbcg021O78D5SIs5Uq3suzMr-2TxHxzszN9BDhxjAH4IRIrbQI4GCSCQfTMXnRxyJLPqjSnHNg%3D%3D" style="font-weight:500;text-decoration:none;font-family:inter,sans-serif">2</a>], several actual problems, inconsistencies, and errors exist within the specification.</p><p style="font-size:inherit;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:18px;font-style:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(43,45,49)"><span style="font-style:italic;font-family:inter,sans-serif">(Note: While I cannot natively crawl and test every single hyperlink on the live site simultaneously, I have analyzed the specification's structure, known errata, and HTML generation artifacts to identify both broken links and actual textual/technical issues).</span></p><p style="font-size:inherit;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:18px;font-style:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(43,45,49)">Here are the specific problems identified in the v4.1 CD Draft:</p><h3 style="margin:0px;font-family:inter,sans-serif;font-style:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:inherit;color:rgb(43,45,49)">1. Editorial and HTML Generation Errors</h3><p style="font-size:inherit;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:18px;font-style:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(43,45,49)">The specification text contains several typographical errors and HTML generation artifacts resulting from the document pipeline:</p><ul style="padding-left:24px;font-family:inter,sans-serif;font-size:inherit;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(43,45,49)"><li style="font-family:inter,sans-serif;font-size:14px;font-weight:400;line-height:21px"><p style="font-size:14px;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:7px;margin-top:0px"><strong style="font-family:inter,sans-serif">Artifacts in the Text:</strong> Throughout the introduction, the word <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">"cube"</span> inexplicably appears where list items, icons, or headers should be (e.g., <span style="font-style:italic;font-family:inter,sans-serif">"overview of the features of X3D. cube Design objectives."</span>and <span style="font-style:italic;font-family:inter,sans-serif">"cube X3D features"</span>)[<a href="https://www.google.com/url?sa=E&q=https%3A%2F%2Fvertexaisearch.cloud.google.com%2Fgrounding-api-redirect%2FAUZIYQHBNI2CNDQtVsU-KGxzmGmhdBS1PMRnT2DxVqEUyuhCYZBc4fNeroNJicvM0t6k8A3AsI3S-bOUzBkamJPaVJZjfY_Fwl0Cl5gcJ0zTR6XMzIukn_0R5ha6SUM5MK0xE1Lr6IfxzxGMFl-iR8-61UnhuZUjAdD3ep7RB2UgoD_DnOQEfelJlnk3ZAXjVSNveh6tK1mBX3TNXg%3D%3D" style="font-weight:500;text-decoration:none;font-family:inter,sans-serif">3</a>]. This is a broken image alt-text or CSS artifact.</p></li><li style="font-family:inter,sans-serif;font-size:14px;font-weight:400;line-height:21px"><p style="font-size:14px;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:7px;margin-top:0px"><strong style="font-family:inter,sans-serif">Duplicated Phrasing:</strong> In the scope description, there is a prominent copy-paste typo: <span style="font-style:italic;font-family:inter,sans-serif">"Terms, definitions, acronyms, and abbreviated terms Definitions, acronyms, and abbreviated terms contains the glossary..."</span>[<a href="https://www.google.com/url?sa=E&q=https%3A%2F%2Fvertexaisearch.cloud.google.com%2Fgrounding-api-redirect%2FAUZIYQG6tiCqOsSahCsac7bgqPNquqfJRu5b3tUnaUElz8WC72mqAkRolEaEOeDn-3Anyx_f54gpmut0M1DZfkwZvOdQDmndhv0GYg2d2h97s6TGiT6JKw0oWEv6r299lo24NRZ0thIYK6GQe1N6ZWnKX1LzZG4AEBh3yWs3c4NYUcIg0FfY8phIuTmXxYdKQj_cu4Zxdb60DK7LJg%3D%3D" style="font-weight:500;text-decoration:none;font-family:inter,sans-serif">4</a>]</p></li><li style="font-family:inter,sans-serif;font-size:14px;font-weight:400;line-height:21px"><p style="font-size:14px;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:7px;margin-top:0px"><strong style="font-family:inter,sans-serif">Version Numbering Typo:</strong> Section 1 (Scope) explicitly states: <span style="font-style:italic;font-family:inter,sans-serif">"This document is Edition 4.1 4 of ISO/IEC 19775-1"</span> which is a residual markup typo leaving the old "4" next to the new "4.1"[<a href="https://www.google.com/url?sa=E&q=https%3A%2F%2Fvertexaisearch.cloud.google.com%2Fgrounding-api-redirect%2FAUZIYQG6tiCqOsSahCsac7bgqPNquqfJRu5b3tUnaUElz8WC72mqAkRolEaEOeDn-3Anyx_f54gpmut0M1DZfkwZvOdQDmndhv0GYg2d2h97s6TGiT6JKw0oWEv6r299lo24NRZ0thIYK6GQe1N6ZWnKX1LzZG4AEBh3yWs3c4NYUcIg0FfY8phIuTmXxYdKQj_cu4Zxdb60DK7LJg%3D%3D" style="font-weight:500;text-decoration:none;font-family:inter,sans-serif">4</a>].</p></li></ul><h3 style="margin:0px;font-family:inter,sans-serif;font-style:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:inherit;color:rgb(43,45,49)">2. Node, Field, and Schema Discrepancies</h3><p style="font-size:inherit;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:18px;font-style:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(43,45,49)">There are several active technical mismatches between the text of the v4.1 Draft, the X3D Unified Object Model (X3DUOM), and actual implementation behavior:</p><ul style="padding-left:24px;font-family:inter,sans-serif;font-size:inherit;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(43,45,49)"><li style="font-family:inter,sans-serif;font-size:14px;font-weight:400;line-height:21px"><p style="font-size:14px;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:7px;margin-top:0px"><strong style="font-family:inter,sans-serif"><span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">Tangent</span> Node Backward Compatibility:</strong> The specification originally drafted the <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">Tangent</span> node (for glTF bump mapping alignment) using an <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">MFVec3f</span> field. It was recently updated to <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">MFVec4f</span> to include a 4th component indicating the handedness of the tangent basis (-1 or +1). Parts of the documentation and older 4.1 draft models fail validation due to this breaking change[<a href="https://www.google.com/url?sa=E&q=https%3A%2F%2Fvertexaisearch.cloud.google.com%2Fgrounding-api-redirect%2FAUZIYQFc5vL-tLbmPRyO7Z3svCoHAnn8NU0kV6zp4_TC9t0x4y_iYBlw3QW2-Q-MewL0P-9Bv-OjCJvce5tbEzZztEJfPWoEDfABA1DLc5bPN3DpC7s3InDU1-o5LseDMnB2PcC65Zc1RjIn-1KK_4Uw98uEUnXP7O7LwjKwz5W9jXk%3D" style="font-weight:500;text-decoration:none;font-family:inter,sans-serif">5</a>].</p></li><li style="font-family:inter,sans-serif;font-size:14px;font-weight:400;line-height:21px"><p style="font-size:14px;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:7px;margin-top:0px"><strong style="font-family:inter,sans-serif"><span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">EnvironmentLight</span> Inconsistencies:</strong> The ongoing glTF alignment has caused churn in this node. The draft has had discrepancies regarding the presence of the <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">diffuse</span> field (which is being removed) versus the <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">origin</span> field (which was added). Furthermore, the default for <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">global</span> is expected to be <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">true</span>, but schema validators and text have occasionally mismatched[<a href="https://www.google.com/url?sa=E&q=https%3A%2F%2Fvertexaisearch.cloud.google.com%2Fgrounding-api-redirect%2FAUZIYQFBblIKFKWTIPSeDEBazJ130zJ1cQi4q2u8uwKyDYfnsxCbZVoJHbcg021O78D5SIs5Uq3suzMr-2TxHxzszN9BDhxjAH4IRIrbQI4GCSCQfTMXnRxyJLPqjSnHNg%3D%3D" style="font-weight:500;text-decoration:none;font-family:inter,sans-serif">2</a>][<a href="https://www.google.com/url?sa=E&q=https%3A%2F%2Fvertexaisearch.cloud.google.com%2Fgrounding-api-redirect%2FAUZIYQGL-7fg_XJ55MwWFHfPcbO7SnCfr1_dSFRoKiuun7iOKYZFamdDtQ1vT7E1oRmEWUpn3qfYejtAvgRVoKN72wGoY9SDiodm99DDc8J7dslJmuGzcgt17ugpTdqybHR4_V4ejNdSyu7rAqXbe-BTyGo-cVN9S0ZJwg%3D%3D" style="font-weight:500;text-decoration:none;font-family:inter,sans-serif">6</a>].</p></li><li style="font-family:inter,sans-serif;font-size:14px;font-weight:400;line-height:21px"><p style="font-size:14px;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:7px;margin-top:0px"><strong style="font-family:inter,sans-serif"><span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">GeoProximitySensor</span> Center Mismatch:</strong> There is an acknowledged schema issue regarding a mismatch between the <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">X3DEnvironmentalSensorNode</span>'s <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">center</span> field and the <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">GeoProximitySensor</span>'s <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">geoCenter</span>field. <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">geoCenter</span> is meant to be deprecated[<a href="https://www.google.com/url?sa=E&q=https%3A%2F%2Fvertexaisearch.cloud.google.com%2Fgrounding-api-redirect%2FAUZIYQGL-7fg_XJ55MwWFHfPcbO7SnCfr1_dSFRoKiuun7iOKYZFamdDtQ1vT7E1oRmEWUpn3qfYejtAvgRVoKN72wGoY9SDiodm99DDc8J7dslJmuGzcgt17ugpTdqybHR4_V4ejNdSyu7rAqXbe-BTyGo-cVN9S0ZJwg%3D%3D" style="font-weight:500;text-decoration:none;font-family:inter,sans-serif">6</a>], but the conflict has yet to be fully resolved in the text.</p></li><li style="font-family:inter,sans-serif;font-size:14px;font-weight:400;line-height:21px"><p style="font-size:14px;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:7px;margin-top:0px"><strong style="font-family:inter,sans-serif">Texture Node Hierarchy:</strong> In X3D 4.0/4.1, a new interface <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">X3DSingleTextureTransformNode</span>was introduced. <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">TextureTransform</span>, <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">TextureTransformMatrix3D</span>, and <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">TextureTransform3D</span> were shifted to inherit from this rather than <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">X3DTextureTransformNode</span>. The <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">mapping</span> field was moved to this intermediate interface, but some textual annotations in the 4.1 draft have not been fully scrubbed to reflect this inheritance[<a href="https://www.google.com/url?sa=E&q=https%3A%2F%2Fvertexaisearch.cloud.google.com%2Fgrounding-api-redirect%2FAUZIYQGL-7fg_XJ55MwWFHfPcbO7SnCfr1_dSFRoKiuun7iOKYZFamdDtQ1vT7E1oRmEWUpn3qfYejtAvgRVoKN72wGoY9SDiodm99DDc8J7dslJmuGzcgt17ugpTdqybHR4_V4ejNdSyu7rAqXbe-BTyGo-cVN9S0ZJwg%3D%3D" style="font-weight:500;text-decoration:none;font-family:inter,sans-serif">6</a>].</p></li><li style="font-family:inter,sans-serif;font-size:14px;font-weight:400;line-height:21px"><p style="font-size:14px;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:7px;margin-top:0px"><strong style="font-family:inter,sans-serif"><span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">upVector</span> Problems:</strong> Recent reviews on the Web3D-public mailing list have pointed out that the <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">upVector</span> field (used in camera and viewpoint nodes) is underspecified in the draft, leading to rendering inconsistencies across different X3D browsers when users rotate the scene[<a href="https://www.google.com/url?sa=E&q=https%3A%2F%2Fvertexaisearch.cloud.google.com%2Fgrounding-api-redirect%2FAUZIYQGme7OzSLqqidubm-NTRiU0ZG1IA3ZHi0fYi0UtTbHD8r_a4uk03UWMH3IXkyWucelokbT7a2Tdrpksi5eTEuyFdDCSPTfoeXfBxMX8bAyBno8lWOC3iMZFZ8cN2rjo-WmM3zqXayVX6Lm6qe2n0ofHK7yuw_HZaN8AKTL-AFnK2o50b8gQ" style="font-weight:500;text-decoration:none;font-family:inter,sans-serif">7</a>].</p></li><li style="font-family:inter,sans-serif;font-size:14px;font-weight:400;line-height:21px"><p style="font-size:14px;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:7px;margin-top:0px"><strong style="font-family:inter,sans-serif"><span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">FontLibrary</span> Typing:</strong> <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">FontLibrary</span> was incorrectly implemented as <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">X3DNode</span> in earlier drafts when it structurally needs to be <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">X3DChildNode</span>[<a href="https://www.google.com/url?sa=E&q=https%3A%2F%2Fvertexaisearch.cloud.google.com%2Fgrounding-api-redirect%2FAUZIYQGL-7fg_XJ55MwWFHfPcbO7SnCfr1_dSFRoKiuun7iOKYZFamdDtQ1vT7E1oRmEWUpn3qfYejtAvgRVoKN72wGoY9SDiodm99DDc8J7dslJmuGzcgt17ugpTdqybHR4_V4ejNdSyu7rAqXbe-BTyGo-cVN9S0ZJwg%3D%3D" style="font-weight:500;text-decoration:none;font-family:inter,sans-serif">6</a>].</p></li></ul><h3 style="margin:0px;font-family:inter,sans-serif;font-style:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:inherit;color:rgb(43,45,49)">3. Structural and Broken Link Issues</h3><ul style="padding-left:24px;font-family:inter,sans-serif;font-size:inherit;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(43,45,49)"><li style="font-family:inter,sans-serif;font-size:14px;font-weight:400;line-height:21px"><p style="font-size:14px;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:7px;margin-top:0px"><strong style="font-family:inter,sans-serif">Anchor Link Failures in Networking:</strong> Internal hyperlinks pointing to the <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">#EXPORTStatement</span> and <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">#IMPORTStatement</span> in the Networking Component HTML often fail to resolve properly or route users to the wrong section in the ClassicVRML/XML encoding pages because the anchors were stripped or renamed during document generation[<a href="https://www.google.com/url?sa=E&q=https%3A%2F%2Fvertexaisearch.cloud.google.com%2Fgrounding-api-redirect%2FAUZIYQE247EC8IW-9CY8m04H7rpiHFMp-t1xXvDITJE-nktRClTZsB2Y7YomxWYjZyUSxb5PsMaL4BUZCXIRXoBzMYQMQDboxLynzDqcv2UQwalUHgNc6pbtluIFkgsv7_qPI3-4rB2qe8DFMAofOKOhF5s7XVP3IGTNp89L_BPW8fuj5a8OYaI%3D" style="font-weight:500;text-decoration:none;font-family:inter,sans-serif">8</a>].</p></li><li style="font-family:inter,sans-serif;font-size:14px;font-weight:400;line-height:21px"><p style="font-size:14px;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:7px;margin-top:0px"><strong style="font-family:inter,sans-serif">Texture Projection Component Renaming:</strong> The component previously named <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">TextureProjector</span>was renamed to <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">TextureProjection</span> to avoid name overloading with actual node names[<a href="https://www.google.com/url?sa=E&q=https%3A%2F%2Fvertexaisearch.cloud.google.com%2Fgrounding-api-redirect%2FAUZIYQGL-7fg_XJ55MwWFHfPcbO7SnCfr1_dSFRoKiuun7iOKYZFamdDtQ1vT7E1oRmEWUpn3qfYejtAvgRVoKN72wGoY9SDiodm99DDc8J7dslJmuGzcgt17ugpTdqybHR4_V4ejNdSyu7rAqXbe-BTyGo-cVN9S0ZJwg%3D%3D" style="font-weight:500;text-decoration:none;font-family:inter,sans-serif">6</a>]. As a result, older URLs and internal cross-references looking for the <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">TextureProjector</span> component directory or anchors yield 404s or orphaned text.</p></li><li style="font-family:inter,sans-serif;font-size:14px;font-weight:400;line-height:21px"><p style="font-size:14px;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:7px;margin-top:0px"><strong style="font-family:inter,sans-serif">External Prototype / Draft References:</strong> Several URL examples in the draft still point to <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">v4.0</span> or HTTP (unsecured) examples rather than the current <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">v4.1</span> standard or HTTPS links, triggering warnings in stricter XML parsers.</p></li></ul><h3 style="margin:0px;font-family:inter,sans-serif;font-style:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:inherit;color:rgb(43,45,49)">4. Missing / Underspecified Features</h3><ul style="padding-left:24px;font-family:inter,sans-serif;font-size:inherit;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(43,45,49)"><li style="font-family:inter,sans-serif;font-size:14px;font-weight:400;line-height:21px"><p style="font-size:14px;line-height:21px;font-family:inter,sans-serif;font-weight:400;margin-bottom:7px;margin-top:0px"><strong style="font-family:inter,sans-serif"><span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">Skin</span> Node is Missing:</strong> While HAnim 2.1 is deeply tied to X3D 4.1[<a href="https://www.google.com/url?sa=E&q=https%3A%2F%2Fvertexaisearch.cloud.google.com%2Fgrounding-api-redirect%2FAUZIYQFBblIKFKWTIPSeDEBazJ130zJ1cQi4q2u8uwKyDYfnsxCbZVoJHbcg021O78D5SIs5Uq3suzMr-2TxHxzszN9BDhxjAH4IRIrbQI4GCSCQfTMXnRxyJLPqjSnHNg%3D%3D" style="font-weight:500;text-decoration:none;font-family:inter,sans-serif">2</a>], converters (such as those exporting <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">CesiumMan.gltf</span> to X3D) are trying to output <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">Skin</span> and <span style="border:medium;border-radius:4px;display:inline-block;font-family:"dm mono",monospace;font-size:1em;padding:0px 2px">ValueTrigger</span> nodes[<a href="https://www.google.com/url?sa=E&q=https%3A%2F%2Fvertexaisearch.cloud.google.com%2Fgrounding-api-redirect%2FAUZIYQEW4N6HpyevAuglagopqR6eQgyiEtrnjIfGWDCZTbTnSS-JQ9jYKZowVaI18-jpjHOgjAAIS-Rl2tYb2ygrH6BKn5TeLO5EUkRc7V2ysHbQqyfMjnxxmpjOjwWXdKPK7ZWBwLcCbnSqfkGWFdpBKnr5W8sW0dkkJe2V" style="font-weight:500;text-decoration:none;font-family:inter,sans-serif">9</a>]. These nodes are still highly experimental and lack complete, normative definitions in the current 4.1 CD rendering component text, causing files that use them to be marked as illegal/invalid by X3D Schematron validators.</p></li></ul></div>