<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:"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;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.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:852457303;
mso-list-type:hybrid;
mso-list-template-ids:1580495366 134807569 134807577 134807579 134807567 134807577 134807579 134807567 134807577 134807579;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>That’s all well and good, but probably requires you extend the DOM or provide a DOM -> flag (this has been written) map.</p><p class=MsoNormal>Currently the DOM contains the USE node as a separate object, I believe (at least in X3DJSONLD, not sure about others), so everything is fine, below the DOM, the scenegraph should take care not to duplicate attributes.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Your code below becomes:</p><p class=MsoNormal><o:p> </o:p></p><ol style='margin-top:0in' start=1 type=1><li class=MsoNormalCxSpMiddle style='margin-left:0in;mso-add-space:auto;line-height:105%;mso-list:l0 level1 lfo1'><span lang=EN-GB>Traverse the scene, stepping through each node, using depth first ordering<o:p></o:p></span></li><li class=MsoNormalCxSpMiddle style='margin-left:0in;mso-add-space:auto;line-height:105%;mso-list:l0 level1 lfo1'><span lang=EN-GB>For each node, depending on whether USE attribute is set:<o:p></o:p></span></li><ol style='margin-top:0in' start=1 type=a><li class=MsoNormalCxSpMiddle style='margin-left:0in;mso-add-space:auto;line-height:105%;mso-list:l0 level2 lfo1'><span lang=EN-GB>If not, write out this node in full<o:p></o:p></span></li><li class=MsoNormalCxSpMiddle style='margin-left:0in;mso-add-space:auto;line-height:105%;mso-list:l0 level2 lfo1'><span lang=EN-GB>If so, only write this node with a USE attribute.<o:p></o:p></span></li></ol></ol><p class=MsoNormalCxSpMiddle style='line-height:105%'><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormalCxSpMiddle style='line-height:105%'><span lang=EN-GB>Actually, we just write out all the attributes in DOM to Java or JavaScript, and thus X3DJSAIL catches the problem, I hope.<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If someone wants me to reuse DOM nodes in X3DJSONLD, let me know.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I use standard DOM -> XML serializers, and I’m not sure how they would handle it. Poorly, I would guess. We’d probably have to write custom serializers for DOM -> XML output. Which can be done! But why reinvent the wheel?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I say we leave it to the scenegraph, but if someone wants real DOM integration, we’ll have to go with rewriting the serializer if we want XML output.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Anyone want to write an XML serializer written in JavaScript for X3DJSONLD that’s pluggable with my other serializers, and is hardened to future DOM changes?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</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:roy.walmsley@ntlworld.com">Roy Walmsley</a><br><b>Sent: </b>Thursday, July 20, 2017 10:29 AM<br><b>To: </b><a href="mailto:yottzumm@gmail.com">'John Carlson'</a>; <a href="mailto:brutzman@nps.edu">'Don Brutzman'</a><br><b>Cc: </b><a href="mailto:x3d-public@web3d.org">'list'</a><br><b>Subject: </b>RE: setUSE in X3DJSAIL</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-GB>Don and John,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>If we are talking about the step of writing our a file, then this is a different question.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>We can use the SAI methods to query the scene in memory. Methods to actually write the scene are a function of the implementation, and not a formal part of the SAI. So, while an implementation may have a setUSE method as part of the writing out interfaces, it is not a formal SAI method. It would be appropriate to indicate, perhaps in comments, those methods that are provided for the convenience of code that outputs the scene to a specific encoding.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>For example, I could consider the following partial algorithm for writing out a file:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><ol style='margin-top:0in' start=3 type=1><li class=MsoNormalCxSpMiddle style='margin-left:0in;mso-add-space:auto;line-height:105%;mso-list:l0 level1 lfo1'><span lang=EN-GB>Traverse the scene, stepping through each node, using depth first ordering<o:p></o:p></span></li><li class=MsoNormalCxSpMiddle style='margin-left:0in;mso-add-space:auto;line-height:105%;mso-list:l0 level1 lfo1'><span lang=EN-GB>For each node:<o:p></o:p></span></li><ol style='margin-top:0in' start=1 type=a><li class=MsoNormalCxSpMiddle style='margin-left:0in;mso-add-space:auto;line-height:105%;mso-list:l0 level2 lfo1'><span lang=EN-GB>Check if this node has already been written<o:p></o:p></span></li><li class=MsoNormalCxSpMiddle style='margin-left:0in;mso-add-space:auto;line-height:105%;mso-list:l0 level2 lfo1'><span lang=EN-GB>If not, write out this node in full<o:p></o:p></span></li><li class=MsoNormalCxSpMiddle style='margin-left:0in;mso-add-space:auto;line-height:105%;mso-list:l0 level2 lfo1'><span lang=EN-GB>If so, only write this node with a USE atttrbute.<o:p></o:p></span></li></ol></ol><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Thus, this function would only write out the node type and the USE attribute for step 2)c. And there would be no “resetting of values” involved.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>All the best,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Roy<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> John Carlson [mailto:yottzumm@gmail.com] <br><b>Sent:</b> 20 July 2017 15:06<br><b>To:</b> Roy Walmsley <roy.walmsley@ntlworld.com>; 'Don Brutzman' <brutzman@nps.edu><br><b>Cc:</b> 'list' <x3d-public@web3d.org><br><b>Subject:</b> RE: setUSE in X3DJSAIL<o:p></o:p></p></div></div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal>Roy,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I imagine setUSE was chosen because it was either an attribute in XML or property @USE in JSON, and we were translating XML and JSON to Java, Nashorn JavaScript and Python. Please provide an equivalent conversion of an X3D XML file to C,C++, or C# which does not use setUSE and uses SAI as you suggest. If you can do it, we will copy you.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We would like to use chained methods with a minimum of extra variables (ideally, just one variable for whole scenegraph will do—not currently achieved). In addition, we would like to take advantage of type safety as much as possible. Please consider type safety when writing your code.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>There are DOM -> various languages examples you can find in X3DJSONLD/src/main/node. JavaScriptSerializer.js and JavaSerializer.js are good ones. You can use any language you want, but if you integrate with X3DJSONLD (json2all.js), it will be integrated into my test suite.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It is also possible that setUSE was required in the concrete classes (not SAI that I know of) and extracting setUSE up to the interface was a good idea. I think this can be solved by providing an intermediate interface.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From: </b><a href="mailto:roy.walmsley@ntlworld.com">Roy Walmsley</a><br><b>Sent: </b>Thursday, July 20, 2017 9:13 AM<br><b>To: </b><a href="mailto:brutzman@nps.edu">'Don Brutzman'</a><br><b>Cc: </b><a href="mailto:yottzumm@gmail.com">'John Carlson'</a>; <a href="mailto:x3d-public@web3d.org">'list'</a><br><b>Subject: </b>setUSE in X3DJSAIL<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-GB>Hi Don,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>I note that in X3DJSAIL you have a “setUSE” method defined in all node classes. I don’t see any point of having this method.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>My thinking is as follows. Please correct it as necessary.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>X3DJSAIL is meant to be an interface for an implementation of the Java Language binding – ISO/IEC 19777-2.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>The SAI 19775-2 has no service related to “USE”. So it does not appear in the Java language binding.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Consider that an instance of a node (say Material) has been loaded into memory and added into a scene. Then consider that further down in the scene it is desirable to implement a “USE”. What are the steps?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>The first would be to call the Java implementation of the SAI execution context service “getNode”, with the SAIString parameter set to the DEF name, and the SAIAction parameter set to DEFNode. In the standard ISO/IEC 19777-2 V3.0, clause 6.4.6 getNode the defined method is getNamedNode. What is your equivalent function in X3DJSAIL?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Having obtained a node reference for the DEF’d node, let’s assume you also have a node reference for the node that is to be the parent of the USE node, which I will assume for this example will be Appearance. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>You now need to obtain a reference for the “material” field of the Appearance node. We need to use the SAI service getField, defined in 6.6.4 getField in ISO/IEC 19775-2. The Java language binding lists this as getField in clause 6.6.4 of ISO/IEC 19777-2. What is your equivalent function in X3DJSAIL?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Now that we have the field reference, and the node reference to add, we can finally make a call to the SAI service setValue, defined in 6.7.6 setValue in ISO/IEC 19775-2. The Java language binding lists this as setValue in 6.7.6 of ISO/IEC 19777-2. What is your equivalent function in X3DJSAIL?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Final comments relate to garbage management. The implementation will probably want some way to remember that the same node reference has been used in multiple places. That is something internal to the implementation, and not anything for the interface.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>So, in conclusion, I don’t see a need for your setUSE method. And it is not in the SAI.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>All the best,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Roy<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>