<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;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Could one layer DOM on top of X3DJSAIL like Andreas has done with Cobweb and what X3DOM does, so internally, DOM is checked for type safety and validated and all that good stuff?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If we had a common way of doing things that would be good. A common architecture. Then our skills would be more portable between X3D browsers.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>What about SAX? DOM trees get big, and if we had a SAX -> X3DJSAIL tree, that would be more efficient.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John<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:brutzman@nps.edu">Don Brutzman</a><br><b>Sent: </b>Thursday, July 20, 2017 4:32 PM<br><b>To: </b><a href="mailto:andreasplesch@gmail.com">Andreas Plesch</a>; <a href="mailto:yottzumm@gmail.com">John Carlson</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] setUSE in X3DJSAIL. Impact on X3DJSONLD.</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>There is some usage of DOM internally to the library, particularly when using Java reflection, but none of that is exposed to the programmer.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Conceivably we could add some form of DOM import and export for X3DJSAIL object trees.</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>