Unverified50% confidenceFactExact time
YAML 1.1 (released in 2005) treats bare words such as y/n, yes/no, on/off, true/false as booleans, and supports implicit types such as octal, underscore thousands separators, and sexagesimal time; YAML 1.2 (2009) keeps only true/false as boolean literals, and on/off/yes/no return to being ordinary strings.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedIn YAML 1.1, version-number strings such as '10.23' are parsed as floats rather than strings, which may break logic that compares versions as text.76% similarUnverifiedIn YAML 1.1, bare no, yes, on, and off are parsed as booleans rather than strings, causing the Norway problem; for example, 'no' in a list of country codes is silently parsed as false.76% similarUnverifiedYAML因语法简洁、支持注释、天然支持嵌套结构，成为存储接口测试数据的首选格式67% similarUnverifiedyaml-cpp 允许开发者通过特化 YAML::convert<T> 模板，实现 encode 和 decode 静态方法完成自定义类型双向转换63% similarVerifiedYAML has become the de facto standard configuration language in the DevOps domain and is widely adopted by Kubernetes, Ansible, and GitHub Actions.61% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1016902API
curl https://kongchang.com/api/v1/knowledge/claims/1016902MCP
get_claim(id=1016902)