Re: [calsify] Timezone Service Protocol not quite complete

[Julian Cable <[e-mail]>]

I know. That is cool. I just hate standards that try to please too many people and offer so many options that no two implementations interoperate.

This proposed standard is a long way from that. Let's keep it small. If Microsoft or tz-list want to translate at the edge fine, but let's have a minimal set of choices on the wire.

-----Original Message-----
From: Cyrus Daboo [mailto:[e-mail]]
Sent: 07 November 2013 15:33
To: Julian Cable; IETF-Calsify
Subject: Re: [calsify] Timezone Service Protocol not quite complete

Hi Julian,

--On November 7, 2013 at 4:26:55 PM +0000 Julian Cable
<[e-mail]> wrote:

>> It is worth noting that there are several data formats in use right now:
>
> Personally, I'd love it if you supported exactly one abstract syntax, and
> ideally, exactly one concrete syntax.
>
> I'd rather parse JSON than rfc5545, but I'd rather have it your way than
> both our ways.

We do have jCal
(<https://datatracker.ietf.org/doc/draft-ietf-jcardcal-jcal/>) which we
will hopefully be finishing up work on now that jCard is done. I already
tweaked my timezone service implementation to allow clients to request and
receive jCal in addition to iCalendar formats.

--
Cyrus Daboo



-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------