<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><o:p> </o:p></p><p class=MsoNormal>John, and Don, </p><p class=MsoNormal>Thanks for the example johnJoint2 skeleton. Nice work on those ‘custom’ values you used. Am wishing the Hierarchy diagram included would reflect what is actually in the subject user code, for names and hierarchy of Joint and Segment and Site nodes, maybe even along with the measurements. </p><p class=MsoNormal>I can look at this in more detail, but </p><p class=MsoNormal> <meta name='modified' content="14 Jan 2023/></p><p class=MsoNormal>Fix this one, please. </p><p class=MsoNormal>The rest seems to run but since no viz of skeleton, hard to tell. That is why the Hierarchy.txt diagram for this example is so important as an author aid. People will add joints and then displacers to get special effects. </p><p class=MsoNormal>Finally, as an author, I would like to start with simple access to either changing or using all measurements in table a10 and a11 and then push the button to generate xml user code for the skeleton. </p><p class=MsoNormal>The hierarchy diagram is simple HAnim GUI that shows all joints, segments sites, dimensions and input/outputs. No need now for lines to show segment and site connections let’s just add the Segment, put on the Joint center marker and add a marker for Site(s) on that segment. Then, hook it up with an existing walk or run or animation to see how it works. Now it becomes possible to make a simple skin and hook it up. </p><p class=MsoNormal>Thanks again, </p><p class=MsoNormal>Joe</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, January 15, 2023 2:17 AM<br><b>To: </b><a href="mailto:brutzman@nps.edu">Don Brutzman</a>; <a href="mailto:joedwil@earthlink.net">Joe D Williams</a>; <a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>Fwd: HAnim Schematron warnings and X3DUOM incorrect?</p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Don, this is my highest priority/stopper now, but me resting even higher!</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Rather than patches right now, confirming the readings of the HAnim standard hierarchy, schematron diagnostics and X3DUOM is welcome. I hesitate moving from the parsing the hierarchy to X3DUOM.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I don’t want to patch my .x3d generator if schematron diagnostics are wrong.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>If necessary, i can apply patches to my Hierarchy.txt file or parser.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks!</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>John</p><div><div><p class=MsoNormal>---------- Forwarded message ---------<br>From: <strong><span style='font-family:"Calibri",sans-serif'>John Carlson</span></strong> <<a href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a>><br>Date: Sun, Jan 15, 2023 at 12:36 AM<br>Subject: Fwd: HAnim Schematron warnings and X3DUOM incorrect?<br>To: Don Brutzman <<a href="mailto:brutzman@nps.edu">brutzman@nps.edu</a>>, Joe D Williams <<a href="mailto:joedwil@earthlink.net">joedwil@earthlink.net</a>>, X3D Graphics public mailing list <<a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>></p></div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>Repeat email. Need to sync my HAnim Hierarchy.txt (attached, i hope, otherwise check HAnim standard) with X3DUOM and maybe XML Schema.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Very important for building LOA4 HAnim models and checking them with Schematron.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Schematron messages included. Please check against hierarchy in standard or my derivative.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I do understand that i may need a better introduction to the Hierarchy.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I’m trying to reduce the pain of recorrecting models that don’t match the standard.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks!</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>John </p></div><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>---------- Forwarded message ---------<br>From: <strong><span style='font-family:"Calibri",sans-serif'>John Carlson</span></strong> <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>><br>Date: Sat, Jan 14, 2023 at 3:20 AM<br>Subject: Re: HAnim Schematron output sampled<br>To: Joe D Williams <<a href="mailto:joedwil@earthlink.net" target="_blank">joedwil@earthlink.net</a>>, Don Brutzman <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>>, X3D Graphics public mailing list <<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>></p></div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>Whoops, I didn't provide zip. Attached.</p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Sat, Jan 14, 2023 at 2:58 AM John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>> wrote:</p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal style='margin-left:4.8pt'>Attached source for your perusal! Please run JohnJoint2.x3d through schematron and check messages in last message as reported by Schematron.</p><div><p class=MsoNormal style='margin-left:4.8pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:4.8pt'>See JohnJoint2.x3d and Hierarchy.txt</p></div><div><p class=MsoNormal style='margin-left:4.8pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:4.8pt'>Thanks!</p></div><div><p class=MsoNormal style='margin-left:4.8pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:4.8pt'>John</p><div><div><p class=MsoNormal style='margin-left:4.8pt'>---------- Forwarded message ---------<br>From: <strong><span style='font-family:"Calibri",sans-serif'>John Carlson</span></strong> <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>><br>Date: Sat, Jan 14, 2023 at 2:48 AM<br>Subject: HAnim Schematron output sampled<br>To: Joe D Williams <<a href="mailto:joedwil@earthlink.net" target="_blank">joedwil@earthlink.net</a>>, Don Brutzman <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>>, X3D Graphics public mailing list <<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>></p></div><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:4.8pt'><o:p> </o:p></p><div><div><div><p class=MsoNormal style='margin-left:4.8pt'>Misreading Hierarchy?</p></div><div><p class=MsoNormal style='margin-left:4.8pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:4.8pt'>Please check the Schematron hierarchy against these complaints. I think the schematron may be wrong. I will send along the model when I get a zip.</p></div><div><p class=MsoNormal style='margin-left:4.8pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:4.8pt'><HAnimJoint DEF='hanim_vl5' name='vl5'/> has parent HAnimJoint name='humanoid_root' rather than expected parent name='sacroiliac', recommend checking model [/X3D/Scene/HAnimHumanoid/HAnimJoint[1]/HAnimJoint[2], warning]</p></div><div><p class=MsoNormal style='margin-left:4.8pt'><HAnimJoint DEF='hanim_l_sternoclavicular' name='l_sternoclavicular'/> has parent HAnimJoint name='vt1' rather than expected parent name='vc7', recommend checking model [/X3D/Scene/HAnimHumanoid/HAnimJoint[1]/HAnimJoint[2]/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint[2], warning]</p></div><div><p class=MsoNormal style='margin-left:4.8pt'><HAnimJoint DEF='hanim_r_sternoclavicular' name='r_sternoclavicular'/> has parent HAnimJoint name='vt1' rather than expected parent name='vc7', recommend checking model [/X3D/Scene/HAnimHumanoid/HAnimJoint[1]/HAnimJoint[2]/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint/HAnimJoint[3], warning]</p></div></div></div></div></div></div></blockquote></div></div></div></div></div><p class=MsoNormal style='margin-left:4.8pt'><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>