From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_02E8_01C76A51.F48858A0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   No.  I'm not assuming everyone is on Outlook.  If you look at the =
iCal standard for exchanging appts you will see that it mandates that =
some timedate info that is interchanged must be in UTC, others must have =
a delta from UTC, and some special case for appts in local time no = matter
where people are.  This strictness with time and time zones is = for the
same reasons I described.

   I wouldn't be surprised if sidekick 98 had no concept of anything but =
local time.  Not very good for people that are mobile across timezones =
but it could be OK for simple use.

Rich

  "Gary Britt"  wrote
in message =
news:45ff0d46$1{at}w3.nls.net...
  OK, I understand your answer, I think.  You are assuming that everyone =
is on=20
  Outlook (appropriate given the thread title) and somebody sends out an =

  appointment to each of the people who then click on it to cause it to =
be=20
  scheduled into their local appointment book (or some similar scenario, =
do I=20
  have this right).  In that kind of situation translation of time zones =
would=20
  be necessary.

  I don't ever have to deal with this which was part of my confusion, =
because=20
  I don't use Outlook.  I use Sidekick 98 for calendaring and phone =
book.  So=20
  I would never send out such a meeting note or use one.  I send an =
email or=20
  or we do a telephone call.  We specifically agree on a time for a =
particular=20
  time zone, and everybody then has to enter the day and time for the =
meetings=20
  on their own in their own local time converting for time zone =
differences.

  Gary



  Rich wrote:
  >    This is not a shared calendar scenario.  This is a meeting with=20
  > multiple participants in multiple time zones.  Quite common with=20
  > teleconferencing.
  > =20
  >    As for the user interface for creating such a meeting, if you are =
the=20
  > organizer you normally would set the time as the local time in your =
time=20
  > zone.  This is automatically translated to local time for the=20
  > recipients.  You can set it in another time zone if you wish if that =

  > makes more sense to you.  Again, it gets translated to local time =
for=20
  > you and all recipients.  If any of the recipients moves between time =

  > zones, and changes the time zone of the computer, everything =
adjusts.
  > =20
  > Rich
  >=20
  >     "Gary Britt"      > wrote in message
  >     news:45feaff6$1{at}w3.nls.net...
  >     Except for a calendar shared across timezones.  It only makes =
sense to
  >     schedule things based upon local time.  At least to me.  If I'm
  >     going to be
  >     on a conference call at X time.  I enter the local time for me.  =
The
  >     parties
  >     should translate timezones when setting up the meeting and each
  >     participant
  >     is responsible for putting down the right time for them on their
  >     local calendar.
  >=20
  >     Someone mentioned shared calendars across timezones where there
  >     could be a
  >     problem, but for the life of me I can't imagine why somebody =
would
  >     want to
  >     share a calendar across timezones.  Everybody keep there own
  >     calendar and is
  >     responsible for their own calendar seems to make the most sense =
to
  >     me.  Its
  >     one thing to make the calendars viewable across =
timezones/offices
  >     but to
  >     make them actually shared seems a problem waiting to happen to =
me.
  >=20
  >     Gary
  >=20
  >     Rich wrote:
  >     >    You would be wrong to schedule an 9:00 AM appt in CA as =
9:00 AM
  >     EST.=20
  >     >  You schedule it for 9:00 AM PST or 12:00 PM EST, the actual =
time
  >     of the
  >     >  meeting.  I do the former because it is clearer for me.  =
Maybe it is
  >     >  easier for you to think about a teleconference between you =
and
  >     someone
  >     >  in CA where what is at 9:00 AM for some participants is at =
12:00
  >     PM for
  >     >  you and others.
  >     >=20
  >     >  Rich
  >     >=20
  >     >
  >     >     "Gary Britt"      
  >     >     > wrote in =
message
  >     >     news:45fe7d3b{at}w3.nls.net...
  >     >     This doesn't make sense to me.  If I schedule a meeting in
  >     >     California for
  >     >     tomorrow at 9:00 AM, expecting to fly there from the East =
Coast
  >     >     today, I
  >     >     enter it on my calendar for 9:00 AM.  When I arrive in =
California
  >     >     and pull
  >     >     up my calendar I expect it to still say 9:00 AM.  Further, =
