[Ietf-calsify] Re: xCal - time to submit?
Michiel van Leeuwen
mvl at exedo.nl
Mon Oct 17 09:44:49 PDT 2005
Helge Hess wrote:
> On 17. Okt 2005, at 18:08 Uhr, Michiel van Leeuwen wrote:
>> For example all the ical share websites, or other ways you can share a
>> calendar. You can't use multipart/alternative on a webserver.
> You accomplish the same thing using content negotiation in HTTP, that is
> "accept: text/xml" vs "accept: text/iCalendar" (or both, or both
> including content preference, say: "accept: text/xml, q=1.0;
> text/calendar, q=0.5;").
Ok, I didn't think of it. And the spec doesn't mention it (While it does
mention multipart/alternative.) It might be worth adding it.
But even then, for the best interop, any app need to be able to consume
both, and only produce the most common format, iCalendar. I still don't
see the advantage of xCal in the light of calsify.
More information about the Ietf-calsify