<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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";
color:black;}
.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><pre>I have recently added</pre><pre><o:p> </o:p></pre><pre> "component": [</pre><pre> {</pre><pre> "@name":"Scripting",</pre><pre> "@level":1</pre><pre> }</pre><pre> ],</pre><pre><o:p> </o:p></pre><pre>To the head of my JSON files.</pre><pre><br>I still get the following error.</pre><pre><o:p> </o:p></pre><pre>Please assist me if possible.</pre><pre><o:p> </o:p></pre><pre>I have had difficulty with PROFILE Full in the past with some browsers, so I am reluctant to add that.</pre><pre><o:p> </o:p></pre><pre>It should not throw an error with the correct component?</pre><pre><o:p> </o:p></pre><pre>I have left the initialization error in place. I’ve upgraded the files on coderextreme.net to have a Scripting component, but not fixed the initialize error as previously mentioned. Would you recommend not initializing the coordIndex component?</pre><pre><o:p> </o:p></pre><pre>Perhaps I should issue a standards change request?</pre><pre><o:p> </o:p></pre><pre>Thanks!</pre><pre><o:p> </o:p></pre><pre>John</pre><p class=MsoNormal><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</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:holger.seelig@googlemail.com">Holger Seelig</a><br><b>Sent: </b>Sunday, September 22, 2019 1:32 AM<br><b>To: </b><a href="mailto:yottzumm@gmail.com">John Carlson</a>; <a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>Re: My sincerest apologies!</p></div><p class=MsoNormal><o:p> </o:p></p><p>Hey John,</p><p><o:p> </o:p></p><p>If you get errors like this:</p><p>x_ite.min.js:19 XML Parser Error: Unkown node type 'Script'.</p><p>then you have insufficient component/profile statement.</p><p>add 'COMPONENT Scripting:1'</p><p>or for convenience</p><p>add 'PROFILE Full'</p><p>to your X3D file.</p><p><o:p> </o:p></p></div></body></html>