Thanks for the idea!
I'm not sure if I understood you correctly, however. What I could imagine is a syntax like

{{davcalevent>id=calendars:start,uid=233}}

that will be rendered as a link with the event's title and, if you click on it, the same "edit event" popup opens that opens if you click an item in the calendar.

Is that what you mean? The link could be shown in the "edit event" popup whenever you edit an event. In the future, we could also come up with a toolbar picker, similar to the page link wizard, that shows calendar events instead.

This is going to disable the XHTML cache for the given page (not the instruction cache), as we need to fetch and render the event on the fly.

Thanks for looking into this.

My use case is this: my calendar items are meetings and I want to have links to the agenda or meeting notes.

For me it would be nice to have a free form data field (Desciption) where one can add links to. If that is not possible then maybe the option to add a few links to the item (as seperate fields) would also be nice.

If I understand well you propose to have for each item a link to a wiki page and there one can add other links et cetera. This will work as well but adds an extra 'layer'.

As for the technical consequences I am sorry but I have no idea.

OK, now I understood your request :) You're speaking of creating links WITHIN an event, not within a page TO an event.

There are actually several possibilities: I could allow wiki syntax in the event's description, then you could simply enter the usual wiki syntax to link to your meeting. However, clients which synchronize via CalDAV will only see the Wiki markup.

An alternative would be the URL field of the ICS specification. Then the URL would be a separate field where you could specify your link. Spec: http://www.kanzaki.com/docs/ical/url.html

You are right. wiki sytax would be useless on other clients. However the ICS url you refer to is just a link. I mean there is no label so you can see what it is where you will go to when you click on it (they could have done URL:"meeting notes":http://bladiebla). Or is that what they mean with 'xparam'?

An ordinary link in the description is also only usefull if the client renders it like a link. Mmm I thought this to be a simple wish....

Yeah, sometimes, when you look closer to "simple" wishes, they become complicated :(

Thunderbird/Lightning calls this feature "Attach Webpage...".
If it is a separate field, is then a further description necessary?

Of course, as a last resort, we can always use private parameters. They won't show up in synchronisation clients, though!

I just checked owncloud. The Calendar app does not have a link. Calendar+ has one link as a seperate field. So it appears one seperate link is considered 'enough'.

For my case it would link to a (wiki) page of a certain meeting. A normal link (no wiki id link) would be best to suit all clients.

I agree. I'll add a separate link field (first step, should be easy) and I'll also change the behaviour of the edit popup: When you click on an event, it will be displayed read-only, so that the URL is rendered. Only after clicking 'Edit', it will be read-write (if you have enough permission).

However, it's going to take some time as I'm a little busy with work.

Thanks again. I am looking foreward to it.

I just started looking into this: In order to support ThunderBird, I'll probably use the ATTACH property of the ICS spec. This one can be specified several times and it defaults to URI. Seems like a good fit.

Support for adding URL attachment was introduced in rDAVCAL40987d2c5f2a. Please test and report back!

Seems to work perfect. Thanks a lot!

Maybe the text in the Edit dialog should be someting else then 'Attached Webpages' and 'Add Attachment'. It is about links or URL's. But maybe I am too technical.

In dutch:

'Bijgevoegde Web Paginas' and 'Voeg Web Pagina toe'

or as I prefer

'Bijgevoegde Links' and 'Voeg Link toe'