[calsify] Re: Question about organizerCalendarAddress in JSCalendar bis

Mauro De Gennaro <mauro@stalw.art> Tue, 07 October 2025 11:57 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 C89F86E8DC66 for <calsify@mail2.ietf.org>; Tue, 7 Oct 2025 04:57:31 -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=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=stalw.art header.b="RMGEmXKk"; dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=stalw.art header.b="nIkeHAaD"
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 MIzR-rxVhN8p for <calsify@mail2.ietf.org>; Tue, 7 Oct 2025 04:57:31 -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) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 41DF36E8DC61 for <calsify@ietf.org>; Tue, 7 Oct 2025 04:57:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; s=202404r; d=stalw.art; c=relaxed/relaxed; h=Message-Id:To:Date:Subject:From; t=1759838250; bh=SXq2+zzK5RMwf0qg3B4jW7F ITL5SZm6okto8XwispXc=; b=RMGEmXKkIN7bpP4+LfmZsYqTmoJl9ddpMVXSYxyJn9MjOs3WK3 7WIxZMK97qg7jstT7zY2RbrF3Y+qssQxXag6Om6m34Vkc7CQKhfZgJ+mKTqsPt6/elYU5SS+6e0 4p0aYyM9RiCAOxR0TF51wQmtGso318XAQC0AkdOGYSIdz/xhNPJlytkzP1R/s2rhBs2cTdfX1cp Qm1qHn78w/Rv+G++umz+mUgn5Qa3bXG02OG8+j4WQ0yuB0hc8Nh2eRWe1+Xa4l54adb+7fPpNw1 lrZyMnA6t41tJP95jugMBYRyhcskxA/S/2N5N62qcWHNk7cSw1jj7/2NNOOI0ETt0Zg==;
DKIM-Signature: v=1; a=ed25519-sha256; s=202404e; d=stalw.art; c=relaxed/relaxed; h=Message-Id:To:Date:Subject:From; t=1759838250; bh=SXq2+zzK5RMwf0qg3B4jW7F ITL5SZm6okto8XwispXc=; b=nIkeHAaDZSB3wJq0Kjm6O/8Qv/uBszcJYcAF29DhPI79iNHYkf ckE5XaD41clfwLEG0D+abt2EJCFieUaVmBDA==;
From: Mauro De Gennaro <mauro@stalw.art>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6.1.11\))
Date: Tue, 07 Oct 2025 13:57:19 +0200
References: <FCD2E6CD-63E5-4E9E-AE36-B3755E4E9060@stalw.art> <f64ae60a-64df-4ddd-958f-2b69ae36efc0@dogfoodapp.fastmail.com> <B0709D29-A239-432F-B382-ABF66F404958@stalw.art> <0851af7a-73e6-4e65-ab90-10fa32b3a9af@dogfoodapp.fastmail.com> <c5c80aa9-7f4b-4be5-b1e8-ffbcb4193ff3@app.fastmail.com> <0D46DDD6-1639-426C-858F-5E7B9A1AB3B4@stalw.art> <c9dc1727-ee93-45df-a59c-b386b5debdd6@app.fastmail.com>
To: calsify@ietf.org
In-Reply-To: <c9dc1727-ee93-45df-a59c-b386b5debdd6@app.fastmail.com>
Message-Id: <E95C58EA-7038-4248-992B-A63C189ED3F1@stalw.art>
X-Mailer: Apple Mail (2.3731.700.6.1.11)
Message-ID-Hash: 7TLC2HNJLC334HHO6XGPBU75STFFAOTO
X-Message-ID-Hash: 7TLC2HNJLC334HHO6XGPBU75STFFAOTO
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [calsify] Re: Question about organizerCalendarAddress in JSCalendar bis
List-Id: "Calendaring, Contacts and Scheduling Standards Maintenance" <calsify.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/O2vbA-zdyVqK9L3cN7TYQNQoIho>
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 agree. It does seem that the “owner” property is used exclusively by JMAP for Calendars to enforce permissions in shared calendar scenarios, and I struggle to see how it would be useful outside that context. For example, I don’t see a meaningful use for this property when JSCalendar is used as a standalone event representation, or when used in iMIP.
> 
> This interpretation suggests that the "owner" role should rather be reserved for JMAP, not a standard value in either JSCalendar or iCalendar? I'll wait for Neil to chime in.

Yes, in one of my earlier replies to this thread I suggested that the “owner” role should be defined in JMAP for Calendars rather than in JSCalendar itself. Neil felt this was not necessary, but I haven’t yet asked him to elaborate on the reasoning.

If the “owner” role does remain defined in JSCalendar, then the calext-jscalendar-icalendar draft should clarify whether (a) it maps to a JSPROP or (b) to a new iCalendar ROLE=OWNER, which the draft could then request to be registered with IANA.


> 
>> That said, I’ve updated my conversion tool to map the “owner” role to an OWNER value for the iCalendar ROLE parameter. While this value is not currently registered, doing so simplifies permission validation (rather than looking for JSPROPs) when iCalendar is used as the underlying representation on the server side.
> 
> Just please don't share that non-standard OWNER role value with CalDAV clients or over iTIP until we registered it at IANA. There's already so much non-standard iCalendar data out there, we shouldn't put more on that pile.

Yes, this is purely for internal representation at the moment. However, if “owner” remains part of JSCalendar, I would prefer that a new OWNER role be formally registered with IANA, as its presence in JSCalendar would imply that it could also be useful in the iCalendar context.


> Do you agree that we should remove the "attendee" role?

Yes, I agree. It seems unnecessary, as the intent is already clear from the participant’s status as required, optional, or informational.


Best,
Mauro