IETF Logo Mail Archive

Re: [Sml] text/plain and SML data display

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Thu, 08 February 2024 13:48 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: sml@ietfa.amsl.com
Delivered-To: sml@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A288BC209B41 for <sml@ietfa.amsl.com>; Thu, 8 Feb 2024 05:48:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ohjf1f0Z4Yle for <sml@ietfa.amsl.com>; Thu, 8 Feb 2024 05:48:18 -0800 (PST)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [144.76.73.169]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47A03C14F5EA for <sml@ietf.org>; Thu, 8 Feb 2024 05:48:17 -0800 (PST)
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 41C55C0050; Thu, 8 Feb 2024 13:48:14 +0000 (GMT)
Authentication-Results: stabil.gulbrandsen.priv.no; dmarc=none (p=none dis=none) header.from=gulbrandsen.priv.no
Authentication-Results: stabil.gulbrandsen.priv.no; spf=none smtp.mailfrom=gulbrandsen.priv.no
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1707400094; bh=HKIn4yMA1eFe1BZtpVk4P9CQZSGBbMapmiLWsxVn6E4=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=aCjgfHEMTcyiK2QKmP2O455Bb0oqOOaHV4lRuxO5OMVvzySvpqqMdp+tHsFnmyekI 2/sDW0iJJLBj7By4OD/2N/TgRqDwIicNVTcvFT/AayL1mxA5K5M4+oSUPch32T8u4G 69oTVXBcSgZiwc0SvKq7RxHzjfR6qg4+LdKTXiks=
Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1707400093-2324-2316/9/474; Thu, 8 Feb 2024 13:48:13 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Bogomil Shopov <bogomil@bogomil.info>
Cc: sml@ietf.org
Date: Thu, 08 Feb 2024 14:48:12 +0100
Mime-Version: 1.0
Message-Id: <431b77c5-7159-4b68-a28b-bd76a4c3ce26@gulbrandsen.priv.no>
In-Reply-To: <96e3ef5d-b59a-488a-8855-f86a80e2b3b7@bogomil.info>
References: <b05d5bf0-968f-4740-89af-a07da7d6d662@bogomil.info> <CAFLkOeoa9r73_xoLpGb3csjxfPWF5hbQrOsBfaJ9TGNSuHmo-g@mail.gmail.com> <5969e65e-9b2c-4002-8fc3-1309836ffe3c@bogomil.info> <CAFLkOepTpRgEsgFfoAUy7VC3N652DnFZf+WmCo0d3hrj6h0Z1A@mail.gmail.com> <2d449728-fed1-4eeb-8668-84ccc2f92e4c@bogomil.info> <96e3ef5d-b59a-488a-8855-f86a80e2b3b7@bogomil.info>
User-Agent: Trojita/v0.7-599-g1d6a1f7d; Qt/5.15.10; xcb; Linux; Devuan GNU/Linux 6 (excalibur/ceres)
Content-Type: text/plain; charset="utf-8"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sml/jZBTNd10dZC8x6yFdiYpzyb0F0k>
Subject: Re: [Sml] text/plain and SML data display
X-BeenThere: sml@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Structured Email <sml.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sml>, <mailto:sml-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sml/>
List-Post: <mailto:sml@ietf.org>
List-Help: <mailto:sml-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sml>, <mailto:sml-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Feb 2024 13:48:23 -0000

Hi,

I'm guessing that the majority preference in the AAON would be to send a 
multipart/alternative with augmented text/html as the first alternative and 
text/pan as the second.

Display subsystems that support text/pan will display that because it's 
last and one is always to use the last supported alternative; processing 
subsystems that look for SML won't support text/pan, will therefore be left 
with text/html as the last supported alternative, will look there, and use 
the structured information they find.

We in the AAON like to describe this as a win-win situation and _totally_ 
in tune with the design of MIME. "Let's call it an unanticipated feature", 
as the great language designer answered when someone reported a bug in his 
language and the bug looked useful.

Arnt

(PS: would you like to become a member of the AAON, the Association of 
Arrogant Nerds, of which I am the founder?)

v2.23.0 | Report a Bug | By Email