From: Carsten Dominik <carsten.dominik@gmail.com>
To: Adam Spiers <orgmode@adamspiers.org>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: .ics export violates RFC2445
Date: Thu, 15 May 2008 10:33:17 +0200 [thread overview]
Message-ID: <BE852836-964C-45EF-B3EC-75DF78275DF2@gmail.com> (raw)
In-Reply-To: <20080429171635.GB9068@atlantic.linksys.moosehall>
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.
>>> The RFC says:
>>>
>>> Conformance: The property MUST be specified in the "VEVENT",
>>> "VTODO", "VJOURNAL" or "VFREEBUSY" calendar components.
>>>
>>> -- http://tools.ietf.org/html/rfc2445#section-4.8.4.7
>>>
>>> The checksum would ensure that the UID field only changes when the
>>> event details check, which would be a first step towards helping
>>> synchronisation systems. I'm vaguely suspicious that the lack of
>>> UIDs
>>> currently confuses Google Calendar too.
>>
>> A UID may be good. However I think changing the UID when changing
>> the
>> entry would be bad, because this would exactly *disable*
>> synchronization.
>> To synchronize, you must know which entries to compare, and this is
>> only
>> possible with a persistent UID.
>
> Doh - you are right of course.
>
>> 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?
- Carsten
next prev parent reply other threads:[~2008-05-15 8:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 20:56 .ics export violates RFC2445 Adam Spiers
2007-11-10 10:07 ` Carsten Dominik
2008-04-29 14:12 ` Adam Spiers
2008-04-29 15:52 ` Carsten Dominik
2008-04-29 17:16 ` Adam Spiers
2008-05-15 8:33 ` Carsten Dominik [this message]
2008-05-27 21:55 ` Adam Spiers
2008-05-27 22:25 ` 1-way syncing with google calendar (was Re: .ics export violates RFC2445) Adam Spiers
2008-05-28 21:02 ` Cezar Halmagean
2008-05-28 21:57 ` Adam Spiers
2008-05-29 10:32 ` Tim O'Callaghan
2008-05-29 13:08 ` Re: 1-way syncing with google calendar David Smith
2008-05-30 20:55 ` Adam Spiers
2009-03-20 15:18 ` David Abrahams
2008-04-30 18:38 ` .ics export violates RFC2445 Leo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BE852836-964C-45EF-B3EC-75DF78275DF2@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=orgmode@adamspiers.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).