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

["Javier Godoy" <[e-mail]>]

Hi Simon,

----- Original Message ----- 
From: "Simon Perreault" <[e-mail]>
To: <[e-mail]>
Sent: Tuesday, April 06, 2010 9:53 AM
Subject: [VCARDDAV] LANGUAGE parameter vs. cardinality and PIDs


> Dearest working group,
>
>Florian Zeitz uncovered a big problem related to the LANGUAGE parameter:
>
>
>It turns out that BIRTH is specified with cardinality (0,1) and so cannot 
>have a PID, but the above example should be allowed.
>
>So what do we do? I see two options:
>
>1. Replace the LANGUAGE parameter with a LANGUAGE property, making vCards 
>monolingual.
>

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)

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

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)

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


>2. Specify how the LANGUAGE parameter affects cardinality (i.e. cardinality 
>applies to same-language sets of property instances). Allow PID to apply to 
>all properties.
>
>Is the language tag very much used currently? Do we think it is important 
>that a vCard can be multilingual?
>
>I think a LANGUAGE property would have more chance of being used. And since 
>it simplifies things, and I like simplicity, I like #1 more at this point.



Best Regards,

Javier