My Sprint sales exec was kind enough to get us tickets to Sprint’s private tent along the parade route for the Portland Rose Festival Grand Floral Parade. I got a lot of great photos, but ran out of storage space on my microdrive with a few floats still to go.

As of last night, every page on this website has been lovingly hand tweaked so as to maintain 100% compatibilty with the XHTML 1.0 Transitional spec. Every rogue & has become & and every empty tag has been terminated.

Just to be clear, I didn’t do this for fun. One of the stated goals of the Retrospect-GDS project is that all output will be XHTML 1.0 Transitional compliant. I figured that by cleaning up this site, I’d get a good feeling for what I’ll have to code differently in Retrospect-GDS.

Last week I managed to ride 60.07 miles in 4 rides, at an average speed of 11.221 miles per hour. My goal for this week is 66 miles (a 10% increase in mileage). The weather hasn’t exactly been cooperating with me, but I’ve already gone 32.23 miles in 2 rides, at an average speed of 12.892 miles per hour. A respectable average speed considering that I’m riding my old hybrid Trek 7500, and not a real road bike. Makes me work a bit harder for the speed.

The new date parsing class for Retrospect-GDS is almost complete. I’m still playing with the final output format, but I believe the the parsing logic is 99% complete for all the standard gedcom date formats. This week I’ll be doing extensive testing with various gedcom files to make sure that all the input format variations are accounted for. I also hope to uncover as many non-standard date formats as I can so that I can code for those as well.

Is anybody actually using the beta GedXML60 specifications? At first perusal it doesn’t seem much better than the Gedcom 5.5 spec. Maybe the benefits will become clear to me after I read the entire document… but I doubt it.