when I
  >     >     schedule
  >     >     it for 9:00 AM while on east coast local time, I don't =
expect to
  >     >     enter it as
  >     >     12:00 PM EST so it will show up on the calendar in =
California for
  >     >     9:00 AM.
  >     >
  >     >     All appointments are scheduled for local time without =
regard to
  >     >     timezones.
  >     >
  >     >     Gary
  >     >
  >     >     Geo. wrote:
  >     >     >  "Gregg N"      
  >     >     > wrote in message
  >     >     >  news:45fd6769{at}w3.nls.net...
  >     >     >
  >     >     > > What is the reason for storing the time as
UTC instead =
of
  >     as local
  >     >     > > time, given that local time is what is being =
scheduled?
  >     >     >
  >     >     >  Global corporations, I may travel to another office and =
it would
  >     >     need to
  >     >     >  remind me at the correct time when I'm there.
  >     >     >
  >     >     >  Geo.
------=_NextPart_000_02E8_01C76A51.F48858A0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








  
No.  I'm not assuming =
everyone is=20
on Outlook.  If you look at the iCal standard for exchanging appts
= you will=20
see that it mandates that some timedate info that is interchanged must = be in=20
UTC, others must have a delta from UTC, and some special case for appts = in local=20
time no matter where people are.  This strictness with time and =
time zones=20
is for the same reasons I described.
 
   I
wouldn't be surprised if =
sidekick 98=20
had no concept of anything but local time.  Not very good for =
people that=20
are mobile across timezones but it could be OK for simple =
use.
 
Rich
 

  "Gary Britt" <GaryNOSPAMBritt{at}genera=">mailto:GaryNOSPAMBritt{at}generalcogster.com">GaryNOSPAMBritt{at}genera=
lcogster.com>=20
  wrote in message news:45ff0d46$1{at}w3.nls.net...OK, I=20
  understand your answer, I think.  You are assuming that everyone =
is on=20
  Outlook (appropriate given the thread title) and somebody sends =
out an=20
  appointment to each of the people who then click on it to cause it =
to be=20
  scheduled into their local appointment book (or some similar =
scenario, do=20
  I have this right).  In that kind of situation translation of =
time=20
  zones would be necessary.I don't ever have
to deal with =
this which=20
  was part of my confusion, because I don't use Outlook.  I use =

  Sidekick 98 for calendaring and phone book.  So I would never =
send=20
  out such a meeting note or use one.  I send an email or or we =
do a=20
  telephone call.  We specifically agree on a time for a particular =

  time zone, and everybody then has to enter the day and time for =
the=20
  meetings on their own in their own local time converting for time =
zone=20
  differences.GaryRich =
wrote:>   =20
  This is not a shared calendar scenario.  This is a meeting with =
>=20
  multiple participants in multiple time zones.  Quite common with =
>=20
  teleconferencing.> 
>    As for the =
user=20
  interface for creating such a meeting, if you are the > =
organizer you=20
  normally would set the time as the local time in your time >=20
  zone.  This is automatically translated to local time for the =
>=20
  recipients.  You can set it in another time zone if you wish if =
that=20
  > makes more sense to you.  Again, it gets
translated to =
local=20
  time for > you and all recipients.  If any of the =
recipients moves=20
  between time > zones, and changes the time zone of the =
computer,=20
  everything adjusts.>  >
Rich>=20
  >     "Gary
Britt" <GaryNOSPAMBritt{at}genera=">mailto:GaryNOSPAMBritt{at}generalcogster.com">GaryNOSPAMBritt{at}genera=
lcogster.com>    =20
  <mailto:GaryNOSPAMBritt=">mailto:GaryNOSPAMBritt{at}generalcogster.com">mailto:GaryNOSPAMBritt=
{at}generalcogster.com>>=20
  wrote in message>     news:45feaff6$1{at}w3.nls.net...=
>    =20
  Except for a calendar shared across timezones.  It only makes =
sense=20
  to>     schedule
things based upon local=20
  time.  At least to me.  If =
I'm>     going=20
  to be>     on a
conference call at X =
time.  I=20
  enter the local time for me. 
The>     =

  parties>     should
translate timezones =
when=20
  setting up the meeting and
each>    =20
  participant>     is
responsible for putting =
down=20
  the right time for them on
