Re: Canonical Representation for decimal

Guy:
My apologies for taking so long to respond.

Here's how I read the spec.
CANONICAL REPRESENTATION FOR DECIMAL
0.1234 is not allowed due to the leading zero.  This
value must be encoded as .1234

CANONICAL RERESENTATION FOR FLOAT/DOUBLE
0.1234E0 is not allowed as there must be one non-zero
digit before the decimal.  This value must be represented as
1.234E-1

All the best, Ashok


"Guy Gurden" <gurden_guy@jpmorgan.com>@w3.org on 11/29/2000 12:16:10 PM

Sent by:  www-xml-schema-comments-request@w3.org


To:   www-xml-schema-comments@w3.org
cc:
Subject:  Canonical Representation for decimal



I would like to get clarification on whether the canonical representation
for
the decimal dataype (
http://www.w3.org/TR/2000/CR-xmlschema-2-20001024/#decimal)
allows the single zero to the left of the decimal place in decimal numbers
such
as 0.12345 or is the zero regarded as a 'leading zero' and therefore
prohibited.

I would assume that the same convention will hold for the mantissa part of
a
float value since the mantissa representation follows the lexical rules for
decimal.  Currently the canonical definition for float is a little cryptic
on
the matter.  It states 'The exponent must be indicated by "E" and number
representations must be normalized such that for non-zero numbers there is
a
single non-zero digit to the left of the decimal point.'

We use a subset of the Schema built-in datatypes in FpML and are currently
deciding whether we should additionally constrain our lexical
representations to
follow the Schema canonical representations.

Thanks

Guy Gurden
J.P. Morgan (FpML.org)



This communication is for informational purposes only.  It is not intended
as
an offer or solicitation for the purchase or sale of any financial
instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made
herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.

Received on Friday, 8 December 2000 14:14:17 UTC