<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;}
.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,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I just tried the validator on flowers2.x3d, and got the following:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'><Script DEF='OrbitScript'> <field name='g' accessType='outputOnly'/> cannot define function g() unless accessType is inputOnly or inputOutput[/X3D/Scene/Group/ProtoDeclare/ProtoBody/Group/Script/field[6], error] <ProtoInstance name='orbit' DEF=''> <fieldValue name='translation' value='-8 0 0'/> with defined type='SFVec3f' accessType='inputOutput' has default value and is optional [/X3D/Scene/Group/ProtoInstance[1]/fieldValue[1], hint] <ProtoInstance name='orbit' DEF=''> <fieldValue name='diffuseColor' value='1 0.5 0'/> with defined type='SFColor' accessType='inputOutput' has default value and is optional [/X3D/Scene/Group/ProtoInstance[1]/fieldValue[2], hint] <ProtoInstance name='orbit' DEF=''> <fieldValue name='specularColor' value='1 0.5 0'/> with defined type='SFColor' accessType='inputOutput' has default value and is optional [/X3D/Scene/Group/ProtoInstance[1]/fieldValue[3], hint] <ProtoInstance name='orbit' DEF=''> <fieldValue name='transparency' value='0.75'/> with defined type='SFFloat' accessType='inputOutput' has default value and is optional [/X3D/Scene/Group/ProtoInstance[1]/fieldValue[4], hint] </span><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:red;background:#EEEEEE'>Error(s) detected during this validation test. X3D Schematron check: <b>fail</b></span><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'>. Good practice is to fix errors and warnings wherever possible, and consider silencing harmless informational messages, so that important indicators remain noticeable.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'>The error that appears seems strange. g is an output variable from my script. I could make it inputOutput, but that’s confusing.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'>Flowers2.x3d and Flowers2.json are attached.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'>The validation error shown is on flowers.json, so I’m suspecting some problem in the ProtoExpander for X3DOM. No validation error shows on index.html for flowers.json with proto expansion on. Hmm. Hmm. Prototypes.html uses the dev distribution version of x3dom while index.html uses my version. The proto expanders are somewhat different between the two. Hmm. Hmm.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'>Flowers.x3d and flowers.json are attached.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'>Guess I’ll have to sleep on it or something.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'>I am feeling the main problem may be with coordIndex in flowers2.x3d, since it doesn’t display with X_ITE in index.html<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'>I totally agree that the coordIndex problem is mine.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Times New Roman",serif;color:black;background:#EEEEEE'>John<o:p></o:p></span></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:brutzman@nps.edu">Brutzman, Donald (Don) (CIV)</a><br><b>Sent: </b>Sunday, September 22, 2019 5:57 PM<br><b>To: </b><a href="mailto:yottzumm@gmail.com">John Carlson</a>; <a href="mailto:holger.seelig@googlemail.com">Holger Seelig</a><br><b>Cc: </b><a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a><br><b>Subject: </b>Re: [x3d-public] (My sincerest apologies!) debugging X3DJSONLD withlatest X_ITE</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>(First: original posts were extremely large... please use links for big things like that next time.)</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John, here are several suggestions.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Have you tried X3D Validator on XML form of your model yet?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> X3D Validator</p><p class=MsoNormal> https://savage.nps.edu/X3dValidator</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>X3D Tooltips have lots of information too.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> X3D Tooltips: IndexedFaceSet</p><p class=MsoNormal> https://www.web3d.org/x3d/tooltips/X3dTooltips.html#IndexedFaceSet</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>X3DJSAIL can help with conversion if needed (though still needs .json import), also has internal validation complementing X3D Validator:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> X3D Java Scene Access Interface Library (X3DJSAIL)</p><p class=MsoNormal> https://www.web3d.org/specifications/java/X3DJSAIL.html</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>IFS is perhaps the most common and long-running node so need for a specification change is quite unlikely.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>"Divide and conquer" is a good way to debug issues. Suggest you work on individual pages before smashups. It is also popping up an error console, but the text is not copyable, so screenshot attached.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>You can find a few thousand examples using X_ITE in the X3D Example Archives, if you think the conversion patterns can be improved then am happy to apply changes.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> X3D Resources, Examples: Scene Archives for X3D</p><p class=MsoNormal> https://www.web3d.org/x3d/content/examples/X3dResources.html#Examples</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> https://www.web3d.org/x3d/content/examples/HelloWorldX_ITE.html</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Echoing: good luck.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On 9/22/2019 11:33 AM, John Carlson wrote:</p><p class=MsoNormal>> I have recently added</p><p class=MsoNormal>> </p><p class=MsoNormal>> "component": [</p><p class=MsoNormal>> </p><p class=MsoNormal>> {</p><p class=MsoNormal>> </p><p class=MsoNormal>> "@name":"Scripting",</p><p class=MsoNormal>> </p><p class=MsoNormal>> "@level":1</p><p class=MsoNormal>> </p><p class=MsoNormal>> }</p><p class=MsoNormal>> </p><p class=MsoNormal>> ],</p><p class=MsoNormal>> </p><p class=MsoNormal>> To the head of my JSON files.</p><p class=MsoNormal>> </p><p class=MsoNormal>> </p><p class=MsoNormal>> I still get the following error.</p><p class=MsoNormal>> </p><p class=MsoNormal>> Please assist me if possible.</p><p class=MsoNormal>> </p><p class=MsoNormal>> I have had difficulty with PROFILE Full in the past with some browsers, so I am reluctant to add that.</p><p class=MsoNormal>> </p><p class=MsoNormal>> It should not throw an error with the correct component?</p><p class=MsoNormal>> </p><p class=MsoNormal>> 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?</p><p class=MsoNormal>> </p><p class=MsoNormal>> Perhaps I should issue a standards change request?</p><p class=MsoNormal>> </p><p class=MsoNormal>> Thanks!</p><p class=MsoNormal>> </p><p class=MsoNormal>> John</p><p class=MsoNormal>> </p><p class=MsoNormal>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10</p><p class=MsoNormal>> </p><p class=MsoNormal>> *From: *Holger Seelig <mailto:holger.seelig@googlemail.com></p><p class=MsoNormal>> *Sent: *Sunday, September 22, 2019 1:32 AM</p><p class=MsoNormal>> *To: *John Carlson <mailto:yottzumm@gmail.com>; X3D Graphics public mailing list <mailto:x3d-public@web3d.org></p><p class=MsoNormal>> *Subject: *Re: My sincerest apologies!</p><p class=MsoNormal>> </p><p class=MsoNormal>> Hey John,</p><p class=MsoNormal>> </p><p class=MsoNormal>> If you get errors like this:</p><p class=MsoNormal>> </p><p class=MsoNormal>> x_ite.min.js:19 XML Parser Error: Unkown node type 'Script'.</p><p class=MsoNormal>> </p><p class=MsoNormal>> then you have insufficient component/profile statement.</p><p class=MsoNormal>> </p><p class=MsoNormal>> add 'COMPONENT Scripting:1'</p><p class=MsoNormal>> </p><p class=MsoNormal>> or for convenience</p><p class=MsoNormal>> </p><p class=MsoNormal>> add 'PROFILE Full'</p><p class=MsoNormal>> </p><p class=MsoNormal>> to your X3D file.</p><p class=MsoNormal>> </p><p class=MsoNormal>> </p><p class=MsoNormal>> _______________________________________________</p><p class=MsoNormal>> x3d-public mailing list</p><p class=MsoNormal>> x3d-public@web3d.org</p><p class=MsoNormal>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org</p><p class=MsoNormal>> </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>all the best, Don</p><p class=MsoNormal>-- </p><p class=MsoNormal>Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu</p><p class=MsoNormal>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149</p><p class=MsoNormal>X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>