Re: [httpapi] RFC 9512 on YAML Media Type
Orie Steele <orie@transmute.industries> Mon, 19 February 2024 14:11 UTC
Return-Path: <orie@transmute.industries>
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 35610C14F6FF for <httpapi@ietfa.amsl.com>; Mon, 19 Feb 2024 06:11:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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=transmute.industries
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 qA9L3J-F2qC5 for <httpapi@ietfa.amsl.com>; Mon, 19 Feb 2024 06:11:30 -0800 (PST)
Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (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 D6C66C14F6B7 for <httpapi@ietf.org>; Mon, 19 Feb 2024 06:11:30 -0800 (PST)
Received: by mail-pj1-x1030.google.com with SMTP id 98e67ed59e1d1-29996cc6382so742490a91.3 for <httpapi@ietf.org>; Mon, 19 Feb 2024 06:11:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=transmute.industries; s=google; t=1708351890; x=1708956690; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=xCkiL4EQ+tQbisBEmjkYls7IJl3hfuGrSbe9CM1Fffw=; b=IGUX16IkVAWSXga4fFxG7AlZLAnqNiQcieTCBBFahguywDBIp6yW7NeYlb35z9G9fp er+oe71mcvliZyjjWOwrocbMNuprnjko/nMJ/nj/k0pzyLIqSRsOOOdZYGXaq4uLiLk+ DUkLXQf7RsKMHXqd9zybIni3LHjD9mg/3YpDoZhYWyW5XYE6PZd+hLr61TBr3qiFvQPk dJjWxXWMRESoXQ2EKLkNfO8axFfrmY55758N/G2OfH2dj6ebO3X4RaHprMHbdnE09woz eIBi4egfP15n5ujiK/CP0YcrDVGBYEeII5s4nWO53Pal1Si9balYRmqs/onRD4J1QsSJ a16A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708351890; x=1708956690; h=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=xCkiL4EQ+tQbisBEmjkYls7IJl3hfuGrSbe9CM1Fffw=; b=cwxo2Hriueh8xMetjwCjmkEnlQ4KhZNSaW3QkgoQamkt9SFkdHxO1b2p+5TFf2rwyN arLUqYrclSZO+uQaLcxb8KwRS1tv8bSqTpKvW6Xfm54tHm0nwSMLWuYuxGX/revM/pXQ MAR7YsJ3PIA/ZTjdI0Os55upMhdDmW96KxVb1HwwAXWPBwHc6hQKPYx2RhT3IOuaMXtK a9QOa2MEG7yXYuGAsfeCe50zSvoN/u3idQ7uhbbAI/ep6AMNKVz+LsUVmHTvvKnqIiKB gxYE5cIDRFC//shg78eo25v6e4jh/E/ZB+b8ETf/U6dof650w16axCc8+JpH1RoN5sD8 LYig==
X-Forwarded-Encrypted: i=1; AJvYcCW88hAMQEQKbzQj3vJpWkMkitSnZ/ortOi4GkhgO5G8qH+gpEBFntf9FM9WjdhCtlX+vIJygn6FvTT9pBuTD24I
X-Gm-Message-State: AOJu0YyHvWortTdyadN7kr+n+d2J94syW0/Dm9PZBQx2R3EcYtD63QwC D7jL2U0YTuitAiGUYQhHL4et3JYar+g+lkOmtB0Yaj+qbaH8jtW9kZwuNoT6eCSlr0Jcu3KVX5t Cm7Ls1KydBmPoV0KSejUj3vCZsqFLDijGDlxyXFdGEE2h/rszBIw=
X-Google-Smtp-Source: AGHT+IFbiGRl/gApP+O0N30qQRL3+E0wg0J4mR9j90fcft6qR1ZgCfBl1ssM9vicQug0toQh0FTyE8jBCaCVMW4VoqY=
X-Received: by 2002:a17:90a:dd41:b0:296:18cb:b717 with SMTP id u1-20020a17090add4100b0029618cbb717mr9368981pjv.25.1708351889743; Mon, 19 Feb 2024 06:11:29 -0800 (PST)
MIME-Version: 1.0
References: <20240214220104.2BF101957AE5@rfcpa.amsl.com> <SJ2PR01MB81022C5D9B3BA6FBB43A50D5A3512@SJ2PR01MB8102.prod.exchangelabs.com> <CAP9qbHVZNtM3W36CqD6PVx_BKkVhQCvsy9D7n1GeOxJUgho-jQ@mail.gmail.com>
In-Reply-To: <CAP9qbHVZNtM3W36CqD6PVx_BKkVhQCvsy9D7n1GeOxJUgho-jQ@mail.gmail.com>
From: Orie Steele <orie@transmute.industries>
Date: Mon, 19 Feb 2024 08:11:18 -0600
Message-ID: <CAN8C-_K5HvG5TfbzmU6PsucbpfQyX=TwbX41n-nJiC5pyGQm6w@mail.gmail.com>
To: Roberto Polli <robipolli@gmail.com>
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: multipart/alternative; boundary="0000000000008a39980611bcab9c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/vTxhk1h1IKGOb5naGTT7uRx5XBw>
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:11:35 -0000
Congratulations to all involved. 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 Not sure if I am interpreting the API media type comment correctly... Is there a plan to do application/schema+json application/schema+yaml In a single document? Regards, OS 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 <https://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