Re: [Ietf-caldav] i;octet collation requirement

I thought we explained this limitation in the spec itself, but I  
can't find that now.  If we missed it, that's an unintentional  
oversight -- we definitely did discuss the limitation.

Lisa

On Dec 16, 2006, at 1:19 PM, Cyrus Daboo wrote:

> Hi Julian,
>
> --On December 16, 2006 4:51:30 PM +0100 Julian Reschke  
> <julian.reschke@gmx.de> wrote:
>
>> In
>> <http://greenbytes.de/tech/webdav/draft-dusseault- 
>> caldav-15.html#rfc.sect
>> ion.7.5>, CalDAV requires:
>>
>> ++
>> CalDAV servers are REQUIRED to support the "i;ascii-casemap" and
>> "i;octet" collations as described in [I-D.newman-i18n-comparator],  
>> and
>> MAY support other collations.
>> ++
>>
>> As CalDAV is not defined in terms of octet sequences, but in terms of
>> Unicode characters, how is "i;octet" supposed to provide any  
>> meaningful
>> results?
>>
>> Did anybody implement that? How?
>
> The base collation specification only defines i;ascii-casemap and  
> i;octet. Work is ongoing to provide better "unicode" collations:
>
> i;basic - <http://www.ietf.org/internet-drafts/draft-gulbrandsen- 
> collation-basic-00.txt>
>
> i;unicode-casemap - <http://www.ietf.org/internet-drafts/draft- 
> crispin-collation-unicasemap-00.txt>
>
> Certainly text matching on user supplied calendar data in  
> properties such as SUMMARY and DESCRIPTION will require one of  
> these (I certainly intend to implement one or both of these).
>
> In the meantime i;ascii-casemap and i;octet can be used to match  
> "tokens" in iCalendar enumerated properties which are just plain  
> ascii.
>
> -- 
> Cyrus Daboo
>
> _______________________________________________
> Ietf-caldav mailing list -- Ietf-caldav@osafoundation.org
> See http://ietf.webdav.org/caldav/ for more CalDAV resources
> http://lists.osafoundation.org/mailman/listinfo/ietf-caldav