[Asdf] Fwd: I-D Action: draft-ietf-asdf-sdf-12.txt
Carsten Bormann <cabo@tzi.org> Thu, 30 June 2022 19:22 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 33F0FC14CF1F for <asdf@ietfa.amsl.com>; Thu, 30 Jun 2022 12:22:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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
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 T1tFkIxPH81S for <asdf@ietfa.amsl.com>; Thu, 30 Jun 2022 12:22:31 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (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 64E76C14CF01 for <asdf@ietf.org>; Thu, 30 Jun 2022 12:22:29 -0700 (PDT)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4LYpB83qWKzDCf7; Thu, 30 Jun 2022 21:22:24 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
Date: Thu, 30 Jun 2022 21:22:24 +0200
X-Mao-Original-Outgoing-Id: 678309743.94945-b5010ce6be8b0f46149f600c748ad221
Content-Transfer-Encoding: quoted-printable
Message-Id: <043F15A2-E1FA-488F-9CD4-4F7460A83686@tzi.org>
References: <165661631009.27172.3376205711822535657@ietfa.amsl.com>
To: asdf@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/asdf/LQBP6XdjVQsIuGUDPHyC1chbcl8>
Subject: [Asdf] Fwd: I-D Action: draft-ietf-asdf-sdf-12.txt
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: Thu, 30 Jun 2022 19:22:34 -0000
To have a consolidated version of the SDF specification and the related data description files available for hacking activities at and around IETF 114, I submitted the current status as -12. I merged PR #81 right before that; this was about enabling the use of RFC 9193 Content-Format-Spec as a value of the contentFormat quality, so Content-Formats (Content-Type + Content-Coding) don’t have to have registered CoAP Content-Format numbers to be used in a contentFormat quality. We didn’t have much discussion of this, but I’d expect this generalization to be non-controversial as it cushions SDF a bit from being too tied to the CoAP ecosystems; I still want to draw your attention to this in case we do decide to back it out. Grüße, Carsten > Begin forwarded message: > > From: internet-drafts@ietf.org > Subject: [Asdf] I-D Action: draft-ietf-asdf-sdf-12.txt > Date: 2022-06-30 at 21:11:50 CEST > To: <i-d-announce@ietf.org> > Cc: asdf@ietf.org > Reply-To: asdf@ietf.org > Archived-At: <https://mailarchive.ietf.org/arch/msg/asdf/O1j0UP0HQS59I06R18-my7pfjQQ> > Message-Id: <165661631009.27172.3376205711822535657@ietfa.amsl.com> > > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the A Semantic Definition Format for Data and Interactions of Things WG of the IETF. > > Title : Semantic Definition Format (SDF) for Data and Interactions of Things > Authors : Michael Koster > Carsten Bormann > Filename : draft-ietf-asdf-sdf-12.txt > Pages : 102 > Date : 2022-06-30 > > Abstract: > The Semantic Definition Format (SDF) is a format for domain experts > to use in the creation and maintenance of data and interaction models > in the Internet of Things. An SDF specification describes > definitions of SDF Objects and their associated interactions (Events, > Actions, Properties), as well as the Data types for the information > exchanged in those interactions. Tools convert this format to > database formats and other serializations as needed. > > > // A JSON format representation of SDF 1.0 was defined in version > // (-00) of this document; version (-05) was designated as an > // _implementation draft_, labeled SDF 1.1, at the IETF110 meeting of > // the ASDF WG (2021-03-11). The present version (-12) collects > // smaller changes up to 2022-06-30. It also removes deprecated > // elements from SDF 1.0. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-asdf-sdf/ > > There is also an HTML version available at: > https://www.ietf.org/archive/id/draft-ietf-asdf-sdf-12.html > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-asdf-sdf-12
- [Asdf] I-D Action: draft-ietf-asdf-sdf-12.txt internet-drafts
- [Asdf] Fwd: I-D Action: draft-ietf-asdf-sdf-12.txt Carsten Bormann