<html xmlns:v="urn:schemas-microsoft-com:vml" 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 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Menlo;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>John,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>First, it can only be a number. Why shouldn’t it be a number? It is a legal JSON number. It gets correctly generated. It’s just large!<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Here it is in JSON: </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:maroon;background:white;mso-highlight:white'>@startTime"</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue;background:white;mso-highlight:white'>:</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:teal;background:white;mso-highlight:white'>999999999999999999999999999999999999</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:teal'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:teal'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>So, lets add one to it. What do we get? 1</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:teal;background:white;mso-highlight:white'>00000000000000000000000000000000000</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:teal'>0. </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Now, let’s add thousands separators to make it easier to count zeroes. It becomes 1,</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:teal;background:white;mso-highlight:white'>000,000,000,000,000,000,000,000,000,000,000,00</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:teal'>0. </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>That makes 36 zeroes, assuming I can count! Now, bearing in mind that this field is an SFTime field, which is specified as a double precision floating point number (see 19775-1 5.3.15 SFTime and MFTime, <a href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/fieldsDef.html#SFTimeAndMFTime">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/fieldsDef.html#SFTimeAndMFTime</a>)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>we could have written the number as </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:teal;background:white;mso-highlight:white'>1.0E36</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>. What is the range of a double precision number? Using IEEE 754 it is up to 1.0E308. So, our example is miniscule in comparison! Thus, it is perfectly legal from all points of view. It just looks huge because it is written out long hand.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>From a loader perspective it needs to know that the startTime field is an SFTime field and handle the input accordingly.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Roy<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> John Carlson [mailto:yottzumm@gmail.com] <br><b>Sent:</b> 03 April 2016 19:15<br><b>To:</b> Don Brutzman; Roy Walmsley<br><b>Cc:</b> X3D Graphics public mailing list<br><b>Subject:</b> @startTime too big a number<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:8.5pt;font-family:"Menlo","serif"'>I think @startTime in several places may be too big of an number, and is being treated like a string? Not sure. Here’s the JSON file:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.5pt;font-family:"Menlo","serif"'><br><br><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.5pt;font-family:"Menlo","serif"'>/<a href="http://www.web3d.org/x3d/content/examples/Basic/StudentProjects/IkeaBeadToy.json">www.web3d.org/x3d/content/examples//Basic/StudentProjects/IkeaBeadToy.json</a><o:p></o:p></span></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Perhaps allow it to be either a string or a number? Not sure. I guess there’s no Time type in JSON.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>What is <span style='font-size:9.5pt'>∞</span> translated to? Not that you can put it in the field.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>John<o:p></o:p></p></div></div></body></html>