<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>Don wrote:</p><p class=MsoNormal>>Interesting to think that any program could produce .x3d .x3dv .wrl .json .java and maybe someday .js .c++ .python etc. Perhaps new worlds of interoperability are emerging, all sharing interactive X3D scenes as presentation layer to users.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We already have .json -> DOM -> .js .py and maybe you don’t realize it in my work yet. .py doesn’t run right now, but I think we are close, since it used to work.</p><p class=MsoNormal><br>Don, if *<b>we</b>* do a little research on how to integrate a Nashorn program into Java, perhaps we could bring my JavaScript https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/node/JavaScriptSerializer.js and Python https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/node/PythonSerializer.js serializers into X3DJSAIL proper. That is, if you’re open to the idea, and are not restricted to doing the stylesheet thing all the time. The goal would be to go from X3DJSAIL app -> Java XML -> XML or DOM -> JavaScript DOM -> .js .py. Then slowly replace them with stylesheets as you and others find the time.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Then I could work with Roy on a DOM -> .cpp serializer in JavaScript as well.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Alternatively, you could get on the stick and integrate X3dToJava.xslt with the now old X3dToES5.xslt so we start writing a new language independent stylesheet that we can target at Java, JavaScript, ECMAScript, Python, C++, C#, … with a parameter.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>My Action Needed has fallen by the wayside I see. That’s OK.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John</p></div></body></html>