updated toIcal.py w.r.t. timezone design for TAG ftf trip to Basel

I'm travelling to Switzerland in October for a TAG meeting,
and the W3C travel folks gave me 3 itineraries to evaluate.

I got all three itineraries converted to .ics format
and loaded into Apple iCal; I'm not sure it got
the timezones right.

I consider much of the data sensitive just now, but you
can see the makefile where I made .ics versions of
the itineraries...

  http://www.w3.org/2004/10dc-bsl/Makefile

Ah what the heck... I'll make the screenshot
world-readable:
  http://www.w3.org/2004/10dc-bsl/eval-3-cals.png

Generating the .ics versions of the itineraries involved
updating toIcal.py w.r.t the timezone design that uses timezones
as properties.

http://www.w3.org/2000/10/swap/pim/toIcal.py
Revision 2.21  2004/09/08 15:46:05

a new dateTime/timezone design, with datatypes
http://lists.w3.org/Archives/Public/www-rdf-calendar/2004Apr/0022.html

Hmm... re-reading that message, I see that
it talks about using timezones as datatypes.
I'm not actually doing that; rather, I'm using
them as http://esw.w3.org/topic/InterpretationProperties
They're analagous, but not quite the same thing.

Sorry this is all jumbled up... today's task was to
make travel arrangements, not to write code. I hope
to explain more later... perhaps to update
http://esw.w3.org/topic/RdfCalendarTimeZoneNotes

-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/

Received on Wednesday, 8 September 2004 17:14:22 UTC