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

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

Hi Simon,

> 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...

It is not the same problem, as I'm not talking about modifying the 
language-versioned property, but another different property that is intended 
to have the same value in every instance. For example, modifying EMAIL in:

BEGIN:VCARD
VERSION:4.0
FN:John Doe
EMAIL:: [e-mail]
BIRTH;LANGUAGE=de-DE:Köln
END:VCARD

BEGIN:VCARD
VERSION:4.0
FN:John Doe
EMAIL:: [e-mail]
BIRTH;LANGUAGE=en-US:Cologne
END:VCARD

Clearly it is not an issue if multiple instances of the same property in 
different languages are allowed:

BEGIN:VCARD
VERSION:4.0
FN:John Doe
EMAIL:: [e-mail]
BIRTH;LANGUAGE=de-DE:Köln
BIRTH;LANGUAGE=en-US:Cologne
END: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
>
> 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.)

What do you mean by "not repeating data"? Actually this approach asks for 
repeating data, as FN and EMAIL in my example above.

>> 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.

Yes and no. The value of RELATED would not be a URI identifying a single vCard 
instance (as I understand it is the intent of RELATED), but a *set* of 
instances (with the actual instance being decided by the negotiation 
mechanism). If it is allowed, it should be explicitly stated.


Best regards

Javier