[Ietf-caldav] freebusy lookups in CalDav are too hard to consume?
lisa at osafoundation.org
Mon May 29 11:04:42 PDT 2006
Cyrus & Bernard & I have been talking about this a long time as a way
to transition to something even more XML friendly. I hadn't thought
it needed to be mentioned in this spec because so far there's only
one ACCEPT-able format.
On May 29, 2006, at 10:57 AM, Wilfredo Sánchez Vega wrote:
> This does bring up one issue.
> Perhaps we should provide guidance/encouragement in the CalDAV
> spec on the use of the Accept header. As far as I know, most web
> clients do not provide a useful Accept header, which is problematic
> when a server can render a calendar component resource in both
> iCalendar and (eg.) hCalendar forms.
> On May 26, 2006, at 3:13 PM, Jim Whitehead wrote:
>>> p.s. For the data format, my personal belief is that data models
>>> should be available in many formats. The hard work is actually
>>> producing and agreeing on the data model, mapping it to different
>>> representations is the easy bit. I would encourage the group to
>>> think about producing an xml representation for iCal. As well as
>>> being more consumable it has a standard approach for character
>>> encodings and allows the elements to be mixed with elements from
>>> other namespaces e.g. Location.
>> I agree with this. The difficulty is not with the parsing, but
>> with the representation of the data model. I would like to see a
>> migration path to XML over time, as the ICalendar format is a
>> historical anomaly, a data format that gathered sufficient
>> internal momentum to not immediately be converted to XML. XML is
>> clearly a better long-term representation strategy, as it offers
>> better extensibility, and there is more tool support for XML.
> Ietf-caldav mailing list -- Ietf-caldav at osafoundation.org
> See http://ietf.webdav.org/caldav/ for more CalDAV resources
More information about the Ietf-caldav