<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:191722949;
mso-list-type:hybrid;
mso-list-template-ids:-1164291478 -1 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:\F0D8;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body lang=EN-US link=blue vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>I know that some HAnim examples cause my X3DJSONLD system to “go out to lunch” for a while, or fail to sync up beginning and ending tags.<o:p></o:p></li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>For hanim, please work on the jin loa4. If we can be sure that is correct, then we can use it as the basis for updated part 1 annex a because I think it has the correct hanim2 names and hierarchy.<o:p></o:p></p><p class=MsoNormal>Thank,<o:p></o:p></p><p class=MsoNormal>Joe <o:p></o:p></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>Saturday, December 11, 2021 2:42 PM<br><b>To: </b><a href="mailto:x3d-public@web3d.org">X3D-Public</a><br><b>Cc: </b><a href="mailto:holger.seelig@yahoo.de">Holger Seelig</a>; <a href="mailto:andreasplesch@gmail.com">Andreas Plesch</a>; <a href="mailto:joedwil@earthlink.net">Joseph D Williams</a><br><b>Subject: </b>Re: Log4j and what it means for encodings</p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>All,<o:p></o:p></p><div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>I’m afraid to introduce this subject, but since I am apparently the QA for the X3D JSON examples, I do feel fairly confident there no examples in the X3D Resources Examples that will break one’s standard JSON parser. I guess the defensive tests may be in SavageDefense. Should we do some examples that can break typical parsers and validators, so browser developers can get more comfortable with their systems? Could this be added to the ConformanceNist examples?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I know that some HAnim examples cause my X3DJSONLD system to “go out to lunch” for a while, or fail to sync up beginning and ending tags.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I suggest we go through my online examples previously posted try to patch what we can. Here’s my current list of examples, from a previous message starting with “Status”. <a href="https://coderextreme.net/X3DJSONLD/src/main/html/codex.html">https://coderextreme.net/X3DJSONLD/src/main/html/codex.html</a>. The message made assignments as I saw fit, but I encourage you to go through your assigned list, I believe I am pointed at development or recent releases of X_ITE and X3DOM.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Apple Mail is making my life miserable. Going back to gmail. Why did I ever leave?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>John<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Sent from my iPad<o:p></o:p></p></div><div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='margin-bottom:12.0pt'>On Dec 11, 2021, at 3:37 PM, John Carlson <yottzumm@gmail.com> wrote:<o:p></o:p></p></blockquote></div></div></div></div></div><p class=MsoNormal style='mso-margin-top-alt:5.0pt;margin-right:.5in;margin-bottom:5.0pt;margin-left:.5in'>Apparently there is a denial of service attack happening on log4j/struts/soap. Imagine your X3D xml/json/VRML having millions of nested Groups and transforms. How can we defend ourselves, and what limits can we set in place? I do know tail recursion can help, but I’m not sure what happens when there are too many stack frames to open.<br><br>I know the standard talks about limits on these things, but is there a limit of depth of nested nodes in the standard? I will do some googling.<br><br>Sent from my iPad<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>