Re: String representations of numeric values

From: Mark Taylor <m.b.taylor-at-bristol.ac.uk>
Date: Fri, 21 Apr 2006 16:10:06 +0100 (BST)


Since I haven't posted anything for a couple of hours at least :-) here are responses to a couple of Roy's minor points:

On Thu, 20 Apr 2006, Roy Williams wrote:

> We already have "width" and "precision", which are recommendations
> about representation, derived from the formatting strings like F12.5 or
> %12.5f depending on language.

these deal with the situation where you have a numeric value and you want to represent it as a string. I'm talking about conversions in the opposite direction.

> There is also the VALUES element, you could have <VALUES ID="hms"> to
> indicate it is sexagesimal.

I don't object to putting something in the VALUES element rather than FIELD if people think that is more appropriate, but it doesn't make any sense to use the VALUES ID attribute. Just from a syntactic point of view it's defined in the schema with a content type of xs:ID, which would mean you could only have one VALUES element with ID="hms" per document.

Mark

-- 
Mark Taylor   Astronomical Programmer   Physics, Bristol University, UK
m.b.taylor@bris.ac.uk +44-117-928-8776 http://www.star.bris.ac.uk/~mbt/
Received on 2006-04-21Z17:10:43