IETF Logo Mail Archive

[Sml] Re: Use Cases for Structured-Email Mailing Lists: Civic Technology

Steve Atkins <steve@wordtothewise.com> Thu, 28 August 2025 09:46 UTC

Return-Path: <steve@wordtothewise.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 F14E35A05A6F for <sml@mail2.ietf.org>; Thu, 28 Aug 2025 02:46:54 -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, 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 (2048-bit key) header.d=wordtothewise.com
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 MeKy9AMoUOwC for <sml@mail2.ietf.org>; Thu, 28 Aug 2025 02:46:54 -0700 (PDT)
Received: from mail.turscar.ie (mail.turscar.ie [IPv6:2a00:1098:88:f6::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 763185A05A68 for <sml@ietf.org>; Thu, 28 Aug 2025 02:46:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=wordtothewise.com; s=blueberry; t=1756374412; bh=/XEstwz2PaEijtgYJ+ezwOJbrCVh1kFU7EZ+7cnEei0=; h=From:Subject:Date:References:To:In-Reply-To:From:Subject:Date:To: Reply-To:Cc; b=asW6v+tRc/nyKMeARi5mGJB7mRm5A9hs70ziEBoEddL5hSM9N5PSFWouR/1iIKDnW kzEKL31uulS59YsBV/KUnx8fL+MhAZr2RBvtFCxqCmHZX66wJtpXMaBQOrfXNi7G1L oc0IqDhCTXk5aKtczTfmHpWvQ+jPnaDqT72e7wOK3GUoywDlFB5CPLdN9PqwVkUB6x l8iVqtNKnkeM3saPP0YGMmECIts52+RQolZQeV9UGB1AGcZdnVn6fiIu982Ov++EUd xf+VP7qax2ES/4X9czA0fAkfRgHnx+tH9bjYokwpeI+FVsnVq1TZkOFgsx4a9YtjjD HAF+GXX/vx3fw==
From: Steve Atkins <steve@wordtothewise.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0A02123E-EFE6-4149-A897-992305184122"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
Date: Thu, 28 Aug 2025 10:46:51 +0100
References: <DS4PPF69F41B22E51E4930056540CDC2BF7C53BA@DS4PPF69F41B22E.NAMP223.PROD.OUTLOOK.COM>
To: "sml@ietf.org" <sml@ietf.org>
In-Reply-To: <DS4PPF69F41B22E51E4930056540CDC2BF7C53BA@DS4PPF69F41B22E.NAMP223.PROD.OUTLOOK.COM>
Message-Id: <7F73E189-5DC5-47E3-BBAE-19F953064A20@wordtothewise.com>
X-Mailer: Apple Mail (2.3826.700.81)
Message-ID-Hash: LJWX3XNVIWK24HQ5O4WXX3UDKPOXQIH3
X-Message-ID-Hash: LJWX3XNVIWK24HQ5O4WXX3UDKPOXQIH3
X-MailFrom: steve@wordtothewise.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: Use Cases for Structured-Email Mailing Lists: Civic Technology
List-Id: Structured Email <sml.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sml/90VJSDAp0s-Ra4fmARL_xZ-1vck>
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>


> On 28 Aug 2025, at 06:11, Adam Sobieski <adamsobieski@hotmail.com> wrote:
> 
> IETF Structured Email Working Group,
> 
> With solutions for addressing recipients' (AI) assistants now at hand, I would like to share a list of scenarios for structured-email mailing lists which pertain to (town- and city-scale) civic technology. People's town and city governments and/or their local newspapers (see: [1]) could use structured-email mailing lists to provide people with new services, features, and conveniences.
> 
> For human recipients, the frequency of their communities' emails could be challenging, daunting, or problematic, i.e., information overload. However, people's AI assistants can readily receive more frequent structured-email messages from their local governments and/or local newspapers to process and organize structured data, synchronize these data (e.g., to people's calendar view apps), and prepare to answer users' questions or to offer them well-timed notifications.

You make a compelling argument that email is not well-suited to this sort of data.

Perhaps you should consider some sort of machine-to-machine protocol, maybe RSS.

Cheers,
  Steve

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