IETF Logo Mail Archive

Re: [Asdf] draft-ietf-asdf-sdf: preparing -18

Carsten Bormann <cabo@tzi.org> Mon, 26 February 2024 15:13 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: asdf@ietfa.amsl.com
Delivered-To: asdf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 453F4C15108E for <asdf@ietfa.amsl.com>; Mon, 26 Feb 2024 07:13:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=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 EOVuIyialvpK for <asdf@ietfa.amsl.com>; Mon, 26 Feb 2024 07:13:54 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (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 57014C151068 for <asdf@ietf.org>; Mon, 26 Feb 2024 07:13:53 -0800 (PST)
Received: from smtpclient.apple (p548dcbf2.dip0.t-ipconnect.de [84.141.203.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Tk3zg0sk1zDCc9; Mon, 26 Feb 2024 16:13:51 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <7A40F83D-2A37-46BE-83AA-11CAC78D5541@tzi.org>
Date: Mon, 26 Feb 2024 16:13:40 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F16B1B15-F025-4802-8CEF-BE57F4449F96@tzi.org>
References: <7A40F83D-2A37-46BE-83AA-11CAC78D5541@tzi.org>
To: asdf@ietf.org
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/asdf/NIE0-z4k3V5taiZIebVwDohbzHU>
Subject: Re: [Asdf] draft-ietf-asdf-sdf: preparing -18
X-BeenThere: asdf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" <asdf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/asdf>, <mailto:asdf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/asdf/>
List-Post: <mailto:asdf@ietf.org>
List-Help: <mailto:asdf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/asdf>, <mailto:asdf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Feb 2024 15:13:58 -0000

On Feb 20, 2024, at 11:49, Carsten Bormann <cabo@tzi.org> wrote:
> 
> On github, there are three issues outstanding that are actionable against draft-ietf-asdf-sdf-17:

These have been processed and merged, so a -18 is almost ready for submission.

There is one more thing:

https://github.com/ietf-wg-asdf/SDF/pull/154

The current CDDL can accept extensions at the various extension points using a wildcard and a .feature name.
However, there is no way for an extension to actually control what can go into the model for that extension.
As we are working on some of these extensions, this is becoming a limitation.

PR #154 adds the CDDL “sockets” (Section 3.9 of RFC 8610 [1]) needed so that extensions can simply plug into them.

This PR has received some basic testing, but no “pressure testing” in the OneDM sense (creating examples that exercise the functionality).  However, the socket definitions s are basic enough that they should just work…

Unless there is an objection to adding this functionality, we’ll include this in the -18 real soon now.

Grüße, Carsten

[1]: https://www.rfc-editor.org/rfc/rfc8610.html#section-3.9

v2.23.0 | Report a Bug | By Email