[Sml] Re: [draft-ietf-sml-structured-email] Referencing structured data in text/html
Ben Bucksch <ben.bucksch@beonex.com> Tue, 04 March 2025 11:10 UTC
Return-Path: <ben.bucksch@beonex.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 EC78C70ED17 for <sml@mail2.ietf.org>; Tue, 4 Mar 2025 03:10:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=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 2mqKuMc2h7jl for <sml@mail2.ietf.org>; Tue, 4 Mar 2025 03:10:58 -0800 (PST)
Received: from mail.server.beonex.com (mail.server.beonex.com [144.76.227.234]) (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 AC23270ED06 for <sml@ietf.org>; Tue, 4 Mar 2025 03:10:58 -0800 (PST)
Received: from mail.beonex.com (fire3.beonex.com [88.99.137.225]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mail.server.beonex.com (Postfix) with ESMTPS id 4BBC9A00103; Tue, 4 Mar 2025 12:10:53 +0100 (CET)
Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) by mail.beonex.com (Postfix) with ESMTPA id D26CEA06EDAC; Tue, 4 Mar 2025 11:10:52 +0000 (UTC)
Date: Tue, 04 Mar 2025 12:10:52 +0100
From: Ben Bucksch <ben.bucksch@beonex.com>
To: sml@ietf.org
In-Reply-To: <7d1bd4fd-7576-477e-a92e-5e183dfa9ff5@audriga.com>
References: <7d1bd4fd-7576-477e-a92e-5e183dfa9ff5@audriga.com>
Message-ID: <B14BD15D-858F-43A9-9B8C-37A32560DA9F@beonex.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Authentication-Results: mail.beonex.com; auth=pass smtp.auth=ben@bucksch.name smtp.mailfrom=ben.bucksch@beonex.com
X-Spamd-Bar: +++
Message-ID-Hash: IAAOB2G4V5UT3XFPVXT76JZOUGTOQAIE
X-Message-ID-Hash: IAAOB2G4V5UT3XFPVXT76JZOUGTOQAIE
X-MailFrom: ben.bucksch@beonex.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: [draft-ietf-sml-structured-email] Referencing structured data in text/html
List-Id: Structured Email <sml.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sml/tNP8qJqubiF47sjkvkcdau2xjo0>
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>
Am 3. März 2025 17:22:04 MEZ schrieb Hans-Joerg Happel <happel@audriga.com>: >how to reference nodes/items from the structured data from within the text/html ... > `<a data-id=”https://cooking.nyt.com/sheet-pan-chopped-salad” href=”...”>sheet-pan chopped salad with chicken</a>` That makes sense to me. It might make processing in the MUA even easier: If I can process SML, and then I likely already extracted and parsed the SML and can access it easily. Requiring me to remember which cid it came from would be an additional burden. So, unless I'm missing something, this actually makes it easier than with cid. Just about the attribute name: * Please do *not* use `data-`. The entire purpose of the data- pseudo-namespace is that it's *not* part of official specs and entirely up to the page to use, without risk of conflict with standards. By using data- in standards, the point is nullified. * Use an attribute namr specific to SML. a) it avoids name conflicts and b) I (as MUA) know that I need to look in the SML to get more info. So, I'm proposing, as small alteration to your proposal: `<a sml-id=”https://cooking.nyt.com/sheet-pan-chopped-salad” href=”...”>sheet-pan chopped salad with chicken</a>` Ben
- [Sml] [draft-ietf-sml-structured-email] Referenci… Hans-Joerg Happel
- [Sml] Re: [draft-ietf-sml-structured-email] Refer… Ben Bucksch
- [Sml] Re: [draft-ietf-sml-structured-email] Refer… Steffen Nurpmeso