Lists Home |
Date Index |
- From: "Michael Kay" <M.H.Kay@eng.icl.co.uk>
- To: <email@example.com>
- Date: Mon, 30 Nov 1998 18:47:58 -0000
>In the case of a date or float, I would argue that they are both compound
>types and should be represented as such.
The popular human representations of dates and floats are compound, but the
intrinsic values are not. They are both points in a one-dimensional space,
the first being discrete and the second pseudo-continuous.
It is possible to choose representations of float and date that require no
parsing to extract, process, or render (localize) the value. I think there
is some merit in choosing a canonical XML representation of dates and floats
that is meaningful to a good proportion of people on the planet, but it is
more important that it is canonical.
In practice I would always recommend ISO 8601 representation for dates. This
is better than using a Julian day number because it is more meaningful to
humans. The parsing of this is so trivial that using XML tagging would not
add value, either for the human reader or the machine recipient.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)