Original text:
to be interpreted as in URI. The terms "node", "alias node", "anchor" and "named anchor" in this <del> document are to be intepreded as in YAML. </del>  1.2. and 7.1 of YAML) as fragment identifiers to designate nodes. A YAML alias node can be represented in a URI fragment identifier by <del> encoding it into octects using UTF-8 UTF-8, while percent-encoding </del>  those characters not allowed by the fragment rule in Section 3.5 of URI. yaml <del> None </del>  <del> None; unrecognized parameters should be ignored </del>  binary <del> HTTP </del>  An empty fragment identifier references the root node.  A fragment identifier starting with "*" is to be interpreted as a YAML alias Deprecated alias names for this type: application/x-yaml, text/ yaml, text/x-yaml <del> Magic number(s) n/a </del>  File extension(s): yaml, yml <del> Macintosh file type code(s): n/a </del>  See Authors' Addresses section. See Authors' Addresses section. <del> n/a </del>  2.2. See <del> See Authors' Addresses section. </del>  See Authors' Addresses section <del> n/a </del>  3. considerations apply. When using YAML as a more efficient format to serialize information <del> intented to be consumed as JSON, information can be discarded: this </del>  includes comments (see Section 3.2.3.3 of YAML) and alias nodes (see Section 7.1 of YAML), that do not have a JSON counterpart. identifiers.  This is to improve the interoperability of already consolidated practices, such as the one of writing OAS in YAML. <del> ex-fragid provides a non exhaustive list of examples that could help understanding interoperability issues related to fragment identifiers. </del>  4.

Reviewer comments:
Fix typical media type template problems Typos
In general, LGTM. About change controller, I was waiting for the feedback from the media type mailing list.

Revised text:
to be interpreted as in URI. The terms "node", "alias node", "anchor" and "named anchor" in this  <ins> document are to be interpreted as in YAML. </ins> 1.2. and 7.1 of YAML) as fragment identifiers to designate nodes. A YAML alias node can be represented in a URI fragment identifier by  <ins> encoding it into bytes using UTF-8 UTF-8, while percent-encoding </ins> those characters not allowed by the fragment rule in Section 3.5 of URI. yaml  <ins> N/A </ins>  <ins> N/A; unrecognized parameters should be ignored </ins> binary  <ins> Applications that need a human-friendly, cross language, Unicode based data serialization language designed around the common native data types of dynamic programming languages. </ins> An empty fragment identifier references the root node.  A fragment identifier starting with "*" is to be interpreted as a YAML alias Deprecated alias names for this type: application/x-yaml, text/ yaml, text/x-yaml  <ins> Magic number(s) N/A </ins> File extension(s): yaml, yml  <ins> Macintosh file type code(s): N/A </ins> See Authors' Addresses section. See Authors' Addresses section.  <ins> IESG </ins> 2.2. See  <ins> httpapi@ietf.org or art@ietf.org </ins> See Authors' Addresses section  <ins> IESG </ins> 3. considerations apply. When using YAML as a more efficient format to serialize information  <ins> intended to be consumed as JSON, information can be discarded: this </ins> includes comments (see Section 3.2.3.3 of YAML) and alias nodes (see Section 7.1 of YAML), that do not have a JSON counterpart. identifiers.  This is to improve the interoperability of already consolidated practices, such as the one of writing OAS in YAML.  <ins> ex-fragid provides a non-exhaustive list of examples that could help understand interoperability issues related to fragment identifiers. </ins> 4.