Re: [httpapi] RFC 9512 on YAML Media Type
Roberto Polli <robipolli@gmail.com> Mon, 19 February 2024 14:40 UTC
Return-Path: <robipolli@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 5CAAFC14F702 for <httpapi@ietfa.amsl.com>; Mon, 19 Feb 2024 06:40:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 ptAVFDhHJkg8 for <httpapi@ietfa.amsl.com>; Mon, 19 Feb 2024 06:40:33 -0800 (PST)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 6ABC8C14F6B7 for <httpapi@ietf.org>; Mon, 19 Feb 2024 06:40:33 -0800 (PST)
Received: by mail-lf1-x12a.google.com with SMTP id 2adb3069b0e04-512a9ae6c02so2012366e87.2 for <httpapi@ietf.org>; Mon, 19 Feb 2024 06:40:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708353631; x=1708958431; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=bZdo98VN77aAAbt/H0wyAyTZC8mPIMxiUnXeUVhB65M=; b=OYdVnMLSVLQyFuG8vlI0G29KJG2Oh1EPtbW/qP6+7J1Ovrsvtu66sFOjee6cPe1qz7 Xgmghbw/OTB8/iv5ljblesKoBuT/sJHSyZrJ/CZpUPhr+8pacIkR9anvh5ckrBdI6EhY c4Rnk3bdS3jOAhySBMRHyRDAKhVfNIzAEGTIX7neeLQUk0c5etFdvRFOTgu4IrpWJJmg KwiBqPKPFRlJw9Nug8OlyhkMVUZR4xr08EbH7thY2YFIBbpNzYL8HbXePV4ylTHsWXS+ WPfICB/76I33tnwZ6IaaDw2RzIZFgKGZlgu8yj1xqJUnyb6m0K+HceQsaCHi3mXmMcjP LBhw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708353631; x=1708958431; 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=bZdo98VN77aAAbt/H0wyAyTZC8mPIMxiUnXeUVhB65M=; b=tJaFcKFguqNZQw2oif4DhdwT1uM2hCh+auwYTUPVCe9qGVDXuElvPun9EsTI8jy8Su 4eudLCo5WSUzJxqvg7ql5uDVl9PqJwzcxuzl+leguuAwSYMOPXDwk2zr/MR5XniHOhWH 0CqCcvMH4KVku9VZFevgfl9gu9PZIVekD/xgwSAnbMhUoD6QpNehupo6jifftq6BOXI/ NHJB9DZftVCcfdEZthX3SFB/oDocxPPCFY3kXH/AR7gY8WcAyUrER78fJSvZtnaFSZhu fES0B2q9GEdw8jrFFAlP/thKQn0tAZLXH6UE6s8SivcBSVqpvGDUhbZQLPsHUTvMBJ2s T5Yg==
X-Forwarded-Encrypted: i=1; AJvYcCXcAAP16s05KBOOfR0x1wf2jqyC6olAZnnaNybqv3tokcWOQwPoT/uIddW/1tclINqrfK5xHpp8W+XLrCJJJ7nO
X-Gm-Message-State: AOJu0YxbJqyPNvfire8GtWPnJzXWziD70KC52Yl6Sr/tVAoMWLUR7p6U ya/AZlFicByW5YTYPTO8t4we1FJ4O+x4Ys1BzYqygm0i8mHTXnyjSG+BGfQJ8Wqk3fH2mLjUC3N FtEtLcoN9Mf5RMSPffSX3ZsfVs8Q=
X-Google-Smtp-Source: AGHT+IHJd4IubkPks8WqE6eIXfHrrqUtgWl4a3WtgBaQUA5EaB6c34+AQ4oSJQAf8LPVwAfRQxzjpm7niXVp1VlHtbM=
X-Received: by 2002:ac2:464f:0:b0:512:9f9b:ec50 with SMTP id s15-20020ac2464f000000b005129f9bec50mr4410653lfo.38.1708353630737; Mon, 19 Feb 2024 06:40:30 -0800 (PST)
MIME-Version: 1.0
References: <20240214220104.2BF101957AE5@rfcpa.amsl.com> <SJ2PR01MB81022C5D9B3BA6FBB43A50D5A3512@SJ2PR01MB8102.prod.exchangelabs.com> <CAP9qbHVZNtM3W36CqD6PVx_BKkVhQCvsy9D7n1GeOxJUgho-jQ@mail.gmail.com> <CAN8C-_K5HvG5TfbzmU6PsucbpfQyX=TwbX41n-nJiC5pyGQm6w@mail.gmail.com>
In-Reply-To: <CAN8C-_K5HvG5TfbzmU6PsucbpfQyX=TwbX41n-nJiC5pyGQm6w@mail.gmail.com>
From: Roberto Polli <robipolli@gmail.com>
Date: Mon, 19 Feb 2024 15:40:19 +0100
Message-ID: <CAP9qbHWRSrOricmsNcP_yTXkM-ZE0v2SLekjSCWGOo7rrc2Phw@mail.gmail.com>
To: Orie Steele <orie@transmute.industries>
Cc: Darrel Miller <darrel@tavis.ca>, "httpapi@ietf.org" <httpapi@ietf.org>, Erik Wilde <erik.wilde@dret.net>, "eemeli@gmail.com" <eemeli@gmail.com>, "drafts-update-ref@iana.org" <drafts-update-ref@iana.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/eJH7CcuGCeME8NXFs51CcV3M5rk>
Subject: Re: [httpapi] RFC 9512 on YAML Media Type
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, 19 Feb 2024 14:40:37 -0000
Hi Orie. On Mon, 19 Feb 2024 at 15:11, Orie Steele <orie@transmute.industries> wrote: > Congratulations to all involved. Thanks :) > I've seen the structured suffix already being used here: > > https://www.w3.org/community/reports/json-ld/CG-FINAL-yaml-ld-20231206/#application-ld-yaml > Yes, the YAML-ld concept started under the IETF but was then delegated to the json-ld wg. > Not sure if I am interpreting the API media type comment correctly... Is there a plan to do > > application/schema+json We're working on it. See https://github.com/ietf-wg-httpapi/mediatypes/issues > application/schema+yaml While I think it's key, we should first finish schema+json > In a single document? Can you please clarify what does "single document" mean? A document should be either YAML or JSON. You can use YAML "flow collection style", in order to create JSON-like YAML. See https://www.rfc-editor.org/rfc/rfc9512.html#section-3.4 Still, the content will be either JSON or YAML. Thanks again for your kind words, R. > On Mon, Feb 19, 2024 at 3:35 AM Roberto Polli <robipolli@gmail.com> wrote: >> >> Hi Darrel + Rich, >> >> On Mon, 19 Feb 2024 at 04:48, Darrel Miller <darrel@tavis.ca> wrote: >> > Congratulations to Roberto, Erik and Eemeli on getting over the finish line with RFC 9512. It was great to see the deep thinking that went into getting this document as clear and as comprehensive as possible. I am confident that the time spent on getting this document right will save many people from frustration in the future. >> >> Thanks to you Rich and all the wonderful IETF, YAML, OAS and >> JSONSCHEMA communities that make it happen. >> >> The road to API mediatype standardization is still long, though :D >> >> Have a nice day, >> R. >> >> >> > ________________________________ >> > From: httpapi <httpapi-bounces@ietf.org> on behalf of rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org> >> > Sent: Wednesday, February 14, 2024 5:01 PM >> > To: ietf-announce@ietf.org <ietf-announce@ietf.org>; rfc-dist@rfc-editor.org <rfc-dist@rfc-editor.org> >> > Cc: rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org>; drafts-update-ref@iana.org <drafts-update-ref@iana.org>; httpapi@ietf.org <httpapi@ietf.org> >> > Subject: [httpapi] RFC 9512 on YAML Media Type >> > >> > A new Request for Comments is now available in online RFC libraries. >> > >> > >> > RFC 9512 >> > >> > Title: YAML Media Type >> > Author: R. Polli, >> > E. Wilde, >> > E. Aro >> > Status: Informational >> > Stream: IETF >> > Date: February 2024 >> > Mailbox: robipolli@gmail.com, >> > erik.wilde@dret.net, >> > eemeli@gmail.com >> > Pages: 13 >> > Updates/Obsoletes/SeeAlso: None >> > >> > I-D Tag: draft-ietf-httpapi-yaml-mediatypes-10.txt >> > >> > URL: https://www.rfc-editor.org/info/rfc9512 >> > >> > DOI: 10.17487/RFC9512 >> > >> > This document registers the application/yaml media type and the +yaml >> > structured syntax suffix with IANA. Both identify document >> > components that are serialized according to the YAML specification. >> > >> > This document is a product of the Building Blocks for HTTP APIs Working Group of the IETF. >> > >> > >> > INFORMATIONAL: This memo provides information for the Internet community. >> > It does not specify an Internet standard of any kind. Distribution of >> > this memo is unlimited. >> > >> > This announcement is sent to the IETF-Announce and rfc-dist lists. >> > To subscribe or unsubscribe, see >> > https://www.ietf.org/mailman/listinfo/ietf-announce >> > https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist >> > >> > For searching the RFC series, see https://www.rfc-editor.org/search >> > For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk >> > >> > Requests for special distribution should be addressed to either the >> > author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless >> > specifically noted otherwise on the RFC itself, all RFCs are for >> > unlimited distribution. >> > >> > >> > The RFC Editor Team >> > Association Management Solutions, LLC >> > >> > >> > -- >> > httpapi mailing list >> > httpapi@ietf.org >> > https://www.ietf.org/mailman/listinfo/httpapi >> >> -- >> httpapi mailing list >> httpapi@ietf.org >> https://www.ietf.org/mailman/listinfo/httpapi > > > > -- > > > ORIE STEELE > Chief Technology Officer > www.transmute.industries > >
- [httpapi] RFC 9512 on YAML Media Type rfc-editor
- Re: [httpapi] RFC 9512 on YAML Media Type Orie Steele
- Re: [httpapi] RFC 9512 on YAML Media Type Roberto Polli
- Re: [httpapi] RFC 9512 on YAML Media Type Darrel Miller
- Re: [httpapi] RFC 9512 on YAML Media Type Roberto Polli
- Re: [httpapi] RFC 9512 on YAML Media Type Orie Steele
- [httpapi] What is application/schema (was: Re: RF… Martin J. Dürst
- Re: [httpapi] What is application/schema (was: Re… Henry Andrews