Re: [VCARDDAV] CardDAV + xCard in query response

On Mon, Jun 13, 2011 at 9:11 PM, Cyrus Daboo <cyrus@daboo.name> wrote:

> Hi Simon,
>
>
> --On June 13, 2011 2:49:45 PM -0400 Simon Perreault <
> simon.perreault@viagenie.ca> wrote:
>
>  http://tools.ietf.org/html/draft-ietf-vcarddav-carddav-10#section-10.4 ,
>>> the address-data corresponding to a REPORT response is defined as:
>>>
>>>       <!ELEMENT address-data (#PCDATA)>
>>>       <!-- PCDATA value: address data -->
>>>
>>> (and the same section contains two paragraph explaining how to deal with
>>> CDATA).
>>>
>>> If I understand this definition correctly, this more or less prevents
>>> the use of xCard as the returned format.
>>>
>>
>> Well, no matter what the schema says, the text itself prevents xCard
>> from being used. If I understand correctly, CardDAV specifies vCard 3,
>> mentions that v4 is compatible, and that's it. I guess we'll need a new
>> 1-page RFC to specify xCard inside CardDAV...
>>
>
> Actually the server can advertise support for xCard via the
> CARDDAV:supported-address-data property at which point it is in theory OK
> for the client to send that. Obviously the schema for the address-data
> element would need to be tweaked to allow "embedded" XML, and maybe we have
> a one page spec to do that (actually perhaps two pages as we should deal
> with this for CalDAV too).
>

So, in other words, it is too late to integrate this change into the CardDAV
spec itself (?...). I can give this one pager a try but is it OK to mix
CardDAV and CalDAV ?

The only other ambiguity in the spec that I faced while implementing CardDAV
+ xCard is the fact that the address-data requires a content-type and a
version number (e.g.

<C:address-data type='text/vcard' version='4.0'/>

) when xCard has no version number per say (versioning is provided through
XML namespaces).

Arnaud Quillaud

>
> --
> Cyrus Daboo
>
>
> _______________________________________________
> VCARDDAV mailing list
> VCARDDAV@ietf.org
> https://www.ietf.org/mailman/listinfo/vcarddav
>