The schedule for this fall soccer season came out August 11th. I got the itinerary for the trip I'm about to take on July 26. But I just now got them synchronized with the family calendar.
The soccer league publishes the schedule in somewhat reasonable HTML; to get that into my sidekick, I have a Makefile that does these steps:
- Use tidy to make the markup well-formed.
- Use 100 lines of XSLT (soccer-schedfix.xsl) to add hCalendar markup.
- Use glean-hcal.xsl to get RDF calendar data.
- Use hipAgent.py to upload the calendar items via XMLRPC to the danger/t-mobile service, which magically updates the sidekick device.
But oops! The timezones come out wrong. Ugh... manually fix the times of 12 soccer games... better than manually keying in all the data... then sync with the family calendar. My usual calendar sync Makefile does the following:
- Use dangerSync.py to download the calendar and task data via XMLRPC.
- Use hipsrv.py to filter by category=family, convert from danger/sidekick/hiptop conventions to iCalendar standard conventions pour the records into a kid template to produce RDF Calendar (and hCalendar).
- Use toIcal.py to convert RDF Calendar to .ics format.
- Upload to family WebDAV server using curl.
Then check the results on my mac to make sure that when my wife refreshes her iCal subscriptions it will look right.
Oh no! The timezones are wrong again!
The sidekick has no visible support for timezones, but the start_time and end_time fields in the XMLRPC interface are in Z/UTC time, and there's a timezone field. However, after years with this device, I'm still mystified about how it works. The Makefiles approach is not conducive to tinkering at this level, so I worked on my REST interface, hipwsgi.py until it had crude support for editing records (using JSON syntax in a form field). What I discovered is that once you post an event record with a mixed up timezone, there's no way to fix it. When you use the device UI to change the start time, it looks OK, but the Z time via XMLRPC is then wrong.
So I deleted all the soccer game records, carefully factored the danger/iCalendar conversion code out of hipAgent.py into calitems.py for ease of testing, and goit it working for local Chicago-time events.
Then I went through the whole story again with my itinerary. Just replace tidy and soccer-schedfix.xsl with flightCal.py to get the itinerary from SABRE's text format to hCalendar:
- Upload itinerary to the sidekick.
- Manually fix the times.
- Sync with iCal. Bzzt. Off by several hours.
- Delete the flights from the sidekick.
- Work on calitems.py some more.
- Upload to the sidekick again. Ignore the sidekick display, which is right for the parts of the itinerary in Chicago, but wrong for the others.
- Sync with iCal. Win!
I suppose I'm resigned that the only way to get the XMLRPC POST/upload right (the stored Z times, at least, if not the display) is to know what timezone the device is set to when the POST occurs. Sigh.
A March 2005 review corroborates my findings:
The Sidekick and the sync software do not seem to be aware of time zones. That means that your PC and your Sidekick have to be configured for the same time zone when they synchronize, else your appointments will be all wrong.
hipwsgi.py is about my 5th iteration on this idea of a web server interface to my PDA data. It uses WSGI and JSON and Genshi, following Joe G's stuff. Previous itertions include:
- pdkb.pl - quick n dirty perl hack (started April 2001)
- hipAgent.py - screen scraping (Dec 2002)
- dangerSync.py - XMLRPC with a python shelf and hardcoded RDF/XML output (Feb 2004)
- hipsrv.py - conversion logic in python with kid templates and SPARQL-like filters over JSON-shaped data (March 2006)