New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RFC 9512: YAML Media Type #7027

Open

simon04 wants to merge 1 commit into google:master from simon04:yaml

Contributor

simon04 commented Feb 21, 2024

https://www.rfc-editor.org/rfc/rfc9512.html


          RFC 9512: YAML Media Type

f21f3d0

https://www.rfc-editor.org/rfc/rfc9512.html

kalebers approved these changes

View reviewed changes

Member

cpovirk commented Feb 26, 2024

Thanks. Do you know where I might learn more about the charset parameter? In https://www.iana.org/assignments/media-types/application/yaml, I see "Optional parameters: N/A; unrecognized parameters should be ignored." That's not as strong as https://www.iana.org/assignments/media-types/application/json, which has a Note that "No 'charset' parameter is defined for this registration." (But see #6901 (comment) for more on that :)) But it's still a contrast to https://www.iana.org/assignments/media-types/application/xml, which lists charset explicitly and links to the relevant RFC, which also mentions it. (RFC 9512 mentions support for non-UTF-8 charsets as a difference between JSON (no) and YAML (yes); https://yaml.org/spec/1.2.2/ likewise mentions other encodings. Neither appears to speak directly to charset.)

cpovirk added type=enhancement package=net P3 labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

P3 package=net type=enhancement