<div dir="ltr">So I tried a less cumbersome task. Just comparing the HAnim hands and feet examples:<div><br></div><div>Don's version of JSON is on right, my version of JSON is on left.</div><div><br></div><div>$ node jsondiff.js ../data/HAnimModelsHandsFeet.json ~/x3dvalidate/HAnimModelsHandsFeet.json<br>================================================================================<br>C:\Users\coderextreme\X3DJSONLD\src\main\node\jsondiff.js ../data/HAnimModelsHan<br>dsFeet.json C:/Users/coderextreme/x3dvalidate/HAnimModelsHandsFeet.json<br>@2 /X3D/head/meta/17/@content/0/0 /X3D/head/meta/17/@content/0/0<br>< "5"<br>> "04"<br>@2 /X3D/head/meta/18/@content/0/0 /X3D/head/meta/18/@content/0/0<br>< "DOM2JSONSerializer.js,"<br>> "X3dToJson.xslt,"<br>@2 /X3D/head/meta/18/@content/1/0 /X3D/head/meta/18/@content/1/0<br>< "<a href="https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/node/DOM2JSONS">https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/node/DOM2JSONS</a><br>erializer.js"<br>> "<a href="https://www.web3d.org/x3d/stylesheets/X3dToJson.html">https://www.web3d.org/x3d/stylesheets/X3dToJson.html</a>"<br>@2 /X3D/head/meta/19/@content/3/0 /X3D/head/meta/19/@content/3/0<br>< "<a href="http://www.web3d.org/wiki/index.php/X3D_JSON_Encoding">http://www.web3d.org/wiki/index.php/X3D_JSON_Encoding</a>"<br>> "<a href="https://www.web3d.org/wiki/index.php/X3D_JSON_Encoding">https://www.web3d.org/wiki/index.php/X3D_JSON_Encoding</a>"<br>@7 /X3D/Scene/-children/3/Transform/-children/0/Inline/@displayBBox<br>> false<br>@7 /X3D/Scene/-children/3/Transform/-children/2/Transform/-children/0/Inline/@di<br>splayBBox<br>> false<br>@7 /X3D/Scene/-children/3/Transform/-children/2/Transform/@displayBBox<br>> false<br>@7 /X3D/Scene/-children/3/Transform/@displayBBox<br>> false<br>@7 /X3D/Scene/-children/4/Transform/-children/0/Inline/@displayBBox<br>> false<br>@7 /X3D/Scene/-children/4/Transform/@displayBBox<br>> false<br>@7 /X3D/Scene/-children/5/Transform/-children/1/Inline/@displayBBox<br>> false<br>@7 /X3D/Scene/-children/5/Transform/@displayBBox<br>> false<br>@7 /X3D/Scene/-children/6/Transform/-children/1/Inline/@displayBBox<br>> false<br>@7 /X3D/Scene/-children/6/Transform/@displayBBox<br>> false<br>@2 /X3D/JSON schema /X3D/JSON schema<br>< "<a href="http://www.web3d.org/specifications/x3d-4.0-JSONSchema.json">http://www.web3d.org/specifications/x3d-4.0-JSONSchema.json</a>"<br>> "<a href="http://www.web3d.org/specifications/x3d-3.3-JSONSchema.json">http://www.web3d.org/specifications/x3d-3.3-JSONSchema.json</a>"<br><br>Different!<br></div><div><br></div><div>However, the other ones are not so easy to compare. Can someone suggest good json diff tool? python's jsondiff tool is not good enough.</div><div><br>This one looks good! <a href="http://www.jsondiff.com/">http://www.jsondiff.com/</a> A bit cumbersome perhaps!</div><div><br></div><div>Thanks,</div><div><br></div><div>John</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 4, 2020 at 11:11 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:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">It would be very cool if I could launch a validator on a file from the command-line. I will look into it for JSON.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 4, 2020 at 11:08 PM John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I guess we're starting with the HAnim standard, and following it with tools. That is, the spec examples are for human consumption, not machine consumption.<div><br></div><div>Or..., should I look into extending the validator?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 4, 2020 at 10:59 PM John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I see 145 occurences leading line break after the leading " in an attribute in the standards examples under HumanoidAnimation/HAnimSpecificationsV2<br><div><br></div><div>$ grep '="$' KoreanCharacterAnnex* |wc<br> 145 398 13514<br></div><div><br></div><div>Hands and Feet in CharactersV2, 👍👍</div><div><br></div><div>Can the spec examples be put through a validator? Maybe I'll do that!</div><div><br></div><div>John</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 4, 2020 at 9:58 PM John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">For example, in values= and point= attributes in:<div><br></div><div><a href="http://www.web3d.org/x3d/content/examples/HumanoidAnimation/HAnimSpecificationV2/KoreanCharacterAnnexD01Jin.x3d" target="_blank">www.web3d.org/x3d/content/examples/HumanoidAnimation/HAnimSpecificationV2/KoreanCharacterAnnexD01Jin.x3d</a><br></div><div><br></div><div>(from the standard),</div><div><br></div><div>I see a leading line break after the leading " in the .x3d file. I will basically have to change ALL my code to expect this. This is NOT funny, and will require me to redo ALL my testing.</div><div><br>Giggle!</div><div><br></div><div>John</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 4, 2020 at 9:42 PM John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Would this ultimately, apply to ALL XML attributes? Need some help here!</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, May 3, 2020 at 1:06 PM John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I found some suggestions in the standards that one use 
 and 
, but no requirement???<div><br></div><div>The reason I mention this is because in the HAnim motion standard, there's examples that certainly look like a SFStrings that cover more than one line, without newline and carriage return encoding, as above. Plus the Motion interface has joints and channels as "string"s, not "sequence<string>"</div><div><br></div><div>I think the standard is correct, we just need to modify our schemas and X3DUOM to change MFString to SFString for joints and channels, if not already done.</div><div><br></div><div>I think I have heard from at least a couple of people that the standard is correct, but from one person, a negative.</div><div><br></div><div>I am not sure if this is a difference between HTML and XML?</div><div><br></div><div>This is timely, because people are implementing the new HAnim motion standard.</div><div><br></div><div>Comments? Corrections?</div><div><br></div><div>Thanks,</div><div><br></div><div>John</div></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>