Unverified50% confidenceFactExact time
In 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.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedYAML 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.76% similarUnverifiedIn 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.69% similarUnverifiedIn HTTP semantics, a missing field is not equivalent to an empty field, and many APIs perform strict validation on empty strings.59% similarUnverifiedConversational generation based on large language models is the latest evolutionary form of no-code, further eliminating the cognitive barrier of understanding platform logic and component relationships compared to traditional no-code approaches.56% similarUnverifiedYAML因语法简洁、支持注释、天然支持嵌套结构，成为存储接口测试数据的首选格式56% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1016894API
curl https://kongchang.com/api/v1/knowledge/claims/1016894MCP
get_claim(id=1016894)