[Cosmo-dev] Carddav draft XML elements

[Vinubalaji Gopal]

Hi
   This topic may be apt for carddav list, but I wanted to make sure I
am right before posting it there and I am not sure if that list is
active, since the last post was sometime in 2005.

A filter in CardDav is defined as (similar to the filter XML definition
in the caldav draft).
<!ELEMENT filter comp-filter>


But in Carddav there is no real component other than VCARD. The
"component" XML elements are kept for future use and for compatibility
with caldav. If my interpretation is right, the examples posted by the
author does not use the right XML definitions:


http://ietfreport.isoc.org/idref/draft-daboo-carddav/#page-19


REPORT /home/bernard/addressbook/ HTTP/1.1 
   Host: adbk.example.com
   Depth: 1
   Content-Type: text/xml; charset="utf-8"
   Content-Length: xxxx

   <?xml version="1.0" encoding="utf-8" ?>
...
     <C:filter>
       <C:prop-filter name="NICKNAME">
         <C:text-match caseless="yes"
                         match-type="equals">
         me
         </C:text-match>
       </C:prop-filter>
     </C:filter>
   </C:adbk-query>



This example should be modified to have <C:comp-filter> with an optional name="VCARD", meaning that 
the example should have been like:

     <C:filter>
       <C:comp-filter>
         <C:prop-filter name="NICKNAME">
           <C:text-match caseless="yes"
                           match-type="equals">
             me
           </C:text-match>
         </C:prop-filter>
       </C:comp-filter>
     </C:filter>
	

In cosmo, my present implementation is to follow this kind of behavior. 


--
Vinu