<div dir="auto">Yes, LOA 1, 2, 3 use</div><div dir="auto"><br></div><div dir="auto"><span style="border-color:rgb(0,0,0) rgb(0,0,0) rgb(0,0,0) rgb(204,204,204);color:rgb(0,0,0)"> l_metatarsophalangeal_2 </span><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jan 23, 2021 at 6:51 PM John Carlson <<a href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">Perhaps we should look at the hierarchies in the spec:<br>
<br>
Hier1.txt: | | l_metatarsophalangeal_2 : l_tarsal_proximal_phalanx_2<br>
Hier1.txt: | r_metatarsophalangeal_2 : r_tarsal_proximal_phalanx_2<br>
Hier2.txt: | | l_metatarsophalangeal_2 : l_tarsal_proximal_phalanx_2<br>
Hier2.txt: | r_metatarsophalangeal_2 : r_tarsal_proximal_phalanx_2<br>
Hier3.txt: | | l_metatarsophalangeal_2 : l_tarsal_proximal_phalanx_2<br>
Hier3.txt: | r_metatarsophalangeal_2 : r_tarsal_proximal_phalanx_2<br>
Hier4.txt: | | | | l_metatarsophalangeal_1 : <br>
l_tarsal_proximal_phalanx_1<br>
Hier4.txt: | | | | l_metatarsophalangeal_2 : <br>
l_tarsal_proximal_phalanx_2<br>
Hier4.txt: | | | l_metatarsophalangeal_3 : <br>
l_tarsal_proximal_phalanx_3<br>
Hier4.txt: | | | l_metatarsophalangeal_4 : <br>
l_tarsal_proximal_phalanx_4<br>
Hier4.txt: | | l_metatarsophalangeal_5 : <br>
l_tarsal_proximal_phalanx_5<br>
Hier4.txt: | | | r_metatarsophalangeal_1 : <br>
r_tarsal_proximal_phalanx_1<br>
Hier4.txt: | | | r_metatarsophalangeal_2 : <br>
r_tarsal_proximal_phalanx_2<br>
Hier4.txt: | | r_metatarsophalangeal_3 : <br>
r_tarsal_proximal_phalanx_3<br>
Hier4.txt: | | r_metatarsophalangeal_4 : <br>
r_tarsal_proximal_phalanx_4<br>
Hier4.txt: | r_metatarsophalangeal_5 : <br>
r_tarsal_proximal_phalanx_5<br>
Hierarchy.txt: | | | | l_metatarsophalangeal_1 : <br>
l_tarsal_proximal_phalanx_1<br>
Hierarchy.txt: | | | | l_metatarsophalangeal_2 : <br>
l_tarsal_proximal_phalanx_2<br>
Hierarchy.txt: | | | l_metatarsophalangeal_3 : <br>
l_tarsal_proximal_phalanx_3<br>
Hierarchy.txt: | | | l_metatarsophalangeal_4 : <br>
l_tarsal_proximal_phalanx_4<br>
Hierarchy.txt: | | l_metatarsophalangeal_5 : <br>
l_tarsal_proximal_phalanx_5<br>
Hierarchy.txt: | | | r_metatarsophalangeal_1 : <br>
r_tarsal_proximal_phalanx_1<br>
Hierarchy.txt: | | | r_metatarsophalangeal_2 : <br>
r_tarsal_proximal_phalanx_2<br>
Hierarchy.txt: | | r_metatarsophalangeal_3 : <br>
r_tarsal_proximal_phalanx_3<br>
Hierarchy.txt: | | r_metatarsophalangeal_4 : <br>
r_tarsal_proximal_phalanx_4<br>
Hierarchy.txt: | r_metatarsophalangeal_5 : <br>
r_tarsal_proximal_phalanx_5<br>
<br>
<br>
All have the digit. So it's more on the authoring side, I would say.<br>
<br>
<br>
John<br>
<br>
On 1/23/21 6:10 PM, Don Brutzman wrote:<br>
> You are correct to flag these other issues.<br>
><br>
> Please look at what I wrote, I think that the solution I proposed <br>
> should work by mapping the four missing LOA-2 and LOA-3 joint names to <br>
> the corresponding first LOA-4 joint name.<br>
><br>
> We'll see what Joe says and then apply/test the best path forward.<br>
><br>
> On 1/23/2021 3:46 PM, John Carlson wrote:<br>
>><br>
>><br>
>> I will have to figure out how to change my skeleton build, it relies on<br>
>> sections cut out of the spec.<br>
>><br>
>> It would probably be good to collect all errors like this, as there may<br>
>> be more. Did you check for "r_metatarsophalangeal" and<br>
>><br>
>> r_metatarsophalangeal_1<br>
>> r_metatarsophalangeal_2<br>
>> r_metatarsophalangeal_3<br>
>> r_metatarsophalangeal_4<br>
>> r_metatarsophalangeal_5<br>
>><br>
>> in the X3D schema or X3DUOM?<br>
>><br>
>> On 1/23/21 5:31 PM, Don Brutzman wrote:<br>
>>> [cc: Joe, x3d-public, hanim]<br>
>>><br>
>>> John, like you, am not finding "l_metatarsophalangeal" in current X3D<br>
>>> Schema or X3DUOM. Instead am finding<br>
>>><br>
>>> l_metatarsophalangeal_1<br>
>>> l_metatarsophalangeal_2<br>
>>> l_metatarsophalangeal_3<br>
>>> l_metatarsophalangeal_4<br>
>>> l_metatarsophalangeal_5<br>
>>><br>
>>> Close reading of these HAnimJoint names will note the prefixes l_ and<br>
>>> r_ are alphabetic, while suffixes _1 _2 _3 _4 _5 are numeric.<br>
>>><br>
>>> However, like you, am nevertheless finding "l_metatarsophalangeal" in<br>
>>> current HAnim Specification in both animation examples but also Part 1<br>
>>> Concepts.<br>
>>><br>
>>> [1] HAnim version 2<br>
>>> <a href="https://www.web3d.org/documents/specifications/19774/V2.0/index.html" rel="noreferrer" target="_blank">https://www.web3d.org/documents/specifications/19774/V2.0/index.html</a><br>
>>><br>
>>> [2] Part 1: Humanoid animation (HAnim) architecture, 4 Concepts,<br>
>>> 4.9.4 The feet<br>
>>> <a href="https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/concepts.html#TheFeet" rel="noreferrer" target="_blank">https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/concepts.html#TheFeet</a> <br>
>>><br>
>>><br>
>>> This paragraph has a layout problem, now entered as Mantis<br>
>>><br>
>>> [3] Mantis 1338: HAnim part 1 clause 4.9.4 has malformed HTML<br>
>>> <a href="https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/concepts.html#TheFeet" rel="noreferrer" target="_blank">https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/concepts.html#TheFeet</a> <br>
>>><br>
>>><br>
>>> (Am guessing we missed this during prior document review because it<br>
>>> was offscreen on the far-right margin.)<br>
>>><br>
>>> Dick, first correction: please advise how we can resolve this layout<br>
>>> issue which relates to whitespace, not prose.<br>
>>><br>
>>> Dick, please also monitor the following resolution and let's decide if<br>
>>> additional prose is appropriate too.<br>
>>><br>
>>> ---<br>
>>><br>
>>> The clause itself reads as follows:<br>
>>><br>
>>>> 4.9.4 The feet<br>
>>>><br>
>>>> The names of the Joint objects for the LOA‑2 and 3 feet are specified<br>
>>>> in Table 4.4.<br>
>>>><br>
>>>> Table 4.4 — LOA‑2 and 3 foot Joint object names<br>
>>>><br>
>>>> Left foot<br>
>>>> l_talocrural l_tarsometatarsal l_metatarsophalangeal<br>
>>>> l_tarsal_interphalangeal<br>
>>>><br>
>>>> Right foot<br>
>>>> r_talocrural r_tarsometatarsal r_metatarsophalangeal<br>
>>>> r_tarsal_interphalangeal<br>
>>><br>
>>> Corresponding joints with _1 _2 _3 _4 _5 appended are found in<br>
>>><br>
>>> [4] Figure 4.9 — LOA‑4 foot joints<br>
>>> <a href="https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/concepts.html#f-FootJoints" rel="noreferrer" target="_blank">https://www.web3d.org/documents/specifications/19774/V2.0/Architecture/concepts.html#f-FootJoints</a> <br>
>>><br>
>>><br>
>>> Joe, second correction: I think that we missed defining 'alias'<br>
>>> values for this difference between LOA-2/LOA-3 and LOA-4.<br>
>>><br>
>>> Proposed fix: define alias correspondences in X3D XML Schema, X3DUOM<br>
>>> and corresponding Quality Assurance (QA) diagnostics such as X3D<br>
>>> Schematron and X3D Tooltips.<br>
>>><br>
>>> l_talocrural l_talocrural_1<br>
>>> l_tarsometatarsal l_tarsometatarsal_1<br>
>>> l_metatarsophalangeal l_metatarsophalangeal_1<br>
>>> l_tarsal_interphalangeal l_tarsal_interphalangeal_1<br>
>>><br>
>>> r_talocrural r_talocrural_1<br>
>>> r_tarsometatarsal r_tarsometatarsal_1<br>
>>> r_metatarsophalangeal r_metatarsophalangeal_1<br>
>>> r_tarsal_interphalangeal r_tarsal_interphalangeal_1<br>
>>><br>
>>> Please let me know what you think about these alias additions. <br>
>>> Entered as<br>
>>><br>
>>> [5] Mantis 1339: missing alias correspondences for foot joints<br>
>>> LOA-2/LOA-3 and LOA-4<br>
>>> <a href="https://www.web3d.org/member-only/mantis/view.php?id=1339" rel="noreferrer" target="_blank">https://www.web3d.org/member-only/mantis/view.php?id=1339</a><br>
>>><br>
>>> John, if accepted, that change will clear the diagnostic errors you<br>
>>> encountered. Thanks for pursuing this tricky problem, am happy to<br>
>>> confirm that your diagnosis was exactly on target.<br>
>>><br>
>>> Pretty tricky problem, but appears to have a straightforward<br>
>>> solution. Please advise what you think.<br>
>>><br>
>>><br>
>>> On 1/21/2021 3:34 PM, John Carlson wrote:<br>
>>>><br>
>>>> Appears valid in spec.<br>
>>>><br>
>>>> $ find . -type f -print0 |xargs -0 grep -w l_metatarsophalangeal|grep<br>
>>>> -e -IS|grep l_metatarsophalangeal<br>
>>>> ./ISO-IEC19774/ISO-IEC19774-2/ISO-IEC19774-2v2.0/ISO-IEC19774-2v2.0-IS/MotionDataAnimation/ExampleMocapAnimationInterpolators.html: <br>
>>>><br>
>>>> <HAnimJoint DEF="hanim_l_metatarsophalangeal" center="3.854 3.64<br>
>>>> 0.7402" name="l_metatarsophalangeal" ><br>
>>>> ./ISO-IEC19774/ISO-IEC19774-2/ISO-IEC19774-2v2.0/ISO-IEC19774-2v2.0-IS/MotionDataAnimation/Concepts.html: <br>
>>>><br>
>>>> <td class="center">l_metatarsophalangeal</td><br>
>>>> ./ISO-IEC19774/ISO-IEC19774-2/ISO-IEC19774-2v2.0/ISO-IEC19774-2v2.0-IS/MotionDataAnimation/Concepts.html: <br>
>>>><br>
>>>> <td class="center">l_metatarsophalangeal</td><br>
>>>> ./ISO-IEC19774/ISO-IEC19774-2/ISO-IEC19774-2v2.0/ISO-IEC19774-2v2.0-IS/MotionDataAnimation/Concepts.html: <br>
>>>><br>
>>>> <li>The <code>l_metatarsophalangeal</code> <span<br>
>>>> class="Object">Joint</span> has the motion of [R17]<br>
>>>> ./ISO-IEC19774/ISO-IEC19774-2/ISO-IEC19774-2v2.0/ISO-IEC19774-2v2.0-IS/MotionDataAnimation/ExampleKeyframeAnimation.html: <br>
>>>><br>
>>>> <HAnimJoint DEF="hanim_l_metatarsophalangeal" center="3.854 3.64<br>
>>>> 0.7402" name="l_metatarsophalangeal" ><br>
>>>> ./ISO-IEC19774/ISO-IEC19774-2/ISO-IEC19774-2v2.0/ISO-IEC19774-2v2.0-IS/MotionDataAnimation/ExampleMocapAnimationMotionObject.html: <br>
>>>><br>
>>>> <HAnimJoint DEF="hanim_l_metatarsophalangeal" center="3.854 3.64<br>
>>>> 0.7402" name="l_metatarsophalangeal" ><br>
>>>> ./ISO-IEC19774/ISO-IEC19774-1/ISO-IEC19774-1v2.0/ISO-IEC19774-1v2.0-IS/Architecture/Design.html: <br>
>>>><br>
>>>> <HAnimJoint DEF="hanim_l_metatarsophalangeal"<br>
>>>> center="3.854000 3.640000 0.740200"<br>
>>>> name="l_metatarsophalangeal" ><br>
>>>> ./ISO-IEC19774/ISO-IEC19774-1/ISO-IEC19774-1v2.0/ISO-IEC19774-1v2.0-IS/Architecture/concepts.html: <br>
>>>><br>
>>>> <td>l_metatarsophalangeal</td><br>
>>>><br>
>>>> But not in XML schema or X3DUOM. Hmm.<br>
>>>><br>
>>>> coderextreme@coderextreme-Kubuntu20:/c/x3d-code/<a href="http://www.web3d.org/specifications$" rel="noreferrer" target="_blank">www.web3d.org/specifications$</a> <br>
>>>><br>
>>>> find . -type f -print0 |xargs -0 grep -w l_metatarsophalangeal<br>
>>>> coderextreme@coderextreme-Kubuntu20:/c/x3d-code/<a href="http://www.web3d.org/specifications$" rel="noreferrer" target="_blank">www.web3d.org/specifications$</a> <br>
>>>><br>
>>>><br>
>>>><br>
>>>> So there must be some disconnect between the spec and the schema?<br>
>>>><br>
>>>><br>
>>>> HAnim examples to test against:<br>
>>>><br>
>>>> coderextreme@coderextreme-Kubuntu20:/c/x3d-code/<a href="http://www.web3d.org/x3d/content/examples/HumanoidAnimation$" rel="noreferrer" target="_blank">www.web3d.org/x3d/content/examples/HumanoidAnimation$</a> <br>
>>>><br>
>>>> find . -type f -print0 |xargs -0 grep -wl l_metatarsophalangeal<br>
>>>><br>
>>>> ./Characters/JinLOA3.x3d<br>
>>>> ./Characters/JinLOA1.x3d<br>
>>>> ./Characters/JinLOA2.x3d<br>
>>>> ./Specifications/KoreanCharacterMotionAnnexD01Jin.x3d<br>
>>>> ./Specifications/KoreanCharacterMotionAnnexC01Jin.x3d<br>
>>>><br>
>>>> The unrecognized value errors are in your build.log.txt.<br>
>>>><br>
>>>> Thanks for looking at this!<br>
>>>><br>
>>>> John<br>
>>>><br>
>>>><br>
>>>> On 1/21/21 5:15 PM, John Carlson wrote:<br>
>>>>> I believe I am using X3DJSAIL. Do I need to do a build/checkout<br>
>>>>> or download jars?<br>
>>>>><br>
>>>>> It would be good to cross test with stylesheet.<br>
>>>>><br>
>>>>> I’ll try to remember to look into it tonight. Resting now.<br>
>>>>><br>
>>>>> John<br>
>>>>> On Thu, Jan 21, 2021 at 10:57 AM Don Brutzman <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a><br>
>>>>> <mailto:<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>>> wrote:<br>
>>>>><br>
>>>>> Thanks for checking John. Wondering, are you checking HAnim<br>
>>>>> specification, X3DUOM or X3D Schema for correct values?<br>
>>>>><br>
>>>>> We can also define alias enumerations if there are allowable<br>
>>>>> synonyms.<br>
>>>>><br>
>>>>> On 1/20/2021 9:07 PM, John Carlson wrote:<br>
>>>>> ><br>
>>>>> ><br>
>>>>> > Running with nashorn.<br>
>>>>> ><br>
>>>>> > jjs -J-Xss1g -J-Xmx4g<br>
>>>>> ><br>
>>>>> -J-Djava.class.path=.:/home/coderextreme/pythonSAI/X3DJSAIL.4.0.full.jar:/home/coderextreme/X3DJSONLD/saxon9he.jar:/home/coderextreme/X3DJSONLD/target/X3DJSONLD-1.0-SNAPSHOT.jar:/home/coderextreme/X3DJSONLD/src/main/nashorn <br>
>>>>><br>
>>>>> ><br>
>>>>> ../nashorn/net/coderextreme/data/KoreanCharacterMotionAnnexC01Jin.js<br>
>>>>> > Warning: The jjs tool is planned to be removed from a future<br>
>>>>> JDK release<br>
>>>>> > Warning: HAnimJoint name newValue="l_metatarsophalangeal" <br>
>>>>> has an<br>
>>>>> > unrecognized value not matching any of the optional string<br>
>>>>> tokens.<br>
>>>>> > Warning: HAnimJoint name newValue="r_metatarsophalangeal" <br>
>>>>> has an<br>
>>>>> > unrecognized value not matching any of the optional string<br>
>>>>> tokens.<br>
>>>>> ><br>
>>>>> > jjs -J-Xss1g -J-Xmx4g<br>
>>>>> ><br>
>>>>> -J-Djava.class.path=.:/home/coderextreme/pythonSAI/X3DJSAIL.4.0.full.jar:/home/coderextreme/X3DJSONLD/saxon9he.jar:/home/coderextreme/X3DJSONLD/target/X3DJSONLD-1.0-SNAPSHOT.jar:/home/coderextreme/X3DJSONLD/src/main/nashorn <br>
>>>>><br>
>>>>> ><br>
>>>>> ../nashorn/net/coderextreme/data/KoreanCharacterMotionAnnexD01Jin.js<br>
>>>>> > Warning: The jjs tool is planned to be removed from a future<br>
>>>>> JDK release<br>
>>>>> > Warning: HAnimJoint name newValue="l_metatarsophalangeal" <br>
>>>>> has an<br>
>>>>> > unrecognized value not matching any of the optional string<br>
>>>>> tokens.<br>
>>>>> ><br>
>>>>> > Related X3D files found in:<br>
>>>>> ><br>
>>>>> ><br>
>>>>> /c/x3d-code/<a href="http://www.web3d.org/x3d/content/examples/HumanoidAnimation/Specifications/" rel="noreferrer" target="_blank">www.web3d.org/x3d/content/examples/HumanoidAnimation/Specifications/</a> <br>
>>>>><br>
>>>>> <<a href="http://www.web3d.org/x3d/content/examples/HumanoidAnimation/Specifications/" rel="noreferrer" target="_blank">http://www.web3d.org/x3d/content/examples/HumanoidAnimation/Specifications/</a>> <br>
>>>>><br>
>>>>><br>
>>>>> ><br>
>>>>> > X3D files up to date:<br>
>>>>> ><br>
>>>>> ><br>
>>>>> coderextreme@coderextreme-Kubuntu20:/c/x3d-code/<a href="http://www.web3d.org/x3d/content/examples/HumanoidAnimation$" rel="noreferrer" target="_blank">www.web3d.org/x3d/content/examples/HumanoidAnimation$</a> <br>
>>>>><br>
>>>>> <<a href="http://www.web3d.org/x3d/content/examples/HumanoidAnimation$" rel="noreferrer" target="_blank">http://www.web3d.org/x3d/content/examples/HumanoidAnimation$</a>><br>
>>>>> > diff Specifications/ ~/X3DJSONLD/src/main/data/|grep diff<br>
>>>>> ><br>
>>>>> coderextreme@coderextreme-Kubuntu20:/c/x3d-code/<a href="http://www.web3d.org/x3d/content/examples/HumanoidAnimation$" rel="noreferrer" target="_blank">www.web3d.org/x3d/content/examples/HumanoidAnimation$</a> <br>
>>>>><br>
>>>>> <<a href="http://www.web3d.org/x3d/content/examples/HumanoidAnimation$" rel="noreferrer" target="_blank">http://www.web3d.org/x3d/content/examples/HumanoidAnimation$</a>><br>
>>>>> > svn up<br>
>>>>> > Updating '.':<br>
>>>>> > At revision 31305.<br>
>>>>> ><br>
>>>>> > John<br>
>>><br>
>>> all the best, Don<br>
><br>
> all the best, Don<br>
</blockquote></div></div>