<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Hi John, </p><p class=MsoNormal>The thing to do is to somehow hook up the gltf schema with the xml schema so that when a scene to be validated encounters imports it can just read the thing and proceed with the validation. I don’t see how to perform complete validation without examining imports. Or, is it OK to just say the file to be imported has been validated independently and so the file being validated is ok? </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Just amazing where this gltf json has become with so much progress in standards-track definition of the various objects and documentation. </p><p class=MsoNormal>Sorry to not study more on this but me, from the gltf json structure and schema, still thinking how to assemble the various gltf files to compose a real node like the hanim Displacer. Still looks like to me that their use is to import some known set of json objects to replace various fields in various x3d concrete nodes. For instance, an animation channel with known behavior so that the author only needs to define the files for the fields and supply target Route(s) from-to the target fields. This is perfect for building a general purpose animation prototype when we use a standard humanoid where behaviors can be developed then reused from a library. </p><p class=MsoNormal>Thanks, </p><p class=MsoNormal>Joe</p><p class=MsoNormal>.</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:yottzumm@gmail.com">John Carlson</a><br><b>Sent: </b>Sunday, March 20, 2022 11:56 AM<br><b>To: </b><a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>[x3d-public] glTF 2.0 schema</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Based on schema 2020-12:<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal><a href="https://github.com/KhronosGroup/glTF/tree/main/specification/2.0/schema">https://github.com/KhronosGroup/glTF/tree/main/specification/2.0/schema</a></p></div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Sorry for any confusion. I should have done research before blabbing.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>John</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>