I've sent Neil a patch that handles export from events to vcal and ical -- that's the easy part. The hard part is importing ical or vcal files and creating event nodes from them. The big issue is the ical/vcal location field, which in those formats is unified, while in the event schema, it's broken into building, room, street address, etc.
It's never going to be possible to parse free-form location fields and reliably get all of the atomic data that the event wants. My best idea right now is to try to get the parts that will usually be in a guessable location or format -- eg, if there are two letters possibly following a comma, and they are a known state abbreviation, that's probably the state. My questions for the list -- does anybody have a better idea? And, if not (or I guess even if so), can everyone send me an example or two of something that might go in a vcal/ical location field, so I can have some test fodder? Thanks, JP
