Re: .ics export violates RFC2445

[Adam Spiers <orgmode@adamspiers.org>]

On Thu, May 15, 2008 at 10:33:17AM +0200, Carsten Dominik wrote:
> On Apr 29, 2008, at 7:16 PM, Adam Spiers wrote:
> >>>Also, it would be great if a UID field could be generated for each
> >>>event, perhaps by checksumming the contents of the event in some  
> >>>way.

[snipped]

> >>I guess we could create one, but this UID would then have to be
> >>stored in the entry, as a property.  Exporting to ical again must
> >>then re- use the old uid each time.
> >>
> >>My org-id.el in the contrib directory allows already to create
> >>unique identifiers, and it would be easy enough to include the
> >>domain to make them truely unique, wordwide.
> >>
> >>However, right now I am hesitating to force a property drawer onto
> >>every entry that ever is exported to iCalendar.  But as an option,
> >>this might really be good and eventually allow true
> >>synchronization.
> >
> >I understand your hesitation - as an option that sounds perfect.
> 
> Please get the latest GIT version of Org.  Then set the variable
> 
> (setq org-icalendar-force-UID t)
> 
> and try to export to iCalendar.
> 
> Right now, I am only forcing and using the ID for VEVENT.  I am not  
> using it for VTODO, because I am not sure if it is allowed to have the  
> same UID for a VEVENT and a VTODO, if they originate from the same  
> entry in a database?  Do you or anyone else know what the rules are  
> for this?

Sorry it took me a while to test this - things have been crazy
recently.  From the release notes it looks like you already decided to
generate unique UIDs for each source, which is fantastic - sounds like
the safe thing to do, regardless of what the official spec
requirements are.

I'm happy to report that using UIDs fixes the issue I was seeing with
duplicate entries in korganizer:

  http://bugs.kde.org/show_bug.cgi?id=99649

I'm going to restart gcaldaemon shortly - if it works then orgmode can
boast unidirectional non-interactive syncing with google calendar! (as
opposed to repeatedly importing an .ics file manually, which is very
tedious).