[Sml] Re: [EXT] Re: Suppressing SML fallbacks
Happel <happel@audriga.com> Sun, 19 July 2026 13:14 UTC
Return-Path: <happel@audriga.com>
X-Original-To: sml@mail2.ietf.org
Delivered-To: sml@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id A15DE11996C98 for <sml@mail2.ietf.org>; Sun, 19 Jul 2026 06:14:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784466864; bh=AS8M/TSv5QG+gvjYZ0G16bFrJDy+bL+KqYS/6WxbmC8=; h=From:To:In-Reply-To:References:Subject:Date; b=I0TdEp+pbBvOaswSDgK8l/wKMOanwmLPFyWkMKOBv3EJBAmZ9cKCMEb77Q0U3aIUB /VUIX20LzO6av5DkaTwuHm6011NvE25JFed2sfW3xx/rPYfapwcsDLnc19yUHXDiob BXLf2XqwR+ZgWTNcSHGjKxSxEGAMBfIfu+eBCay0=
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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=audriga.com header.b="zXYwMsTG"; dkim=pass (1024-bit key) header.d=audriga.com header.b="zXYwMsTG"
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 qbrRTlL5SeUL for <sml@mail2.ietf.org>; Sun, 19 Jul 2026 06:14:24 -0700 (PDT)
Received: from mail.audriga.com (mail.audriga.com [IPv6:2a01:4f8:c013:1f9e::1]) (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 EC98911996C91 for <sml@ietf.org>; Sun, 19 Jul 2026 06:14:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=audriga.com; s=mail; t=1784466855; bh=AS8M/TSv5QG+gvjYZ0G16bFrJDy+bL+KqYS/6WxbmC8=; h=From:To:In-Reply-To:References:Subject:Date:From; b=zXYwMsTG2QlkrzRSJyp2b6BW4uMCh/4ImKozBT6K5a55JZuX4hvlFglUZBCA7rUMA PppmCzw3WFQr96Ijlt+pWhaEn/R6HzFq4v0hoziSKKHlOvTl+E5BFwiiI+3zJ+4kYk OR03ggB/vpm4Y7hvNTZoxigX2MKFpCxD7cFbHr5k=
Received: from localhost (localhost [127.0.0.1]) by mail.audriga.com (Postfix) with ESMTP id E820935B580; Sun, 19 Jul 2026 13:14:15 +0000 (UTC)
X-Virus-Scanned: Debian amavis at mail.audriga.com
Received: from mail.audriga.com ([127.0.0.1]) by localhost (mail.audriga.com [127.0.0.1]) (amavis, port 10024) with ESMTP id PYk1txIBeV4E; Sun, 19 Jul 2026 13:14:15 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=audriga.com; s=mail; t=1784466855; bh=AS8M/TSv5QG+gvjYZ0G16bFrJDy+bL+KqYS/6WxbmC8=; h=From:To:In-Reply-To:References:Subject:Date:From; b=zXYwMsTG2QlkrzRSJyp2b6BW4uMCh/4ImKozBT6K5a55JZuX4hvlFglUZBCA7rUMA PppmCzw3WFQr96Ijlt+pWhaEn/R6HzFq4v0hoziSKKHlOvTl+E5BFwiiI+3zJ+4kYk OR03ggB/vpm4Y7hvNTZoxigX2MKFpCxD7cFbHr5k=
Received: from [127.0.0.1] (unknown [31.130.238.7]) by mail.audriga.com (Postfix) with ESMTPSA id C8B9B35B57F; Sun, 19 Jul 2026 13:14:14 +0000 (UTC)
User-Agent: Mustang/0.9.34 Parula/0.9.34
From: Happel <happel@audriga.com>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, sml@ietf.org, Ben Bucksch <ben.bucksch@beonex.com>
In-Reply-To: <51SoKRXB4fsH5xlB23GyYy9B0ltqVy1mtnbcXJ8yAOk=.sha-256@antelope.email>
References: <87pl3k2l0o.fsf@libertango.gulbrandsen.priv.no> <7d018465-e97f-27f4-3be3-2404de50ef72@beonex.com> <51SoKRXB4fsH5xlB23GyYy9B0ltqVy1mtnbcXJ8yAOk=.sha-256@antelope.email>
Message-ID: <444551d0-bbe3-6573-6cdb-feab5cd74a05@audriga.com>
Date: Sun, 19 Jul 2026 13:14:11 +0000
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_NmP-d9dba0bb8eaad320-Part_1"
Message-ID-Hash: DQP6UHMJRPQOVG4SLYIOL3LRRVBAXSDS
X-Message-ID-Hash: DQP6UHMJRPQOVG4SLYIOL3LRRVBAXSDS
X-MailFrom: happel@audriga.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; 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: [Sml] Re: [EXT] Re: Suppressing SML fallbacks
List-Id: Structured Email <sml.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sml/qYKB2T6DxCbesIy99chWAD_pKFw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sml>
List-Help: <mailto:sml-request@ietf.org?subject=help>
List-Owner: <mailto:sml-owner@ietf.org>
List-Post: <mailto:sml@ietf.org>
List-Subscribe: <mailto:sml-join@ietf.org>
List-Unsubscribe: <mailto:sml-leave@ietf.org>
Hi Arnt, can do, but would help me understand better, if you could illustrate the particular use case you had in mind. As Ben wrote, the referencing mechanism is close to this and a solution for what you have in mind should probably be part of that. I'll add a discussion point for this to my slides for the session. Best, Hans-Joerg Arnt Gulbrandsen wrote on 4/28/2026, 8:09 PM: > Hi, > > Now that your say it, I remember that. > > Perhaps the spec should be "render either this or your json-ld thing, your > choice, they're equivalent". > > HJ? Can you add this to the draft, unless you disagree? > > Arnt > > On 2026-04-28 Ben Bucksch <ben.bucksch@beonex.com> wrote: > > > Hey Arnt, SML group, > > > > Arnt Gulbrandsen wrote on 27.4.2026, 22:41: > > > > > SML is extremely minimal in some senses, there's no rendering advice or > > > anything. When I composed some mail on Friday, I found that there was > > > something I wanted: Suppose you send some HTML mail and you attach some > > > SML. Fine. You may want to add a fallback of some sort. In actual fact I > > > immediately … > > > > Yes, there's definitely a need for that. > > > > We've discussed this about a year ago, in one of the IETF meetings. HJ > > suggested to mark this fallback HTML element with an attribute that > > references an ID in the SML. That attribute tells the renderer that the SML > > is equivalent to that HTML element, so the renderer can do its fancy > > programmatic rendering instead of the static HTML. We had this conceptually > > mostly nailed down, and were fairly concrete in the solution. We stopped > > just short of defining the exact HTML attribute name, value, and how IDs > > look like and how exactly they are found in the SML. > > > > Why important: E.g. the Polls usecase that I presented at FOSDEM 2026 > > [https://fosdem.org/2026/schedule/event/JQSRHP-parula/] You want the > > responses from all recipients, not only those that happen to use Parula or > > HJ's version of K9Mail. So, my plan (not implemented yet) is to include a > > static preview of the options, and a link to a webpage, where the recipient > > can then answer the poll. Parula (and other SML mail readers that support > > this particular "meeting time poll" usecase) can render the calendar UI > > inline, and merge the poll with my own calendar, which supports me better, > > but non-Parula users can still respond. For this to work, Parula needs to > > know at which point in the HTML the fallback is, so that it can replace it. > > > > Ben > > > > -- > > Beonex GmbH > > Taunusstein bei Wiesbaden, Germany > > CEO / Geschäftsführer: Ben Bucksch > > Handelsregister: Amtsgericht Wiesbaden, HRB 30065 > > > > -- > > > > Sml mailing list -- sml@ietf.org > > > > To unsubscribe send an email to sml-leave@ietf.org > > -- > Sml mailing list -- sml@ietf.org > To unsubscribe send an email to sml-leave@ietf.org
- [Sml] Suppressing SML fallbacks Arnt Gulbrandsen
- [Sml] Re: Suppressing SML fallbacks Ben Bucksch
- [Sml] Re: Suppressing SML fallbacks arnt
- [Sml] Re: [EXT] Re: Suppressing SML fallbacks Happel