Re: [calsify] Working Group Last call for jscontact drafts

[Robert Stepanek <[e-mail]>]

Thanks for the review, Neil.

On Wed, Dec 7, 2022, at 5:54 AM, Neil Jenkins wrote:
> One thing: I would like a little more clarity on the expected usage of `fullName` and `fullAddress` – should we be saying these MUST NOT be present if you provide `name`/`address` components separately? It's unclear to me which I should display if both were present, as they could get out of sync.

I'd agree with MUST NOT if we would start from scratch with contacts data. But to make it simple to migrate existing vCards I think they SHOULD NOT be present (the vCard equivalent of `fullName` and `fullAddress` are the FN property and the LABEL parameter). I'll also highlight that implementations SHOULD prefer displaying the name rather than full name value, if both are present.

> The other stated purpose is for localisation: is the idea here that you would, for example, add a localised fullName property in the localizations patch, where there was none in the original (just components in the original)? Or must there be a fullName in the card's language too?

I think that this stated purpose is wrong and it was just an oversight that we didn't remove it before WGLC.  The localizations property only is meant to provide additional localizations of values that already are present in the original. This is suggested in the definition of the localizations property in the second paragraph, but we already came to realize that both the current examples and definitions are unclear on that. We'll update the RFC to hopefully make that clearer.