[Asdf] Versions, Dates, Features, Token holders
Carsten Bormann <cabo@tzi.org> Mon, 19 April 2021 16:06 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 8550D3A38B9 for <asdf@ietfa.amsl.com>; Mon, 19 Apr 2021 09:06:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.32
X-Spam-Level:
X-Spam-Status: No, score=-2.32 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YQlXQRZpWMPd for <asdf@ietfa.amsl.com>; Mon, 19 Apr 2021 09:06:25 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0356E3A38B7 for <asdf@ietf.org>; Mon, 19 Apr 2021 09:06:24 -0700 (PDT)
Received: from [192.168.217.118] (p548dcb12.dip0.t-ipconnect.de [84.141.203.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FPBWf5hFLz11Bp; Mon, 19 Apr 2021 18:06:22 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mao-Original-Outgoing-Id: 640541182.236986-5cf56e88794cc6cd29e0ca6312d7eebc
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Mon, 19 Apr 2021 18:06:22 +0200
Message-Id: <C85E5605-08A9-41F3-B7FA-368515820E52@tzi.org>
To: asdf@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/asdf/bfoGyTrA_hzUI6nHshe-OxpbFHI>
Subject: [Asdf] Versions, Dates, Features, Token holders
X-BeenThere: asdf@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Apr 2021 16:06:30 -0000
Today at the OneDM meeting we had a look at the info block qualities. We have: * title (just some human-readable text) * version * copyright (legal) * license (legal) Today in the OneDM playground, the version quality simply contains a date string (ISO 3339 style, "2021-04-19”). Beyond the date information, we now seem to discuss pressing a lot of other information into the version quality: — semver (1.2.3, major/minor/patch), — token holder (who is expected to be evolving that spec) — date (what exactly is the date this is about?) — feature tags (which features are addressed by this model) Instead of coming up with a complicated regexp to jam all this information into a single version string, we are probably better off with just having separate qualities in the info block. What we came up with in today’s OneDM meeting: — put the semver information into the “version” quality. To make this comparable lexicographically, we simply use two-digit numbers (01.02.03). — add a “date” quality that can hold an RFC 3339 full-date or date-time for the point in time when this model was created/finalized etc., so we have covered this. (This might turn into multiple qualities if we find that different dates are relevant to a single model.) — add an “token-holder” quality, which in OneDM usage would be an (identifier-like) ecosystem name up to the time when a model is picked up by OneDM. — add feature tags, which is an (unordered) array of (identifier-like) text strings that can be used to find out whether a model addresses a particular feature or not. Info block qualities are a defined extension point in SDF 1.1, so this should not get us into trouble. (Identifier-like means that the text string is not a sentence, but something like [a-z][-a-z0-9.]* .) Comments welcome; I’d like to spend a little time discussing this on Wednesday’s ASDF interim. Grüße, Carsten
- [Asdf] Versions, Dates, Features, Token holders Carsten Bormann
- Re: [Asdf] Versions, Dates, Features, Token holde… Carsten Bormann
- Re: [Asdf] Versions, Dates, Features, Token holde… Ari Keränen