Re: [VCARDDAV] vCard XML

[Simon Perreault <[e-mail]>]

On 2010-03-05 16:34, Cyrus Daboo wrote:
>> Why is it important that this cannot be written?
>>
>> XML:<email><text>[e-mail]</text></email>
>
> A vCard parser seeing this will treat it as an opaque value. vCard
> parsers should not be expected to parse XML into vCard properties - that
> is the duty of the XML<->vCard converter.

Yes of course. A proper converter would do that. But I don't see why the 
example above should be illegal.

Here's a use case: Suppose you have to pass XML vCards through something 
that groks only text vCard. Your XML-speaking endpoints don't have or 
need a text vCard parser. So they can just wrap their vCard with:

BEGIN:VCARD
VERSION:4.0
XML:<XML vCard goes here>
END:VCARD

and it will come out on the other end unaltered.

> I don't think we should forbid the use of the same name in a property,
> parameter or value. Its seems somewhat unfair to say we can't have a
> DATE property or parameter now given that the only concern is how the
> XML schema is written (and its really just a stylistic feature of the
> schema - after all there is nothing that requires the relaxNG
> definitions to use names that match their vCard equivalents - the names
> of elements have to match of course).

Then it would be better to use different XML namespaces for the 
properties, parameters, and values instead of prefixing their tag names, 
don't you think?

Simon
-- 
NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server        --> http://numb.viagenie.ca
vCard 4.0               --> http://www.vcarddav.org