[x3d-public] summary of remaining JSON parse errors

[Joe D Williams]

>> 1.e2 converted to 1.0e2

> In other words, it should be 1e2

shall be defined in standard:
IS 1 EQ 1. EQ 1.0?
n EQ n.0 for all n?
nem EQ n.0em AND nem EQ n.0em.0 ... for all nandm?

> concerned that will add one more digit of precision

could possibly be a problem with several real numbers depending upon 
digital representation

> faithful rendering of the number ...

> Thoughts?

For this individual special carefully considered case, if I understand 
it, then just write 1 with no decimal and no exponent, no matter the 
exponent.

For all others, I think preferred and hopefully carefully specified as 
the desired form is:
If no decimal then no problem or, if you place a decimal, then it 
needs to be followed with 0 or a number then no spaces then the e then 
a number. Overall, for the stuff before the e, if decimal then 
something; no decimal no problem.

Great work to characterize and specify these important details for all 
known cases.

Thanks,
Joe





----- Original Message ----- 
From: "John Carlson" <yottzumm at gmail.com>
To: "Don Brutzman" <brutzman at nps.edu>
Cc: "X3D Graphics public mailing list" <x3d-public at web3d.org>
Sent: Tuesday, March 01, 2016 9:28 AM
Subject: Re: [x3d-public] summary of remaining JSON parse errors


>I am a bit concerned that will add one more digit of precision, and 
>will not be a faithful rendering of the number.  Thoughts?
>
> In other words, it should be 1e2
>
> John
>> On Mar 1, 2016, at 10:06 AM, Don Brutzman <brutzman at nps.edu> wrote:
>>
>> Last night's build went OK.
>>
>> Found and amended code block (template output-reals) to insert 
>> missing 0 after decimal point, before scientific notation (e.g. 
>> 1.e2 converted to 1.0e2).
>>
>> Marked ScriptSyntaxExample.x3d meta information as a test scene.
>>
>> Many of your error cases in log file were test scenes or archived 
>> backups, not working scenes.  I'll keep scrutinizing and pursuing 
>> problems in the list.
>>
>>> On 2/26/2016 2:18 PM, John Carlson wrote:
>>>> Some number formatting issues (need digit after .)
>>>> Escaping issues
>>>> ContainerField naming or object attribute value braces missing.
>>>> ‘,’ value is missing.
>>>> Bad source documents (not X3D).
>>>> -metadata should be an array or a containerField.
>>
>> all the best, Don
>> -- 
>> Don Brutzman  Naval Postgraduate School, Code USW/Br 
>> brutzman at nps.edu
>> Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA 
>> +1.831.656.2149
>> X3D graphics, virtual worlds, navy robotics 
>> http://faculty.nps.edu/brutzman
>
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>