JSON Schema for YAML usage

[char0n]

Hi everybody,

I'd like to open discussion on clarifying the following OpenAPI excerpt (3.x.y):

In order to preserve the ability to round-trip between YAML and JSON formats, YAML version 1.2 is RECOMMENDED along with some additional constraints:
Tags MUST be limited to those allowed by the JSON Schema ruleset.
Keys used in YAML maps MUST be limited to a scalar string, as defined by the YAML Failsafe schema ruleset.

specifically

Tags MUST be limited to those allowed by the JSON Schema ruleset.
What does it actually mean, or rather what was intended by this sentence? Let me explain my question further...

---

1. we can say that this sentence means that tag resolution is driven by JSON Schema ruleset (and its extended list of regular expressions), it effectively means that following YAML is invalid:

openapi: 3.0.4

It can only be valid if we define it like this:

! openapi: ! 3.0.4
---
"openapi": "3.0.4"
---
'openapi': '3.0.4'
---
!!str openapi: !!str "3.0.4"
---

2. we can say that this sentence means that we can basically use any YAML Schema derived from JSON Shema ruleset (like Core) as long as the tag names are the same as in JSON Schema regardless of the resolution rules and extended list of regular expressions; which makes following valid YAML

openapi: 3.0.4

---

I'm assuming it was intended to target option 1.? As we probably want to retain all the info during the YAML/JSON round-trips (but I might be completely wrong)

key: FALSE

becomes

{"key": "FALSE"}

and not
{"key": false}

[char0n]

I've also opened a new issue with YAML spec itself, related to their examples for JSON Schema ruleset being misleading/wrong.