<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:1921059109;
mso-list-type:hybrid;
mso-list-template-ids:194520620 -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><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>Why are X3D experts satisfied with text?<o:p></o:p></li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Not satisfied, just a basic ideal and I think a requirement that there exists a human-readable version that is complete and has a structure that contains critical data for a high-performance interactive scenegraph allowing realtime internal and external transactions using multiple media and interface styles. </p><p class=MsoNormal>This is why x3d uses a certain vocabulary and data structure that is extensible to include new functionality. <o:p></o:p></p><p class=MsoNormal>To validate something, to identify that you can share, then most basic is that you can literally read the stuff and at least try to understand whether it is worth trying to use it in your content. Also, you really want a convenient way to create and share what you have another way than a picture of the tool gui to save what you have for the next project. So, at some level, for some level of validation, I would say yes, we need a text form for anything in x3d. That is just being courteous and thoughtful to the community. <o:p></o:p></p><p class=MsoNormal>Thanks, <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>Friday, June 25, 2021 9:27 AM<br><b>To: </b><a href="mailto:brutzman@nps.edu">Don Brutzman</a><br><b>Cc: </b><a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>Re: [x3d-public] Wishlist: X3DUOM visualization</p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>I’m hoping for a better “XML” that’s actually feasible in a VR setup, Don. I think computing is moving away from the desktop/paper-like approach.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>That’s why I’m exploring 3D specification based on Java and ISO standard specification language. The first task is getting the X3D specifications into that language. Next we figure out how to visualize the specification in X3D. I’m aiming for explaining X3D concepts in 3D.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I don’t know if semantics or specification is better. Perhaps the best of both worlds?</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Even the guy behind the DynaBook said we’re stuck in this paper-like world we’ve created.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Why are X3D experts satisfied with text?</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>John</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><div><p class=MsoNormal>On Fri, Jun 25, 2021 at 9:34 AM Don Brutzman <<a href="mailto:brutzman@nps.edu">brutzman@nps.edu</a>> wrote:</p></div></div></div><p class=MsoNormal style='margin-left:4.8pt'>Hi John. Your mail identifies how the X3DUOM (an XML file matching X3D Architecture Specification) is implemented as Java classes.<br><br>Not clear what the goal of your visualization might be. Sofar we've made all of this information readily available to programmers in XML, Java and Python.<br><br>I'd suggest that the X3D Architecture Specification itself is the authoritative "visualization" of What It All Means.<br><br>There is also the Interface Hierarchy, a plain-text (ASCII art) tree version of all interfaces and nodes, originally produced by Joe Williams and faithfully updated by editors as we've progressed.<br><br>* X3D4 Architecture, Clause 4 Concepts, 4.4.2.3 Interface hierarchy<br> <a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/concepts.html#InterfaceHierarchy" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/concepts.html#InterfaceHierarchy</a><br><br><br>On 6/24/2021 10:37 AM, John Carlson wrote:<br>> I'm trying to achieve a 2D, 3D or 4D visualization of the X3DUOM.<br>> <br>> $ grep public.*get /c/x3d-code/www_web3d_org/x3d/stylesheets/java/src/org/web3d/x3d/util/x3duom/X3DUnifiedObjectModel.java<br>> public SimpleTypeEnumerations getSimpleTypeEnumerations() {<br>> public FieldTypes getFieldTypes() {<br>> public AbstractObjectTypes getAbstractObjectTypes() {<br>> public AbstractNodeTypes getAbstractNodeTypes() {<br>> public ConcreteNodes getConcreteNodes() {<br>> public Statements getStatements() {<br>> public String getVersion() {<br>> <br>> <br>> Wanted: Someone to take this class and create a visualization of an instantiation of the class. Use the X3DUnifiedObjectModel40.java to instantiate the 4.0 version of X3DUOM, then "marshall" out (with the get methods) the 4.0 version of the X3DUOM to MVC view code (possibly using an X3D encoding) and display.<br>> <br>> Right now, I'm thinking of 5-6 X3D superstores where you can shop for objects in each returned collection.<br>> <br>> Right now, I'm grepping/searching/editing the X3DUOM as a file. As I don't have XMLSpy, I could see an extension of X3D-Edit as an option. Can we use X3D-Edit 4 to edit the X3DUOM, not unlike how we can currently edit an X3D encoded file?<br>> <br>> What's the best way to browse the X3DUOM besides the specification?<br>> <br>> Gonna google 3D specification.<br>> <br>> Thanks!<br>> <br>> John<br>all the best, Don<br>-- <br>Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu" target="_blank">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">http://faculty.nps.edu/brutzman</a></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>