IETF Logo Mail Archive

[calsify] Re: JSContact: supporting multiple names?

Mauro De Gennaro <mauro@stalw.art> Wed, 23 April 2025 12:40 UTC

Return-Path: <mauro@stalw.art>
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 450AD1FF380C for <calsify@mail2.ietf.org>; Wed, 23 Apr 2025 05:40:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=stalw.art header.b="b89VqSgu"; dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=stalw.art header.b="qQQj+ipK"
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 VJE_RWy28c3A for <calsify@mail2.ietf.org>; Wed, 23 Apr 2025 05:40:09 -0700 (PDT)
Received: from mail.stalw.art (mail.stalw.art [135.181.195.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id CF7561FF3802 for <calsify@ietf.org>; Wed, 23 Apr 2025 05:40:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; s=202404r; d=stalw.art; c=relaxed/relaxed; h=To:Message-Id:Date:Subject:From; t=1745412006; bh=csX0OS/TsAuopILFV4OeEXP 4V3orMOsbK23sjfkKwMo=; b=b89VqSguml9QQdK8VdDnHVWC8b6gLDpVr7g+4LMHVftvIlWFoV ep7Y05r1C5xOqtGOtN9NTJFQwgyXqImqowfGfIvRRVE1R9im33x3oVhko1Ig9w9SQPRM1nzTqfI kztWI5/x3GKp/7Ac0SRQqi2W5Gbkg9j01WgayIlcflzb+7MYnCsURWElJvDre1Mx9DeucvfC1Yz 3NBgTpcJJsZJjFrW4yrypqSWyxB88oQRU5ScW/bm+VP1qU7x3GT3aE7JC6pGvA2wHVFDnlfxuh2 XkmfxoIfpmvduX1ZrFN0Op88CvD03SB5NNIZ9TdeGVGdZ68eBXG9dRku5oAiB3Gx2yA==;
DKIM-Signature: v=1; a=ed25519-sha256; s=202404e; d=stalw.art; c=relaxed/relaxed; h=To:Message-Id:Date:Subject:From; t=1745412006; bh=csX0OS/TsAuopILFV4OeEXP 4V3orMOsbK23sjfkKwMo=; b=qQQj+ipKaJEvS1RXjDvzR/QinpEOt+kXPj3VhU6pQ+uVmhOf1D IxG7GaX0xHZcht6a03qU6J9HuPJnO/hSdGBw==;
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Mauro De Gennaro <mauro@stalw.art>
Mime-Version: 1.0 (1.0)
Date: Wed, 23 Apr 2025 14:39:55 +0200
Message-Id: <E39B63F5-AF4D-4C98-A9CE-3C9FF83B8F9C@stalw.art>
References: <527ae9bd-0d91-4755-8293-a445b5c9c4df@app.fastmail.com>
In-Reply-To: <527ae9bd-0d91-4755-8293-a445b5c9c4df@app.fastmail.com>
To: Robert Stepanek <rsto=40fastmailteam.com@dmarc.ietf.org>
X-Mailer: iPhone Mail (22D82)
Message-ID-Hash: SW35DJWQR6DEPMUSD6EI2SQROA7HHYZQ
X-Message-ID-Hash: SW35DJWQR6DEPMUSD6EI2SQROA7HHYZQ
X-MailFrom: mauro@stalw.art
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/yy2-o8R44z5Dapj95EGrsSXmiqM>
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>

Hi Robert,

I can’t think of a single use case for supporting multiple full names beyond localization, but this is already supported in JSContact with patch objects.

It would be nice to be able to represent in JSContact the multiple FN properties found in a vCard, but this can be done under a separate object. This is related to the previous JSCalendar thread, in order to allow lossless conversion between formats we need a way to represent every iCal/vCard property and parameter in JSCalendar/JSContact.

-Mauro

> On 23 Apr 2025, at 1:59 pm, 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

v2.46.0 | Report a Bug | By Email | System Status