Imported from previous forum
[ original email was from John Prewett - jprewett@lavatrading.com ]
Despite the title, this posting has nothing to do with any dispute between Ryan & I 
A while back, I posted about the format of the datatype Price (see General Q/A "The price of freedom" 4/25/2001). The FIX 4.2 with errata specification clarified the issue by including examples:
Note that float values may contain leading zeros (e.g. “00023.23” = “23.23”) and may contain or omit trailing zeros after the decimal point (e.g. “23.0” = “23.0000” = “23”).
Being currently involved in yet another debate concerning the Price field, I would like to see a further clarification to be considered for the upcoming FIX.4.4 specification:
Note that float values may contain leading zeros (e.g. “00023.23” = “23.23”) and may contain or omit trailing zeros after the decimal point (e.g. “23.0” = “23.0000” = “23” = "23.").
You will notice that the only change was to the very last example where the integer value 23 may also be represented as “23.” (note the trailing decimal point). I am not suggesting that this is a particularly friendly format, I don’t think it is. I just believe that FIX engines should accept it as a valid value in accordance with the wording “and may contain or omit trailing zeros after the decimal point”. Clearly “23.” is in accordance with this wording.
Conversely, if you don’t agree to this change because you think “23.” shouldn’t be considered to be a valid representation of the integer value 23 then the FIX.4.4 specification should be amended to explicitly state that.
Comments?
[ original email was from Jim Northey - jnorthey@lasalletech.com ]
Capture this text for the volume#1.
We should not encourage leading zeroes - just say they are tolerated.
> Despite the title, this posting has nothing to do with any dispute between Ryan & I
>
> A while back, I posted about the format of the datatype Price (see General Q/A “The price of freedom” 4/25/2001). The FIX 4.2 with errata specification clarified the issue by including examples:
> ---------------------
> Note that float values may contain leading zeros (e.g. “00023.23” = “23.23”) and may contain or omit trailing zeros after the decimal point (e.g. “23.0” = “23.0000” = “23”).
> ---------------------
>
> Being currently involved in yet another debate concerning the Price field, I would like to see a further clarification to be considered for the upcoming FIX.4.4 specification:
> ---------------------
> Note that float values may contain leading zeros (e.g. “00023.23” = “23.23”) and may contain or omit trailing zeros after the decimal point (e.g. “23.0” = “23.0000” = “23” = “23.”).
> ---------------------
> You will notice that the only change was to the very last example where the integer value 23 may also be represented as “23.” (note the trailing decimal point). I am not suggesting that this is a particularly friendly format, I don’t think it is. I just believe that FIX engines should accept it as a valid value in accordance with the wording “and may contain or omit trailing zeros after the decimal point”. Clearly “23.” is in accordance with this wording.
>
> Conversely, if you don’t agree to this change because you think “23.” shouldn’t be considered to be a valid representation of the integer value 23 then the FIX.4.4 specification should be amended to explicitly state that.
>
> Comments?
>
[ original email was from Kevin Houstoun - kevin.houstoun@ssmb.com ]
This issue has been assigned ID PC20030411_13 and will be discussed by the Global Technical Committee
> Capture this text for the volume#1.
>
> We should not encourage leading zeroes - just say they are tolerated.
>
> > Despite the title, this posting has nothing to do with any dispute between Ryan & I
> >
> > A while back, I posted about the format of the datatype Price (see General Q/A “The price of freedom” 4/25/2001). The FIX 4.2 with errata specification clarified the issue by including examples:
> > ---------------------
> > Note that float values may contain leading zeros (e.g. “00023.23” = “23.23”) and may contain or omit trailing zeros after the decimal point (e.g. “23.0” = “23.0000” = “23”).
> > ---------------------
> >
> > Being currently involved in yet another debate concerning the Price field, I would like to see a further clarification to be considered for the upcoming FIX.4.4 specification:
> > ---------------------
> > Note that float values may contain leading zeros (e.g. “00023.23” = “23.23”) and may contain or omit trailing zeros after the decimal point (e.g. “23.0” = “23.0000” = “23” = “23.”).
> > ---------------------
> > You will notice that the only change was to the very last example where the integer value 23 may also be represented as “23.” (note the trailing decimal point). I am not suggesting that this is a particularly friendly format, I don’t think it is. I just believe that FIX engines should accept it as a valid value in accordance with the wording “and may contain or omit trailing zeros after the decimal point”. Clearly “23.” is in accordance with this wording.
> >
> > Conversely, if you don’t agree to this change because you think “23.” shouldn’t be considered to be a valid representation of the integer value 23 then the FIX.4.4 specification should be amended to explicitly state that.
> >
> > Comments?
> >
>