Re: [core] Endpoint type (et) vs. resource type (rt)

Christian Amsüss <christian@amsuess.com> Tue, 16 February 2021 20:23 UTC

Return-Path: <christian@amsuess.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5C243A1073 for <core@ietfa.amsl.com>; Tue, 16 Feb 2021 12:23:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 u9Bk3A3Dc0AF for <core@ietfa.amsl.com>; Tue, 16 Feb 2021 12:23:08 -0800 (PST)
Received: from prometheus.amsuess.com (prometheus.amsuess.com [5.9.147.112]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DEF03A1079 for <core@ietf.org>; Tue, 16 Feb 2021 12:23:07 -0800 (PST)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by prometheus.amsuess.com (Postfix) with ESMTPS id CD89C40887; Tue, 16 Feb 2021 21:23:05 +0100 (CET)
Received: from poseidon-mailbox.amsuess.com (hermes.amsuess.com [10.13.13.254]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id CCD00FD; Tue, 16 Feb 2021 21:23:04 +0100 (CET)
Received: from hephaistos.amsuess.com (hephaistos.amsuess.com [IPv6:2a02:b18:c13b:8010::aa6]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 808FB44; Tue, 16 Feb 2021 21:23:04 +0100 (CET)
Received: (nullmailer pid 603940 invoked by uid 1000); Tue, 16 Feb 2021 20:23:04 -0000
Date: Tue, 16 Feb 2021 21:23:04 +0100
From: Christian Amsüss <christian@amsuess.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: "core@ietf.org WG (core@ietf.org)" <core@ietf.org>
Message-ID: <YCwpqCQaHMdGPAzU@hephaistos.amsuess.com>
References: <8F2BA41A-011C-4C3F-88BE-D7C3E05C9465@tzi.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="Jmt24qtcy6kwZEEY"
Content-Disposition: inline
In-Reply-To: <8F2BA41A-011C-4C3F-88BE-D7C3E05C9465@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/K2EFXNcIsKOQ14kC2tfKzYTRIno>
Subject: Re: [core] Endpoint type (et) vs. resource type (rt)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Feb 2021 20:23:11 -0000

On Wed, Feb 10, 2021 at 02:42:37PM +0100, Carsten Bormann wrote:
> https://w3c.github.io/wot-discovery/#introduction-core-rd
> … uses the endpoint type as if it were a replacement for RFC 6990 rt (resource type).
> 
> Is this replacement where we want to steer people to?

No -- but it's not so much the et/rt that bugs me, but rather that they
intend to do endpoint lookups rather than resource lookups.

Opened <https://github.com/w3c/wot-discovery/issues/120>; maybe the
reactions also give a clue on why that turn was taken.

thx
c

-- 
Build a man a fire, and he'll be warm for a day. Set a man on fire, and
he'll be warm for the rest of his life.
  -- Terry Pratchett (attributed)