Re: [httpapi] Question about schema ressource discovery
Sascha Kohlmann <sascha.kohlmann@gmail.com> Tue, 21 November 2023 06:59 UTC
Return-Path: <sascha.kohlmann@gmail.com>
X-Original-To: httpapi@ietfa.amsl.com
Delivered-To: httpapi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEF7EC14CE24 for <httpapi@ietfa.amsl.com>; Mon, 20 Nov 2023 22:59:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 BqigF2Cb34mU for <httpapi@ietfa.amsl.com>; Mon, 20 Nov 2023 22:59:59 -0800 (PST)
Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 79FD4C14CE53 for <httpapi@ietf.org>; Mon, 20 Nov 2023 22:57:59 -0800 (PST)
Received: by mail-wr1-x42e.google.com with SMTP id ffacd0b85a97d-33139ecdca7so3185397f8f.0 for <httpapi@ietf.org>; Mon, 20 Nov 2023 22:57:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700549877; x=1701154677; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=+ZAImgESF/4ge2V/CEYW5l2sY2jZWxLDvjxstOivx88=; b=W15zjYe1NG2sU1ov2RtglDSEueXtDEPUNVn1PWgk+PaWa7domR4TCkJV0aMQi5uvFl YGmd8QVDtinNRc1wiVTwtmpOeyojsBnaGAuack5HT5HQ/SyP0YTjjH6cXLutbAN3DnOL ZfnlPa9iTQieWDJJYUQXaNEulFlfJqL45QKj0ybNgPr3V77kO0bVIX3pL9I4MZf6ShT/ +OFOBYzu3eoS1+UlViQPmklCg/QgQZhmD+snYUlqUUR2cTmu/KRxjQggmWOkA/252jAS 7knZI+Ra/4SCn/EyuXo4S0Yx26CMGrASUfF6R/mThnIYNJ8GSNe1Bmce8AZ/Ivlcs7Oz 2C/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700549877; x=1701154677; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=+ZAImgESF/4ge2V/CEYW5l2sY2jZWxLDvjxstOivx88=; b=ZJie5e2dHZMp2ho/U7miOWGQCBSeo1ooIWTXx1cteNZ2+Y9bgkiemdc6ooyb0/WnAY F+kYA+L+04jHlBWz5T/0YJScy8aWhz5xTzf+HvZYwrzm3owvknpwARvoncNRNh+xi0HW D5fGhrv+HPnw5OkZ9sLqA7QvjjOeEygVle5g40MvzFChb2trdZMzbccvcmGcsQKfNs65 Ayr1wOIQAormw8hr7DaeuHumKb2f6SMDwi3Vjjpfa4gqSa0kkDlmDcBku/Sfix0GH45H KZQXHbeX13EMqX0JOUKAbxvlJFJrl+bhzCwF9Ee63NkZ8fGF/aLLgT9qtOxF11bh9Ja+ LJ9Q==
X-Gm-Message-State: AOJu0YxRaQlmLEowEzyk47IAkLFFXs0WQn/kIaBmlPzdxljkHmJ/QRrj /Ii3V+opsW0B336LbpLLycEK6zVXiUM=
X-Google-Smtp-Source: AGHT+IH1Q5Z84O6n2rqkbK6nymD7MwdQi8a8WZOJdRyABG3IjiwV2d2wHGP31/bh+AH2hor5l2Iykw==
X-Received: by 2002:a5d:6985:0:b0:32f:7d50:267e with SMTP id g5-20020a5d6985000000b0032f7d50267emr7317975wru.9.1700549876588; Mon, 20 Nov 2023 22:57:56 -0800 (PST)
Received: from smtpclient.apple (dynamic-077-013-036-107.77.13.pool.telefonica.de. [77.13.36.107]) by smtp.gmail.com with ESMTPSA id d19-20020adf9b93000000b003316eb9db40sm11253155wrc.51.2023.11.20.22.57.56 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Nov 2023 22:57:56 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\))
From: Sascha Kohlmann <sascha.kohlmann@gmail.com>
In-Reply-To: <CALcoZirGMm+CEVb6AfY2qy5RRPVfzSB8+J=kmBXT9SAat6wp8Q@mail.gmail.com>
Date: Tue, 21 Nov 2023 07:57:44 +0100
Cc: Mark Baker <distobj@acm.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D604A13E-E6EE-414F-9EE4-267D5FE947C4@gmail.com>
References: <167D6B6D-08CD-4033-8FDC-2E78A76AFAC5@gmail.com> <CALcoZirGMm+CEVb6AfY2qy5RRPVfzSB8+J=kmBXT9SAat6wp8Q@mail.gmail.com>
To: HTTPAPI Info Page <httpapi@ietf.org>
X-Mailer: Apple Mail (2.3774.200.91.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/J5182iiZoZVSy-R8Hm8kwITL24Q>
Subject: Re: [httpapi] Question about schema ressource discovery
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/httpapi>, <mailto:httpapi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi/>
List-Post: <mailto:httpapi@ietf.org>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpapi>, <mailto:httpapi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Nov 2023 07:00:00 -0000
> Am 20.11.2023 um 16:36 schrieb Mark Baker <distobj@acm.org>: > > On Sun, Nov 19, 2023 at 11:20 AM Sascha Kohlmann > <sascha.kohlmann@gmail.com> wrote: >> >> Hello everyone >> >> Mike Amundsen encouraged me on X/Twitter to join this professional group >> as I have a question about web linking. I hope you can help me. >> >> The use case is quite simple. I have a sender of a message that defines >> the content type "application/json". The recipient of the message needs >> to validate the content of the message. I have a JSON schema for this. > > I would say that best practice here is to use a media type specific to > your format, rather than application/json. Thank you very much, Mark. I'll do the same. Unfortunately, many developers are a bit careless and also overwhelmed in API design. Even the fact that there can be custom media types is unknown to many. That's sad, but it's my lived reality. And because this is the case, many developers use 'application/json' as the media type for everything that is coded with JSON. From their point of view, it is sufficient that the sender and recipient already know what to do based on the URL and the OpenAPI documentation. In other words: you are proposing a static binding. I welcome that. The reality is often dynamic binding. This has enormous disadvantages. But a Python developer who has done nothing else for 20 years doesn't think about static binding in API design. -Sascha
- [httpapi] Question about schema ressource discove… Sascha Kohlmann
- Re: [httpapi] Question about schema ressource dis… Evert Pot
- Re: [httpapi] Question about schema ressource dis… Graham Cox
- Re: [httpapi] Question about schema ressource dis… Sascha Kohlmann
- Re: [httpapi] Question about schema ressource dis… Mark Baker
- Re: [httpapi] Question about schema ressource dis… Sascha Kohlmann