their>     local =

  calendar.>
>     Someone
mentioned =
shared=20
  calendars across timezones where
there>     =
could=20
  be a>     problem,
but for the life of me I =
can't=20
  imagine why somebody
would>     want=20
  to>     share a
calendar across =
timezones. =20
  Everybody keep there
own>     calendar
and=20
  is>     responsible
for their own calendar =
seems to=20
  make the most sense
to>    
me. =20
  Its>     one thing
to make the calendars =
viewable=20
  across
timezones/offices>    
but=20
  to>     make them
actually shared seems a =
problem=20
  waiting to happen to me.>
>     =
Gary>=20
  >     Rich =
wrote:>    =20
  >    You would be wrong to schedule an
9:00 AM appt =
in CA as=20
  9:00 AM>     EST. =
>    =20
  >  You schedule it for 9:00 AM PST or 12:00 PM EST, the actual =

  time>     of =
the>    =20
  >  meeting.  I do the former because it is clearer for =
me. =20
  Maybe it is>    
>  easier for you =
to think=20
  about a teleconference between you
and>     =

  someone>    
>  in CA where what is =
at 9:00=20
  AM for some participants is at
12:00>     =
PM=20
  for>    
>  you and=20
  others.>     > =
>    =20
  > 
Rich>     >=20
  >    
>>    =20
  >     "Gary Britt"
<GaryNOSPAMBritt{at}genera=">mailto:GaryNOSPAMBritt{at}generalcogster.com">GaryNOSPAMBritt{at}genera=
lcogster.com>    =20
  <mailto:GaryNOSPAMBritt=">mailto:GaryNOSPAMBritt{at}generalcogster.com">mailto:GaryNOSPAMBritt=
{at}generalcogster.com>>    =20
  >     <mailto:GaryNOSPAMBritt=">mailto:GaryNOSPAMBritt{at}generalcogster.com">mailto:GaryNOSPAMBritt=
{at}generalcogster.com>>=20
  wrote in message>     =
>    =20
  news:45fe7d3b{at}w3.nls.net...>=
    =20
  >     This doesn't make sense
to me.  If I =

  schedule a meeting in>    =20
  >     California =
for>    =20
  >     tomorrow at 9:00 AM,
expecting to fly =
there from=20
  the East Coast>     =
>    =20
  today, I>    
>     =
enter it=20
  on my calendar for 9:00 AM.  When I arrive in=20
  California>     =
>     and=20
  pull>    
>     up =
my=20
  calendar I expect it to still say 9:00 AM.  Further, when=20
  I>    
>    =20
  schedule>    
>     =
it for=20
  9:00 AM while on east coast local time, I don't expect=20
  to>    
>     enter =
it=20
  as>    
>     12:00 =
PM EST=20
  so it will show up on the calendar in California=20
  for>    
>     9:00=20
  AM.>     =
>>    =20
  >     All appointments are
scheduled for local =
time=20
  without regard to>     =
>    =20
  timezones.>    =20
  >>    
>    =20
  Gary>     =
>>    =20
  >     Geo. =
wrote:>    =20
  >     > 
"Gregg N" <invalid{at}invalid.invalid&g=">mailto:invalid{at}invalid.invalid">invalid{at}invalid.invalid&g=
t;    =20
  <mailto:invalid{at}invalid.invalidmailto:invalid{at}invalid.invalid">mailto:invalid{at}invalid.invalid
>>>    =20
  >     <mailto:invalid{at}invalid.invalidmailto:invalid{at}invalid.invalid">mailto:invalid{at}invalid.invalid
>>>=20
  wrote in message>     =
>    =20
  >  news:45fd6769{at}w3.nls.net...>=
    =20
  >    
>>    =20
  >     > > What
is the reason for storing =
the time=20
  as UTC instead of>     as=20
  local>    
>     =
> >=20
  time, given that local time is what is being=20
  scheduled?>     =
>    =20
  >>    
>     =
> =20
  Global corporations, I may travel to another office and it=20
  would>    
>     =
need=20
  to>    
>     =
> =20
  remind me at the correct time when I'm =
there.>    =20
  >    
>>    =20
  >     >  =
Geo.

------=_NextPart_000_02E8_01C76A51.F48858A0--

--- BBBS/NT v4.01 Flag-5