Re: [VCARDDAV] XML extensions

[Simon Perreault <[e-mail]>]

Joe Hildebrand wrote:
> EXTENSIONS;ENCODING=b;TYPE=text/xml:base64(xml)
                                     ^^^^^^^^^^^^

Why is this needed? It would mean that when you decode the base64 (as
indicated by ENCODING=b), you end up with base64 data, which you decode
again, and then you have text/xml, right?

(I couldn't find a definition of what it actually means.)

> (on the bus, we said "X-TENSIONS", but that was overly-cute)

You have exceeded your cleverness quota for the day. Please report to
secretariat ASAP.

> <?xml version="1.0" encoding="UTF-8"?>
> <vcard xmlns="urn:ietf:params:xml:ns:vcard-4.0">
>   <fn><text>Simon Perreault</text></fn>
> ...
>   <extensions>
>     <my-extension xmlns='urn:example:foo'>
>     </my-extension>
>   </extensions>
> </vcard>

Why is the extensions element needed here? There can't be name clashes
anyway because each extension is in its own XML namespace.

> The PI for encoding is important, but (as always in XML) it's odd that
> really only the first two code points ("<?") are used to guess the encoding,
> then the guess is double-checked with the encoding declaration is reached.

Just use the charset MIME parameter in the TYPE property parameter:

EXTENSIONS;ENCODING=b;TYPE="text/xml;charset=UTF-8":...

> The extensibility language in vcardrev and vcardxml will need to be updated
> to ensure round-tripability.  XML extensions will not solve the problem of
> existing X- or VND- fields in the old format, and their mechanical
> translation into the XML format. 

Agreed.

+1

Simon
-- 
STUN/TURN server    --> http://numb.viagenie.ca
Interplanetary news --> http://reeves.viagenie.ca
vCard 4.0           --> http://www.vcarddav.org