Please read the rest
"

o Each encompassed language's subtag SHOULD be used as the primary
language subtag. For example, a document in Mandarin Chinese
would be tagged "cmn" (the subtag for Mandarin Chinese) in
preference to "zh" (Chinese).

o If compatibility is desired or needed, the encompassed subtag MAY
be used as an extended language subtag. For example, a document
in Mandarin Chinese could be tagged "zh-cmn" instead of either
"cmn" or "zh".
"
"

As noted above, applications can choose to use the macrolanguage
subtag to form the tag instead of using the more specific encompassed
language subtag. For example, an application with large quantities
of data already using tags with the 'zh' (Chinese) subtag might
continue to use this more general subtag even for new data, even
though the content could be more precisely tagged with 'cmn'
(Mandarin), 'yue' (Cantonese), 'wuu' (Wu), and so on. Similarly, an
application already using tags that start with the 'ar' (Arabic)
subtag might continue to use this more general subtag even for new
data, which could be more precisely tagged with 'arb' (Standard
Arabic).
"

`Prefix` is a "SHOULD", not a "MUST". When there are multiple encompassed language as seen here, using the encompassed language is clearer. OSM is also starting fresh for scripts, not burdened by any compatibility which only existed as non-compliant `name:zh_pinyin` .

I don't see what's your argument for the situation in HK and Macau. I didn't talk about `zh-HK` either.
`zh` means Standard Written Chinese or Cantonese in OSM here. We already have enough work with `name=` , `name:en=`, and `name:zh=` . Then people like to add `name:yue=` further because they think `name:zh=` means Mandarin, which is worsened by iD.

That being said, I believe if more subtags from `*-Latn` to `*-Latn-pinyin` is specified, using `cmn` would be wise anyway. `zh` is only needed for compatibility at a simple level.

For reference "Each encompassed language's subtag SHOULD be used as the primary language subtag. For example, a document in Mandarin Chinese would be tagged "cmn" (the subtag for Mandarin Chinese) in preference to "zh" (Chinese)." https://www.ietf.org/rfc/bcp/bcp47.html#section-4.1.2
I don't oppose using `zh` for PRC and Taiwan. But this would be different in HK and Macau.

Also I still don't see your wiki page?

`zh` would mean Cantonese or Standard Written Chinese in Hong Kong. It's not reliably treated as Mandarin.

Can you please discuss this first, as you have been warned before? HK has `yue` which makes `zh` unclear.

@InsertUser I thought I want to see if DWG has anything to say in the other edit. Also, at least one expressed support over `=classroom` itself osm.wiki/Talk:Key:room#Classrooms

I don't see any update on previous changeset/157698378

Don't use `=permissive` . That means allowed. It's `=private` .

Besides, another requirement is you need to create a wiki page to document this editing. On a minor note, it doesn't help that Telegram is a limited visibility service that others can't see the whole conservation publicly without joining.

You are making a worldwide change, not in those countries only. The language doesn't mean you only need to discuss with countries using it as the native language. For one thing, there are speakers around the world as well.
Let me give a simple example of a problem. It seems `description:*=` only refers to the script, not any differences between the 2 countries. Then `description:zh-TW` etc should rather be changed to `description:zh-Hant=` etc. An exception would be those `=monitoring_station` that actually use different words "空气质量" and "空氣品質" in them.

Others ref changeset/157698378
https://github.com/openstreetmap/id-tagging-schema/pull/1355

(sorry I overlooked. I see it's already known.)

@woodpeck For easy reference, the user committeed another undiscussed mass retagged internationally after editing wiki changeset/157697294
changeset/157697989
changeset/157687202

As linked, you have to discuss it visibly on the official services beforehand for some days before editing, among other requirements. You haven't even obtained consensus in those pr.

Where was this discussed? `=class` is still more numerous, and listed for OpenIndoor. osm.wiki/OpenIndoor#Rooms
There are other problems with `room=` eg `=toilet` vs `=toilets` osm.wiki/Talk:Key:room#Avoid_room=toilets (also how to distinguish open stalls with partitions vs actual room-like stalls with walls)
The other major issue is `room=` `=shop` , `=restaurant` , `=reception` could be used to show the main `=room` . That's not covered by `amenity=` room=*#Avoid_these_values
Actually you have uniliaterally discouraged it? osm.wiki/w/index.php?title=Key:room&type=revision&diff=2711907&oldid=2621100

Still waiting for your reply if you have the leisure of stalking and harasssing others with irrelevant comments to a changeset changeset/144534922

Please don't make meaningless edits to bump. This has no effect. Carto is a static raster style. Long labels can be unable to be rendered. Furthermore, Standard Tile only has z=19 zoom.