Chuck Norris from EVDB is talking about how to store detailed location information in calendaring objects.
iCalendar specifies just a single text field that contains location – that’s not specific enough for much event calendaring.
They are proposing an extension to iCalendar to handle more structured location data. The concept is that there is a location ID that is referred to in the Location field of an iCalendar file, then there is a Location block that has contains all the detailed data on that specific location.
There’s some discussion about why not to just embed Vcard into iCalendar – apparently there are some syntax differences that would make iCalendar parsers choke on vCard data. Another reason is that vCard is really oriented towards people, not location (though it contains some location data).
Technorati Tags: Calconnect, Calendaring