[Ietf-carddav] Carddav draft examples and XML elements

Vinubalaji Gopal <vinu@osafoundation.org> Tue, 15 August 2006 19:05 UTC

Return-Path: <vinu@osafoundation.org>
X-Original-To: ietf-carddav@osafoundation.org
Delivered-To: ietf-carddav@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org []) by leilani.osafoundation.org (Postfix) with ESMTP id E8CEC7F73C for <ietf-carddav@osafoundation.org>; Tue, 15 Aug 2006 12:05:03 -0700 (PDT)
Received: from [] (adsl-75-5-124-98.dsl.pltn13.sbcglobal.net []) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id BCEF214225C for <ietf-carddav@osafoundation.org>; Tue, 15 Aug 2006 12:05:03 -0700 (PDT)
From: Vinubalaji Gopal <vinu@osafoundation.org>
To: ietf-carddav@osafoundation.org
Content-Type: text/plain
Organization: OSA Foundation
Date: Tue, 15 Aug 2006 12:04:53 -0700
Message-Id: <1155668693.6405.64.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.1
Content-Transfer-Encoding: 7bit
Subject: [Ietf-carddav] Carddav draft examples and XML elements
X-BeenThere: ietf-carddav@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: vinu@osafoundation.org
List-Id: ietf-carddav.osafoundation.org
List-Unsubscribe: <http://lists.osafoundation.org/cgi-bin/mailman/listinfo/ietf-carddav>, <mailto:ietf-carddav-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-carddav>
List-Post: <mailto:ietf-carddav@osafoundation.org>
List-Help: <mailto:ietf-carddav-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/cgi-bin/mailman/listinfo/ietf-carddav>, <mailto:ietf-carddav-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Aug 2006 19:05:04 -0000

   I am responsible for implementing carddav in Cosmo and had a few corrections on the carddav draft:

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 in the draft does not
use the right XML definitions:


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:prop-filter name="NICKNAME">
         <C:text-match caseless="yes"

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

         <C:prop-filter name="NICKNAME">
           <C:text-match caseless="yes"