Re: [httpapi] Question about schema ressource discovery
Mark Baker <distobj@acm.org> Mon, 20 November 2023 15:36 UTC
Return-Path: <mark@coactus.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 5F912C15199D for <httpapi@ietfa.amsl.com>; Mon, 20 Nov 2023 07:36:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.656
X-Spam-Level:
X-Spam-Status: No, score=-6.656 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 gXelcVjMF9ZB for <httpapi@ietfa.amsl.com>; Mon, 20 Nov 2023 07:36:54 -0800 (PST)
Received: from mail-pf1-f169.google.com (mail-pf1-f169.google.com [209.85.210.169]) (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 A33DBC151998 for <httpapi@ietf.org>; Mon, 20 Nov 2023 07:36:54 -0800 (PST)
Received: by mail-pf1-f169.google.com with SMTP id d2e1a72fcca58-6c33ab26dddso3856303b3a.0 for <httpapi@ietf.org>; Mon, 20 Nov 2023 07:36:54 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700494614; x=1701099414; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=gZUi06qBwz5Sv+ZtROunX70/50VALKof0Ti5TjgbKVg=; b=r5wDQjF/FzXaIYnQDH9iMaXp60yadSMwzZpEt6B6UWUpQRxOoJZDFu6+z4moWSGyQ0 CxkaksqnAn/ACZauI9uWuN+CArYvc5/HOiaJElF3IPmWBHCaeQXBstbEy6/xGPhuM8Ke vkml8qWn2Nlf1peY+jItWOpdgCYBR/EzhnziQ3nPyLAA7unwtkkG+LXUcyBrklsbT2p/ 1MXu+97KcAaxmd8o3c/JYsPwwckhExPOMKifjNZT95b5jRFsNL2VnMr2QWC7F+ADosle ss7wvQNFpAc0oEbdi5odep8+1Fq6F3f9L8hCguggfOLpHda9ZsasjLbvJm8yMy3Z33AT 8shw==
X-Gm-Message-State: AOJu0Yy1qymjSi9ZFLfwlBq6kPtDPvvVQF+GdFdQzXpTr4jXBw065Idt /OaIukGZh0Pc6WvQceKlKaf/AsuPYu3m/zuK0/uqbHD54tmoyRly
X-Google-Smtp-Source: AGHT+IGzn29xKGVNXp4VvwO2aL6fycuEfuTZMISkpZbj+0Q3n3Vttwkz5OAuoy26I9Y8ciybTNIY466fPe7x1x8tuOc=
X-Received: by 2002:a17:90b:164f:b0:280:3b2:d37a with SMTP id il15-20020a17090b164f00b0028003b2d37amr5387194pjb.18.1700494613793; Mon, 20 Nov 2023 07:36:53 -0800 (PST)
MIME-Version: 1.0
References: <167D6B6D-08CD-4033-8FDC-2E78A76AFAC5@gmail.com>
In-Reply-To: <167D6B6D-08CD-4033-8FDC-2E78A76AFAC5@gmail.com>
From: Mark Baker <distobj@acm.org>
Date: Mon, 20 Nov 2023 10:36:42 -0500
Message-ID: <CALcoZirGMm+CEVb6AfY2qy5RRPVfzSB8+J=kmBXT9SAat6wp8Q@mail.gmail.com>
To: Sascha Kohlmann <sascha.kohlmann@gmail.com>
Cc: HTTPAPI Info Page <httpapi@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/s0AdpkY-ITUVKeqWT_elpwZ0TVU>
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: Mon, 20 Nov 2023 15:36:56 -0000
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. Mark.
- [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