<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I am posting to a different subject.</p>
<p>The reason to implement a new SAI in ECMAScript 6 would be to
take advantage of classes and modules in ES6.</p>
<p>How far it would diverge from standard SAI, IDK.</p>
<p>I do not think we should load ES6 modules with JavaScript
modules.</p>
<p>One reason stylesheets are useful is that you can make tiny
tweaks, and you can achieve a new syntax.</p>
<p>But I don't want to be a stylesheet programmer, unless we go with
something like i18n. Feasibility of this, IDK. That's why
people do research.</p>
<p>John<br>
</p>
<div class="moz-cite-prefix">On 10/31/21 20:45, Joseph D Williams
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:617f46f1.1c69fb81.1366b.4391SMTPIN_ADDED_MISSING@mx.google.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@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;}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;}div.WordSection1
{page:WordSection1;}ol
{margin-bottom:0in;}ul
{margin-bottom:0in;}</style>
<div class="WordSection1">
<p class="MsoNormal">Does anyone want to discuss SAI for
building a scenegraph from X3DJSON? What approaches are out
there?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Just wondering, or waking up, why would
there be a special SAI for use with json? All I thought I
needed was a way to reliably import/export nodes and
parameters ilnto a standard scenegraph using standard SAI
interfaces. <o:p></o:p></p>
<p class="MsoNormal">Sure, using external programming interfaces
to build a scene by authoring or importing nodes and
statements and structures is possible, but regardless the
scenegraph is built from nodes and statements that may be
emitted from and external and internal scripts activated when
the scene is initialized using the spec SAI. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">At this point I still think of the json as
a way to store some data and some organized way for import
into the x3d scenegraph using the spec interfaces for external
and external programming. Bite my lip, but why think of a
scenegraph built entirely for json? How can I say no way, too
verbose<span style="font-family:"Segoe UI
Emoji",sans-serif">😊</span>I don’t think there needs
to be a canonical form for a scene built from json, like for
x3d xml and x3d Classic. I think it is more appropriate to
think of the Json as imported into or from the scene and
integrated into the scenegraph to be accessible by SAI using
the existing SAI with the canonical user code in XML or
Classic (same interfaces for both).<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">Joe<o:p></o:p></p>
</div>
</blockquote>
</body>
</html>