<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Actually, the main focus of this thread was:</p>
<p>There are many '<Inheritance
baseType="SceneGraphStructureStatement"/>' in X3DUOM
V3.0-V3.3. There is no AbstractNodeType of
SceneGraphStructureStatement in V3.* any more.<br>
</p>
<p>I don't know if you want to remove the Inheritance or not. There
are '<xs:complexType name="SceneGraphStructureStatement"
abstract="true">' in the XML schema V3.*. The complexType seems
to have disappeared in translation to X3DUOM V3.*<br>
</p>
<p>I will assume that the conversion from XML Schema to X3DUOM is
broken for V3.*</p>
<p>I could dig a bit further, but at this point, I think an issue of
transferring complexTypes from XML Schema to X3DUOM V3.* has been
identifiied.</p>
<p>I agree that V3.* is deprecated at this point. Ideally, we
could get JSON Schemas checked into sourceforge.<br>
</p>
<p>Likely, you are in the middle of testing.</p>
<p>Going back into my cave.</p>
<p>John<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 9/14/21 2:53 PM, John Carlson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGC3UE=W6M=hS5nTjU9-hUnkmHVEp1q9adV36S_Wir2Bnw4rGQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">It sounds like we should focus on JSON schema 4.0,
and leave old schemas behind.</div>
<div dir="auto"><br>
</div>
<div dir="auto">I have been validating files against various JSON
schema versions.</div>
<div dir="auto"><br>
</div>
<div dir="auto">I think my main problem was setIS in a field
value, which we started addressing Monday.</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">I have a list of pressing issues if you’re ready.</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Sep 14, 2021 at 2:36
PM Brutzman, Donald (Don) (CIV) <<a
href="mailto:brutzman@nps.edu" moz-do-not-send="true">brutzman@nps.edu</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)">
<div link="blue" vlink="#954F72"
style="word-wrap:break-word" lang="EN-US">
<div class="m_997246790946943590WordSection1">
<p class="MsoNormal">Regarding backwards compatibility:</p>
<p class="MsoNormal"> </p>
<ul style="margin-top:0in" type="disc">
<li class="m_997246790946943590MsoListParagraph"
style="margin-left:0in">XML Schemas are available
for all versions of X3D, 3.0 through 4.0, Each has
evolved past the prior version.</li>
<li class="m_997246790946943590MsoListParagraph"
style="margin-left:0in">X3DUOM is autogenerated from
each corresponding XML schema, similarly showing
evolution.</li>
<li class="m_997246790946943590MsoListParagraph"
style="margin-left:0in">We have paid a lot of
attention to forward/backward compatibility among
these many versions of X3D and VRML97.</li>
</ul>
<p class="MsoNormal"> </p>
<p class="MsoNormal">It is possible to maintain multiple
versions of corresponding software builds but that
seems fairly counterproductive. Better is strategy at
top of X3DJSAIL page:</p>
<ul type="disc">
<li class="MsoNormal" style="color:black">
<span
style="font-size:13.5pt;font-family:"Times
New Roman",serif">Test ongoing development
of <a href="https://www.web3d.org/x3d4"
target="_blank" style="font-family:"Times
New Roman",serif" moz-do-not-send="true">X3D
version 4</a> (also supporting X3D versions 3.0
through 3.3).</span></li>
</ul>
<p class="MsoNormal">So X3DJSAIL, X3DPSAIL and X3D
Ontology (and for that matter XML Schema and X3D
DOCTYPE) are focused on 4.0 completeness in each
implementation, including backwards compatibility to
good effect.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thus X3DUOM updates are not
postponed at all, rather these match exactly each
version of the X3D Specification as captured by X3D
XML Schemas.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Hope this is clearer now.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">all the best, Don</p>
</div>
</div>
<div link="blue" vlink="#954F72"
style="word-wrap:break-word" lang="EN-US">
<div class="m_997246790946943590WordSection1">
<p class="MsoNormal"><br>
<span style="font-size:10pt;font-family:"Courier
New"">-- <br>
Don Brutzman Naval Postgraduate School, Code
USW/Br <a href="mailto:brutzman@nps.edu"
target="_blank" style="font-family:"Courier
New"" moz-do-not-send="true">brutzman@nps.edu</a><br>
Watkins 270, MOVES Institute, Monterey CA
93943-5000 USA +1.831.656.2149<br>
X3D graphics, virtual worlds, navy robotics <a
href="http://faculty.nps.edu/brutzman"
target="_blank" style="font-family:"Courier
New"" moz-do-not-send="true">
http://faculty.nps.edu/brutzman</a></span></p>
<p class="MsoNormal"> </p>
<div style="border-style:solid none
none;border-top-width:1pt;padding:3pt 0in
0in;border-top-color:rgb(225,225,225)">
<p class="MsoNormal" style="border:none;padding:0in"><b>From:
</b><a href="mailto:yottzumm@gmail.com"
target="_blank" moz-do-not-send="true">John
Carlson</a><br>
<b>Sent: </b>Tuesday, September 7, 2021 10:42 AM<br>
<b>To: </b><a href="mailto:x3d-public@web3d.org"
target="_blank" moz-do-not-send="true">X3D
Graphics public mailing list</a><br>
<b>Subject: </b>Re: [x3d-public] Mantis? No
SceneGraphStructureStatement AbstractNodeType
present in old X3D3 versions, X3DUOM</p>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">Hmm. I mean IS field in
fieldValue in X3DUOM. I guess X3DUOM updates are
postponed until X3D4 is done.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">John</p>
</div>
<div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">On Tue, Sep 7, 2021 at 12:28
PM John Carlson <<a
href="mailto:yottzumm@gmail.com"
target="_blank" moz-do-not-send="true">yottzumm@gmail.com</a>>
wrote:</p>
</div>
<blockquote style="border-style:none none none
solid;border-left-width:1pt;padding:0in 0in 0in
6pt;margin-left:4.8pt;margin-right:0in;border-left-color:rgb(204,204,204)">
<div>
<p class="MsoNormal">As previously reported, I
am fairly sure I added an IS node (which
creates a setIS method). I don’t think I
checked any of this in.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">I haven’t formally tested
JSON schema that I remember.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">John</p>
</div>
<div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">On Thu, Sep 2, 2021 at
9:38 PM John Carlson <<a
href="mailto:yottzumm@gmail.com"
target="_blank" moz-do-not-send="true">yottzumm@gmail.com</a>>
wrote:</p>
</div>
<blockquote style="border-style:none none none
solid;border-left-width:1pt;padding:0in 0in
0in
6pt;margin-left:4.8pt;margin-right:0in;border-left-color:rgb(204,204,204)">
<div>
<div>
<p class="MsoNormal">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.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">I’m wondering if my
changes locally affected
fieldValue.setIS as previously
reported? Or fieldValue.addChild(new
IS()) (IS is not a node)</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">I am thinking
someone should look at the type
hierarchy differences for statements.
If we go with X3D4, I will upgrade
various examples.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">I guess the other
solution is to provide different jars
for X3D3 versus X3D4.</p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">John</p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">On Sat, Aug 28,
2021 at 4:09 PM John Carlson <<a
href="mailto:yottzumm@gmail.com"
target="_blank"
moz-do-not-send="true">yottzumm@gmail.com</a>>
wrote:</p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
<p class="MsoNormal"
style="margin-right:0in;margin-bottom:12pt;margin-left:0.2in">
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"
target="_blank" moz-do-not-send="true">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="https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsourceforge.net%2F&data=04%7C01%7Cbrutzman%40nps.edu%7C14ad8d313ab94fccae3208d97226ccdc%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637666333260834274%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=mnVeGHLC%2B5v7Tn1eIq4CpKX%2BQIf3r%2FIuh31UL6grDss%3D&reserved=0"
target="_blank" moz-do-not-send="true">
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</p>
<p class="MsoNormal"> </p>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</body>
</html>