From: "Rich" 

This is a multi-part message in MIME format.

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

   This is not a shared calendar scenario.  This is a meeting with =
multiple participants in multiple time zones.  Quite common with = teleconferencing.

   As for the user interface for creating such a meeting, if you are the =
organizer you normally would set the time as the local time in your time =
zone.  This is automatically translated to local time for the = 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 = you and all
recipients.  If any of the recipients moves between time = zones, and
changes the time zone of the computer, everything adjusts.

Rich
  "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=20
  on a conference call at X time.  I enter the local time for me.  The =
parties=20
  should translate timezones when setting up the meeting and each =
participant=20
  is responsible for putting down the right time for them on their local =
calendar.

  Someone mentioned shared calendars across timezones where there could =
be a=20
  problem, but for the life of me I can't imagine why somebody would =
want to=20
  share a calendar across timezones.  Everybody keep there own calendar =
and is=20
  responsible for their own calendar seems to make the most sense to me. =
 Its=20
  one thing to make the calendars viewable across timezones/offices but =
to=20
  make them actually shared seems a problem waiting to happen to me.

  Gary

  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=20
  > 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=20
  > in CA where what is at 9:00 AM for some participants is at 12:00 PM =
for=20
  > you and others.
  > =20
  > Rich
  > =20
  >=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.
  >=20
  >     All appointments are scheduled for local time without regard to
  >     timezones.
  >=20
  >     Gary
  >=20
  >     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_02BE_01C76A18.DA9D74E0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   This is
not a shared =
calendar=20
scenario.  This is a meeting with multiple participants in
multiple = time=20
zones.  Quite common with teleconferencing.
 
   As for
the user interface =
for creating=20
such a meeting, if you are the organizer you normally would set the time = as the=20
local time in your time zone.  This is automatically translated to
= local=20
time for the recipients.  You can set it in another time zone if =
you wish=20
if that makes more sense to you.  Again, it gets translated to =
local time=20
for you and all recipients.  If any of the recipients moves
between = time=20
zones, and changes the time zone of the computer, everything=20
adjusts.
 
Rich

  "Gary Britt" <GaryNOSPAMBritt{at}genera=">mailto:GaryNOSPAMBritt{at}generalcogster.com">GaryNOSPAMBritt{at}genera=
lcogster.com>=20
  wrote in message news:45feaff6$1{at}w3.nls.net...Except=20
  for a calendar shared across timezones.  It only makes sense to=20
  schedule things based upon local time.  At least to
me.  =
If I'm=20
  going to be on a conference call at X time.  I enter the =
local time=20
  for me.  The parties should translate timezones when setting =
up the=20
  meeting and each participant is responsible for putting down the =
right=20
  time for them on their local calendar.Someone
mentioned shared =

  calendars across timezones where there could be a problem, but for =
the=20
  life of me I can't imagine why somebody would want to share a =
calendar=20
  across timezones.  Everybody keep there own calendar and is=20
  responsible for their own calendar seems to make the most sense to =

  me.  Its one thing to make the calendars viewable across=20
  timezones/offices but to make them actually shared seems a problem =
waiting=20
  to happen to me.GaryRich =
wrote:>    You=20
  would be wrong to schedule an 9:00 AM appt in CA as 9:00 AM EST.  =

  > You schedule it for 9:00 AM PST or 12:00 PM EST, the actual =
time of=20
  the > meeting.  I do the former because it is
clearer for=20
  me.  Maybe it is > easier for you to think about a =
teleconference=20
  between you and someone > in CA where what is at 9:00 AM for =
some=20
  participants is at 12:00 PM for > you and
others.>  =

  > Rich>  >
>     =
"Gary=20
  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:45fe7d3b{at}w3.nls.net...>=
    =20
  This doesn't make sense to me.  If I schedule a meeting=20
  in>     California=20
  for>     tomorrow at
9:00 AM, expecting to =
fly=20
  there from the East
Coast>     today,=20
  I>     enter it on
my calendar for 9:00 =
AM. =20
  When I arrive in
California>     and=20
  pull>     up my
calendar I expect it to =
still say=20
  9:00 AM.  Further, when
I>    =20
  schedule>     it for
9:00 AM while on east =
coast=20
  local time, I don't expect
to>     enter it =

  as>     12:00 PM EST
so it will show up on =
the=20
  calendar in California
for>     9:00 =
AM.>=20
  >     All
appointments are scheduled for =
local time=20
  without regard
to>    
timezones.>=20
  >     Gary> =
>    =20
  Geo. wrote:>    
>  "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
  wrote in
message>    
>  news:45fd6769{at}w3.nls.net...>=
    =20
  >>    
> > What is the reason for =
storing=20
  the time as UTC instead of as
local>     =
> >=20
  time, given that local time is what is being=20
  scheduled?>    =20
  >>    
>  Global corporations, I =
may=20
  travel to another office and it
would>     =
need=20
  to>    
>  remind me at the correct =
time=20
  when I'm there.>    =20
  >>    
>  =
Geo.

------=_NextPart_000_02BE_01C76A18.DA9D74E0--

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