Re: [core-parameters] Content-Format for application/sdf+json
Carsten Bormann <cabo@tzi.org> Wed, 13 March 2024 10:55 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: core-parameters@ietfa.amsl.com
Delivered-To: core-parameters@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F6FBC17C8A5 for <core-parameters@ietfa.amsl.com>; Wed, 13 Mar 2024 03:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 gyCe-jRyiP4y for <core-parameters@ietfa.amsl.com>; Wed, 13 Mar 2024 03:55:09 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.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 16E5BC1519A7 for <core-parameters@ietf.org>; Wed, 13 Mar 2024 03:55:07 -0700 (PDT)
Received: from [192.168.217.145] (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 4TvnTh4MkpzDCf8; Wed, 13 Mar 2024 11:55:04 +0100 (CET)
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>
In-Reply-To: <DU0P190MB19785F66951350F928E80D2FFD2A2@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
Date: Wed, 13 Mar 2024 11:55:04 +0100
Cc: "core-parameters@ietf.org" <core-parameters@ietf.org>
X-Mao-Original-Outgoing-Id: 732020104.040705-94877e0200a273718a763d38c9a3e4e4
Content-Transfer-Encoding: quoted-printable
Message-Id: <614F5838-C14A-445A-B45F-E8E20C29D48B@tzi.org>
References: <02330D12-3DA3-463D-86BA-D53DCF98346E@tzi.org> <74264B36-059A-460D-A43B-170353F9A324@tzi.org> <DU0P190MB197812E7D586FE73586F5110FD242@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <74E20465-DE83-4BA1-9718-1F0652F8EC25@tzi.org> <DU0P190MB19785F66951350F928E80D2FFD2A2@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
To: Esko Dijk <esko.dijk@iotconsultancy.nl>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core-parameters/4lmEsLayBwcT-Ned5ecQvZ95f5w>
Subject: Re: [core-parameters] Content-Format for application/sdf+json
X-BeenThere: core-parameters@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Expert review of CoAP parameters." <core-parameters.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core-parameters>, <mailto:core-parameters-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core-parameters/>
List-Post: <mailto:core-parameters@ietf.org>
List-Help: <mailto:core-parameters-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core-parameters>, <mailto:core-parameters-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2024 10:55:13 -0000
On 2024-03-13, at 11:45, Esko Dijk <esko.dijk@iotconsultancy.nl> wrote: > >> Another application that is becoming more common is to use a content-format number in places like COSE’s “content type” (3) header parameter (RFC 9052) or in formats such as RFC 8710 or RFC 9193, or via Section 4.3 of RFC 9277. > > That's good to know! Agreed. > >> Right — it wouldn’t hurt to earmark a number, > Earmarking 434 - right next to the competing "Thing" formats from W3C! I wouldn’t say “compete” (this is really more like coopetition), but 434 sounds good to me. So I assume the designated experts will sign this off once approved by IESG? > Thought: should the SDF draft also have a reference to the W3C thing variant (https://www.w3.org/TR/wot-thing-description11/) and point out the differences? I’d leave that to a scientific paper… (Which you could still submit to T2TRG.) Grüße, Carsten
- [core-parameters] Content-Format for application/… Carsten Bormann
- Re: [core-parameters] Content-Format for applicat… Esko Dijk
- Re: [core-parameters] Content-Format for applicat… Carsten Bormann
- Re: [core-parameters] Content-Format for applicat… Esko Dijk
- Re: [core-parameters] Content-Format for applicat… Carsten Bormann
- Re: [core-parameters] Content-Format for applicat… Esko Dijk