[iaufwg] IAUFWG review of the new draft FITS Standard

[William Pence]

Arnold,

Are you suggesting that we define a new binary table TFORMn data code 
(e.g., 'T') for ISO 8601 date strings?  In this case, I presume the 
repeat count value (as in TFORM1 = '19T') would give the width of the 
single date value, in bytes, and would not mean that the column contains 
a vector of 19 ISO data values.

If this is what is being proposed, then it sounds to me like a major 
change to FITS that should be discussed as a separate proposal, rather 
than including it as part of the current exercise to simply update and 
clarify the wording of the FITS Standard.

Bill

Arnold Rots wrote:
> I meant as a datatype, allowed in tables (rather than faking it as a string).
> And, yes, ISO 8601 as restricted by the Y2K agreement.
> 
>   - Arnold
> 
> Steve Allen wrote:
>> On Mon 2008-03-17T21:24:17 +0100, Andreas Wicenec hath writ:
>>> Just saw your latest e-mail: Since we do have this Y2K agreement (I
>>> forgot about this),
>>> why shouldn't we put it into the standard?
>> The reference to ISO is is implicit in the requirements of 4.4.2.1,
>> but only explicit in the body of ref 10.
>>

-- 
____________________________________________________________________
Dr. William Pence                       William.Pence at nasa.gov
NASA/GSFC Code 662       HEASARC        +1-301-286-4599 (voice)
Greenbelt MD 20771                      +1-301-286-1684 (fax)