Re: [httpapi] [media-types] YAML media type: requesting early review after WGLC
Roberto Polli <robipolli@gmail.com> Tue, 18 October 2022 09:07 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 70B7FC14F72B; Tue, 18 Oct 2022 02:07:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_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 zf96Hnw2ywhL; Tue, 18 Oct 2022 02:07:00 -0700 (PDT)
Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) (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 A16C4C14F722; Tue, 18 Oct 2022 02:07:00 -0700 (PDT)
Received: by mail-ej1-x629.google.com with SMTP id fy4so30601125ejc.5; Tue, 18 Oct 2022 02:07:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; 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=j42oGeJE+UKB8FhW+OoijvATLkWvMHHiCTTDhI6lJTA=; b=lNY6Til0Hi++n2c/Ksn+C1nJUgK2uTBe5rl2vq+QJM1jKRSlOGgPtG0/A/i0kC0LtV 0cJ/kuqymbtEqlhJHUk/TOQ7zNf9dOcErdiG45kM0v9mW3rvVfv6jVJfdcjApg8LImxu IxDk+uEPW5CMOhv+PjWT/WtYs46OdB57A3dbsb9DcDYTF4HwtxAoNKUIyhSJCinVto7X 0Bzg7sUaxIArLYmviRLqdu/rynjxsbglMdbLhivXj8qo2pH+cysob9BfMuV4diGTjk/J 8S+KUXcGVNnYTDzsMFzAL52NT1qWgh3dis8e8CdZf6ycTqrbA4SkFf8C6/pnyZ539seG qykg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=j42oGeJE+UKB8FhW+OoijvATLkWvMHHiCTTDhI6lJTA=; b=3zLei8i+hnhCABuEPoKPo6mf0f0oieXC1DONZ8QS2B7DOdoGgCN+6Fzus1+kLp9NaT Xz7rY7AWgGp+aJloo9+gnyyF7q5suCqZ53hJeONgnjnlbTc6O4g3ymra7PYosTIdvMGi dhV4ltYIXnUtOthAqfyjJ0z4AaVN89xyd46BoD833CS2FES34aq3pm9CZkhGJaBQkRKt jMimnnWExXY7jiNdQM3o0lu908O/VZnwNsWTaiCCwa0mcHDD0RUVNZKu3a8SXy/fTSNV OZjVNvYbm+5etBdCGjBsiFKUduFWjZXJ9tQ3tGOjj+e0KUJp7YOZ98n1bqdlbH7NmBWH ew9A==
X-Gm-Message-State: ACrzQf30ryc09t1liVEoT9mB9OC5OP1XGiIHrmWinGdD6+kIAJB8O6R5 I62FKNxBbPzrwAJ3bReg2QMlg79EgNEfDTwjQIw=
X-Google-Smtp-Source: AMsMyM4TJEbS5hFqi7RCTIGYFQxkOm+yD22bjIyqPiETokpIGtTrlDMZ9Bh41WVrbh0AtKbyU0lYq8CDiBIve6fJpWQ=
X-Received: by 2002:a17:907:2721:b0:78d:4e30:df36 with SMTP id d1-20020a170907272100b0078d4e30df36mr1561102ejl.508.1666084018792; Tue, 18 Oct 2022 02:06:58 -0700 (PDT)
MIME-Version: 1.0
References: <CAP9qbHWLkKak6LuDVZHusFCwRpTGH0tgvuqkTSQsh=mAshMg8Q@mail.gmail.com> <CAP9qbHXOVrRRt65fxn_XB38GeaYWMfarGKxd_bCqCFA+vV8S-g@mail.gmail.com> <5CD489D3-7615-4E42-87DE-330E1CEABAE9@hoplahup.net>
In-Reply-To: <5CD489D3-7615-4E42-87DE-330E1CEABAE9@hoplahup.net>
From: Roberto Polli <robipolli@gmail.com>
Date: Tue, 18 Oct 2022 11:06:47 +0200
Message-ID: <CAP9qbHUG6QFupuM4JY0vX2RTJ2mt8uL3P776pm7bMFECfh4aKQ@mail.gmail.com>
To: Paul Libbrecht <paul@hoplahup.net>
Cc: media-types@ietf.org, httpapi@ietf.org, Erik Wilde <erik.wilde@dret.net>, eemeli@gmail.com, duerst@it.aoyama.ac.jp
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/fTf2x9nDtDU0CQfvTl6hRFRMd2o>
Subject: Re: [httpapi] [media-types] YAML media type: requesting early review after WGLC
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, 18 Oct 2022 09:07:04 -0000
Hi Paul, thanks for your email! On Thu, 6 Oct 2022 at 22:28, Paul Libbrecht <paul@hoplahup.net> wrote: > I am supposing that YAML content is likely to be exchanged among editors > using a copy-and-paste exchange mechanism. Yes. > If this is the case, I would like to suggest to add uniform type identifiers > and windows clipboard names so that future implementations may take part to such an exchange > in the Additional Information section. Tracked https://github.com/ietf-wg-httpapi/mediatypes/issues/66 I didn't know UTIs and Windows clipboard names: can you reference any example in IANA registration form? Is it ok for you to continue the discussion on the github issue? Have a nice day, R. > > Thanks in advance. > > Paul > > PS: this might even include web-pages-included editors (an API is arriving). > > On 6 Oct 2022, at 10:31, Roberto Polli wrote: > > Dear media types folks, > > as suggested by Martin Duerst I hereby provide a summary of the media type and structured syntax suffix registrations. > Thanks again and have a nice day, > R. > > 2.1. Media Type application/yaml > > The media type for YAML text is application/yaml; the following information serves as the registration form for this media type. > > Type name: > > application > > Subtype name: > > yaml > > Required parameters: > > N/A > > Optional parameters: > > N/A; unrecognized parameters should be ignored > > Encoding considerations: > > binary > > Security considerations: > > see Section 4 of this document > > Interoperability considerations: > > see Section 3 of this document > > Published specification: > > [YAML] > > Applications that use this media type: > > Applications that need a human-friendly, cross language, Unicode based data serialization language designed around the common native data types of dynamic programming languages. > > Fragment identifier considerations: > > See Section 1.2 > > Additional information: > > Deprecated alias names for this type: application/x-yaml, text/yaml, text/x-yaml > Magic number(s) N/A > File extension(s): yaml, yml > Macintosh file type code(s): N/A > > Person and email address to contact for further information: > > See Authors' Addresses section. > > Intended usage: > > COMMON > > Restrictions on usage: > > None. > > Author: > > See Authors' Addresses section. > > Change controller: > > IESG > > 2.2. The +yaml Structured Syntax Suffix > > The suffix +yaml MAY be used with any media type whose representation follows that established for application/yaml. The media type structured syntax suffix registration form follows. See [MEDIATYPE] for definitions of each of the registration form headings. > > Name: > > YAML Ain't Markup Language (YAML) > > +suffix: > > +yaml > > References: > > [YAML] > > Encoding considerations: > > see Section 2.1 > > Fragment identifier considerations: > > Differently from application/yaml, there is no fragment identification syntax defined for +yaml. > > A specific xxx/yyy+yaml media type needs to define the syntax and semantics for fragment identifiers because the ones in Section 2.1 do not apply unless explicitly expressed. > > Interoperability considerations: > > See Section 2.1 > > Security considerations: > > See Section 2.1 > > Contact: > > httpapi@ietf.org or art@ietf.org > > Author: > > See Authors' Addresses section > > Change controller: > > IESG > > > On Tue, 4 Oct 2022 at 17:25, Roberto Polli <robipolli@gmail.com> wrote: >> >> Dear media types folks, >> >> in the HTTPAPI WG are closing the WGLC for YAML media type. >> The latest I-D is here: >> >> - https://www.ietf.org/archive/id/draft-ietf-httpapi-yaml-mediatypes-03.html >> >> We'd be grateful if you could provide an early review, so that we can move forward. >> The publication of this document will allow the registration of xxx+yaml media >> types, such as: >> >> - openapi+yaml which will follow up in the HTTPAPI WG; >> - ld+yaml which is taking place under the W3C. >> >> Thanks for all the support you can provide, >> and have a nice day, >> Roberto & the editors > > _______________________________________________ > media-types mailing list > media-types@ietf.org > > https://www.ietf.org/mailman/listinfo/media-types
- [httpapi] YAML media type: requesting early revie… Roberto Polli
- Re: [httpapi] YAML media type: requesting early r… Roberto Polli
- Re: [httpapi] YAML media type: requesting early r… Alexey Melnikov
- Re: [httpapi] [media-types] YAML media type: requ… Paul Libbrecht
- Re: [httpapi] [media-types] YAML media type: requ… Roberto Polli
- Re: [httpapi] YAML media type: requesting early r… Roberto Polli
- Re: [httpapi] [media-types] YAML media type: requ… Manu Sporny
- Re: [httpapi] [media-types] YAML media type: requ… Manu Sporny
- Re: [httpapi] [media-types] YAML media type: requ… Roberto Polli