<div><div dir="auto">I just discovered this draft. Sorry for the delay. I think the primary goal should be the alignment of the statement type hierarchy between X3D3 and X3D4.</div><div dir="auto"><br></div><div dir="auto">I’m wondering if my changes locally affected fieldValue.setIS as previously reported? Or fieldValue.addChild(new IS()) (IS is not a node)</div><div dir="auto"><br></div><div dir="auto">I am thinking someone should look at the type hierarchy differences for statements. If we go with X3D4, I will upgrade various examples.</div><div dir="auto"><br></div><div dir="auto">I guess the other solution is to provide different jars for X3D3 versus X3D4.</div><div dir="auto"><br></div><div dir="auto">John</div></div><div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Aug 28, 2021 at 4:09 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-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">I'm still having to back out updates to X3DUOM:<br>
<br>
$ grep SceneGraphStructureStatement X3dUnifiedObjectModel*|sort -u<br>
X3dUnifiedObjectModel-3.0.xml: <Inheritance <br>
baseType="SceneGraphStructureStatement"/><br>
X3dUnifiedObjectModel-3.1.xml: <Inheritance <br>
baseType="SceneGraphStructureStatement"/><br>
X3dUnifiedObjectModel-3.2.xml: <Inheritance <br>
baseType="SceneGraphStructureStatement"/><br>
X3dUnifiedObjectModel-3.3.xml: <Inheritance <br>
baseType="SceneGraphStructureStatement"/><br>
<br>
Here's what's in the old X3D3 versions, but not 4.0:<br>
<br>
<AbstractNodeType name="SceneGraphStructureStatement"><br>
<InterfaceDefinition <br>
specificationUrl="<a href="https://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/concepts.html#scenegraph" rel="noreferrer" target="_blank">https://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/concepts.html#scenegraph</a>"<br>
appinfo="SceneGraphStructureStatement is a marker interface that <br>
identifies statements relating to nonrenderable scene graph structure. <br>
SceneGraphStructureStatement does not extend from any other node type <br>
since it is not an explicit part of the X3D node interface hierarchy, <br>
and DEF/USE is not appropriate for such statements."><br>
<componentInfo name="Core" level="1"/><br>
<field name="class"<br>
type="SFString"<br>
accessType="inputOutput"<br>
baseType="xs:NMTOKENS"<br>
description="The class attribute on each X3D node <br>
and statement is a space-separated list of classes, reserved for use by <br>
Cascading Style Sheets (CSS) and XML stylesheets."/><br>
</InterfaceDefinition><br>
</AbstractNodeType><br>
<br>
<br>
I am proceeding to delete the Inheritance nodes from my versions 3 <br>
X3DUOM. There are some "AdditionalInheritance" elements that may need to <br>
be converted over to "Inheritance."<br>
<br>
If you want me to proceed with updating X3DUOM and AdditionalInheritance <br>
on <a href="http://sourceforge.net" rel="noreferrer" target="_blank">sourceforge.net</a>, let me know, but that's treading on unknown <br>
territory for me, updating the stuff that creates X3DUOM. I assume this <br>
means updating XML schema versions 3. Is there a Mantis issue yet? I am <br>
capable of filing one, I hope.<br>
<br>
I am not currently testing anything that uses X3DUOM besides my own <br>
stuff. Mostly, I am just trying to get the JSON schema working.<br>
<br>
Thanks!<br>
<br>
John<br>
<br>
</blockquote></div></div>
</div>