[calsify] Re: JSContact: supporting multiple names?

Phillip Hallam-Baker <phill@hallambaker.com> Sun, 27 April 2025 17:55 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: calsify@mail2.ietf.org
Delivered-To: calsify@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 33AC321C91EC for <calsify@mail2.ietf.org>; Sun, 27 Apr 2025 10:55:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: 0.006
X-Spam-Level:
X-Spam-Status: No, score=0.006 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LNXNF0Wm30hz for <calsify@mail2.ietf.org>; Sun, 27 Apr 2025 10:55:08 -0700 (PDT)
Received: from mail-qv1-f54.google.com (mail-qv1-f54.google.com [209.85.219.54]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 7B85121C91DF for <calsify@ietf.org>; Sun, 27 Apr 2025 10:55:08 -0700 (PDT)
Received: by mail-qv1-f54.google.com with SMTP id 6a1803df08f44-6e8f05acc13so59697836d6.2 for <calsify@ietf.org>; Sun, 27 Apr 2025 10:55:08 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1745776508; x=1746381308; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=k/qAJeagRoVTMhpqCt2ad81lYhdqRx2sL4lJtC+GP60=; b=cpAq3RaP5Cr0CIv9VUERKJDC6XzgpbZnVL7g0XQYw9kaw7JZAbv69+tkCqNQYFY7es V7rKtvxCUmrJW9ZgQOFopT6k77isKjKo3mDpSKYrE9Xwx/5d0yy6ES0qLdqJulCQJsCR HNt3HPKaM+Vb3BLLoGXcYDxCsxETsKhO6fHiabE+wrpXiy6vG0FNgld8u4D6SsDxjYxr UtsEYtYmjUGSvIlpQGCo2kuKXgaCH1JlCQNBJqqEjqOKOi3qn4q4kFc4UE/oTezySak8 f4/dVNKCkFnk8INzXkLdQqiP37OgdmgdbhmZD63G1xvRSeYO4BQi4MLLBoyDo3UK7tHG LwZA==
X-Gm-Message-State: AOJu0YyzFVBy44nkUqbl5pajKJkXM0LTE7NTIvmFmckTq+D7S7mFutZO gwiZQJr5LS1gf4yOh0y2Wrk/1w71jlTaJgltcX52B9/S9X8lnD69a2ZWGL0NyxSgyJ1Q0la63dL dgMDtVLolXBgkqGQxEWDm754lGMA=
X-Gm-Gg: ASbGnctC5Hvsw6dnd2cr4w7DwlW4vVXkVIJ0R8vbk3acCgXCxbcGEx6l4VOEDS4VYaB 4gPCgtY8C3LnrYtjyJ/Giy3ePGpB0mTJJaPJq1iW1BfvNdbgVu+ZXuZV2CDrfm8pp3jrTw7hL7r UVIPvZii3BOJQbUYJJOvYe8vaukryve7Vf5fpD/NZ58FP/59bCROeDNUaW
X-Google-Smtp-Source: AGHT+IE4jugSZhYnKS1/VWfqZFNHdvWJ13EBeIlsJOyGHzXQBZtRM1HcnbYCKRQEW2cypUnPIPlSNLo2fMdj33mhPlU=
X-Received: by 2002:a05:6214:529e:b0:6e8:fb92:dffa with SMTP id 6a1803df08f44-6f4d1f1a8eemr122781876d6.25.1745776507923; Sun, 27 Apr 2025 10:55:07 -0700 (PDT)
MIME-Version: 1.0
References: <527ae9bd-0d91-4755-8293-a445b5c9c4df@app.fastmail.com>
In-Reply-To: <527ae9bd-0d91-4755-8293-a445b5c9c4df@app.fastmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sun, 27 Apr 2025 13:54:57 -0400
X-Gm-Features: ATxdqUFSNwR0Bd5umVFrOwbdecFEqKV8i-T3W-DxuxRWr0-EfwLJGh4_T7lGDVo
Message-ID: <CAMm+LwjvsPzxtNLpHFYxJ9TrACjvOXFrLb+479_Qgyd_6v6fAw@mail.gmail.com>
To: Robert Stepanek <rsto=40fastmailteam.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009cb4870633c644fc"
Message-ID-Hash: MP7GSAFLGUFUWXNHK4S2ABYFOGGB2ROZ
X-Message-ID-Hash: MP7GSAFLGUFUWXNHK4S2ABYFOGGB2ROZ
X-MailFrom: hallam@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-calsify.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: calsify@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [calsify] Re: JSContact: supporting multiple names?
List-Id: Calendaring and Scheduling Standards Simplification <calsify.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/omdCdW2_IFCFS-f1vgds0eDgrj4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Owner: <mailto:calsify-owner@ietf.org>
List-Post: <mailto:calsify@ietf.org>
List-Subscribe: <mailto:calsify-join@ietf.org>
List-Unsubscribe: <mailto:calsify-leave@ietf.org>

Use of multiple personal names is very common.

Women often change their name on marriage or divorce for a start. And that
means that it can be really hard to track publications. I didn't use my
full surname until college, last thing you want at an English public school
is a double barrelled surname. Actors commonly use stage names and so on.

It is important to distinguish between active names and former names.



On Wed, Apr 23, 2025 at 7:59 AM Robert Stepanek <rsto=
40fastmailteam.com@dmarc.ietf.org> wrote:

> During IETF last call for RFC 9553 and also recently, we got notified that
> JSContact does not support to have more than one personal name. This is in
> contrast to vCard, where multiple FN properties are allowed to be set.
>
> We are open to introducing support for multiple names in JSContact, but we
> would first like to understand the requirements. Other than localized
> names, which already are supported in current JSContact, what are the
> situations where someone would have multiple names? How would someone know
> which name to choose to address the contact represented by that card?
>
> Regards,
> Robert
>
>
> _______________________________________________
> calsify mailing list -- calsify@ietf.org
> To unsubscribe send an email to calsify-leave@ietf.org
>