[ietf-caldav] typo in expanded mode example ?
Bernard Desruisseaux
bernard.desruisseaux at oracle.com
Fri Nov 14 10:12:58 PST 2008
Thanks to Cyrus, our working copy of rfc4791bis is now accessible here:
http://caldav.calconnect.org/caldavfiles/
Here's a link to the issue you brought up:
http://caldav.calconnect.org/caldavfiles/files/draft-desruisseaux-rfc4791bis.changes.html#rfc.issue.example-missing-utc-designator
Cheers,
Bernard
Bernard Desruisseaux wrote:
> Hi Arnaud,
>
> Yes, this is a typo.
>
> Jari Urpalainen had actually reported it to me back in March 2007 along
> with other typos.
>
> I'll try to publish our working copy of rfc4791bis on the web...
>
> Thanks,
> Bernard
>
> Arnaud Quillaud wrote:
>> Hello, the expanded mode example at
>>
>> http://tools.ietf.org/html/rfc4791#section-7.8.3
>>
>> shows all DTSTART and RECURRENCE-ID without a final "Z".
>>
>> In the meantime, the definition of the expanded mode states that "
>>
>> Date and local
>> time with reference to time zone information MUST be converted
>> into date with UTC time.
>>
>> ".
>> (http://tools.ietf.org/html/rfc4791#section-9.6.5)
>>
>> So do we have a typo in the example ?
>>
>> Thanks,
>>
>> Arnaud Q
>> _______________________________________________
>> ietf-caldav mailing list -- ietf-caldav at osafoundation.org
>> See http://ietf.webdav.org/caldav/ for more CalDAV resources
>> http://lists.osafoundation.org/mailman/listinfo/ietf-caldav
>>
>
>
More information about the ietf-caldav
mailing list