Re: [VCARDDAV] LANGUAGE parameter vs. cardinality and PIDs

[Simon Perreault <[e-mail]>]

On 2010-04-07 07:05, Javier Godoy wrote:
> The problem with this approach is that versions in different languages
> may be out of sync (for instance, I modify EMAIL or TEL in the en-vCard,
> but I don't in the es-vCard or the fr-vCard)

Yes, but the same problem could also happen for multiple instances of 
the same property in different languages...

> If #1 is applied, we also need a new value for the RELATED type, such as
> "translation" or "self", for linking vCards instances describing the
> same individual in diferent languages.
>
> RELATED;TYPE=self:http://example.com/directory/en/jdoe.vcf
> RELATED;TYPE=self:http://example.com/directory/fr/jdoe.vcf
> RELATED;TYPE=self:http://example.com/directory/en/jdoe.vcf

I think that's a good idea.

> Note that clients won't know which vCard is in which language, before
> retrieving the instance (we might add a language-param for this case)

With CardDAV we can retrieve only the LANGUAGE property for all the 
related vCards in a single REPORT query with addressbook-multiget. So I 
don't see this as a problem. (And not repeating data could be considered 
desirable.)

> Content-negotiation MAY be used, if it is defined for the URI scheme. In
> that case we would have just one "self" vCard URI.
> RELATED;TYPE=self:http://example.com/directory/jdoe.vcf

Yes, but that's implementation-specific.

I would also envision using urn:uuid: URIs instead of http: URIs...

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