IETF Logo Mail Archive

[Sml] Structured quoting

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Mon, 27 April 2026 20:48 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
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 8BDC2E43052E for <sml@mail2.ietf.org>; Mon, 27 Apr 2026 13:48:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1777322886; bh=rgvPCinIjD/lK3xxnmNztdo44o3tcoSF5e1kDeRrxDA=; h=From:To:Subject:Date; b=YxYJo9+5MpKouFGOrMxVvyhoua+JR3OlZkO17vb3ksWl6O7lHl+gHYqcvDy54gC2K 0LvTk1Qae3Z17iIgBYrsohcy3h7BpleJtDbghBpxZ1Wxgv8shQTjPMbZZ/1uiOjscu TiKpjRYOoV/LwALS2oAnfR+plRs2GOwzPnPwCaio=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, 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=gulbrandsen.priv.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 DHzNHXHQtddH for <sml@mail2.ietf.org>; Mon, 27 Apr 2026 13:48:06 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) (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 1E471E430529 for <sml@ietf.org>; Mon, 27 Apr 2026 13:48:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1777322884; bh=rgvPCinIjD/lK3xxnmNztdo44o3tcoSF5e1kDeRrxDA=; h=From:To:Subject:Date:From; b=mbA4gZzYgfeMqHtVdfrpg/yedlYDg7ps+MeI2LMqGdb0sIzdzkQlyqW/yR4HpkavG coTxo4bGOfq9VYiBQ5S1pcaz/m+a5AltcZfeSjIrzpFgGfM1VGglsjQgUGccZouD9R z7eniWkTdRRZx9y8goT47hLWZ1T7o/F2OJmWJNug=
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) by stabil.gulbrandsen.priv.no (Postfix) with ESMTP id 60E67C001A; Mon, 27 Apr 2026 21:48:03 +0100 (IST)
Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1777322882-3471-3470/9/17; Mon, 27 Apr 2026 20:48:02 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: sml@ietf.org
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/30.2
Date: Mon, 27 Apr 2026 22:48:02 +0200
Message-Id: <87lde82kql.fsf@libertango.gulbrandsen.priv.no>
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"
Message-ID-Hash: HVEDEYQOCJS5SKMCFKS3X5ZGZFJ5CAOZ
X-Message-ID-Hash: HVEDEYQOCJS5SKMCFKS3X5ZGZFJ5CAOZ
X-MailFrom: arnt@gulbrandsen.priv.no
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] Structured quoting
List-Id: Structured Email <sml.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sml/NrC9tAlU1W8vf0tXAIf4RuLJH64>
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,

one of the things I've implemented now is structured quoting, 
which I've done twice (once to generate, once to render).

I found both really easy, but in one case I had to make it really 
easy by putting the JSON-LD in a HTML comment when I generated 
outgoing mail, and in the other I had to assume that the JSON-LD 
is in the HTML I parse (because the existing surrounding code 
assumed that parsing the text/html was enough to generate HTML for 
display.)

Phillip's draft currently specifies that the JSON-LD goes in a 
separate MIME part, because the main draft has a corresponding 
rule.

Based on this overwhelming number of samples (two) I suggest 
specifying that the JSON-LD goes in the HTML, always, not 
optionally.

Arnt

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