<div dir="auto">Related, but unrelated ticket:</div><div dir="auto"><br></div><div dir="auto"><div><a href="https://sourceforge.net/p/x3d/tickets/37/">https://sourceforge.net/p/x3d/tickets/37/</a></div><br></div><div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, Jul 29, 2025 at 1:53 AM John Carlson <<a href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Interesting and important.  I already proposed an X3DParentNode that all nodes with children, addChildren and removeChildren fields could inherit from.  And of course, X3DGroupingNode would inherit from X3DParentNode.  <div dir="auto"><span style="color:rgb(0,0,0);font-family:'-apple-system',sans-serif;font-size:19px;font-style:normal;font-weight:400;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;display:inline!important;float:none">X3DParentNode would inherit from X3DNode.</span></div></div><div dir="auto"><br></div><div dir="auto">I’m not sure such a tight hierarchy is needed.</div><div dir="auto"><br></div><div dir="auto">But I, too, would like to hear comments.</div><div dir="auto"><br></div><div dir="auto">John<br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Mon, Jul 28, 2025 at 11:41 PM Don Brutzman via x3d-public <<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Found some small changes for XML Schema, DTD and specification during X3DJSAIL model debugging.<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">X3D DTD update activity:<br><a href="https://www.web3d.org/specifications/x3d-dtd-changelog.txt" target="_blank">https://www.web3d.org/specifications/x3d-dtd-changelog.txt</a><br>28 JUL 2025, brutzman<br>- (v3.2-4.0) add ScreenGroup to list of allowed GroupingNodes </blockquote><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">X3D XML Schema update activity:<br><a href="https://www.web3d.org/specifications/x3d-schema-changelog.txt" target="_blank">https://www.web3d.org/specifications/x3d-schema-changelog.txt</a><br>28 JUL 2025, brutzman<br>- (v3.2-4.0) add ScreenGroup to ChildContentModelFull group list of allowed GroupingNodes<br>- (v3.2-4.0) note Mantis 1501 specification issue: LayoutGroup is X3DNode, not an X3DGroupingNode</blockquote><div><br></div><div>Checking on corresponding changes revealed a mistaken node type in X3D Architecture.</div><div><ul><li>Mantis 1501: LayoutGroup needs to be X3DNode, not X3DGroupingNode</li><li><a href="https://mantis.web3d.org/view.php?id=1501" target="_blank">https://mantis.web3d.org/view.php?id=1501</a></li></ul><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> LayoutGroup needs to be X3DNode, not X3DGroupingNode</blockquote><div><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">* X3D Architecture, clause 36 Layout component, 36.4.2 LayoutGroup<br>* <a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD/Part01/components/layout.html#LayoutGroup" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD/Part01/components/layout.html#LayoutGroup</a> </blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">    LayoutGroup : X3DGroupingNode {</blockquote><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">However the spec prose also says<br>* "The LayoutGroup is a grouping node whose children are related by a common layout within a parent layout. Thus, a LayoutGroup can only be a child of a LayoutLayer node or another LayoutGroup node."</blockquote><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Some fields of X3DGroupingNode are provided, but others are not.</blockquote><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">A satisfactory replacement for X3DGroupingNode is X3DNode, which is less restrictive and not contradictory.</blockquote></div></div><div><br></div><div>Change applied to draft spec for review purposes.</div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><h2 style="margin-top:18px;color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif"><span title="Mantis 1501" style="background-color:yellow"><font size="2">36.4.2 LayoutGroup</font></span></h2></div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><pre style="color:rgb(0,0,0);font-size:11.05px;margin-left:25px">LayoutGroup : <span title="Mantis 1501" style="background-color:yellow">X3DNode</span> <span title="Mantis 1501" style="background-color:orange;text-decoration-line:line-through">X3DGroupingNode</span> {</pre></div></blockquote><div><br></div><div>Further review and comment welcome prior to eventual editors' review.</div><div><br></div><div>all the best, Don</div></div>
_______________________________________________<br>
x3d-public mailing list<br>
<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
</blockquote></div></div>
</blockquote></div></div>