Re: data expression of date information (yes)

At 11:44 PM 2002-12-19, John Cowan wrote:
>Al Gilman scripsit:
> > The resolution is that the place and local time is sufficent as a 
> policy for
> > how to rendezvous, and it is a rendezvous policy that is what goes in a
> > plan, *not* necessarily an _unambiguous_ *time* reference.
>True.  But as a surrogate for the place, the ADO time zone may well serve,
>because it is a spatial unit that has had the same time offset history
>since the epoch (1970-01-01); furthermore, it in no case crosses national

Yes.  The collection of ADO time zones fills a hole in my description
of "what works" by way of where+whenInLocalTime.  This is a rule that
tells you what sort of a 'where' reference will work.  In the form
where+whenInLocalTime, the 'where' part should be something that has
a unique associated ADO time zone.  'Boston' works, 'Tennessee' doesn't.


> > The offset
> > policy of the civil authority will be definitized in time to accomplish the
> > rendezvous transaction of both being at the agreed meeting point at the 
> same
> > time.
>"In my last lifetime,                           John Cowan
>I believed in reincarnation;          
>in this lifetime,                     
>I don't."  --Thiagi                   

Received on Friday, 20 December 2002 10:14:21 UTC