Why YAML rejects the “markup” label
YAML’s name is a recursive acronym: “YAML Ain’t Markup Language.” A recursive acronym includes its own name in its expansion, so the phrase loops back on itself. The joke also points to a real distinction in how YAML is meant to be used: it describes data, rather than adding display instructions to a document.
Structure, not presentation
A markup language typically marks up text to describe how parts should be interpreted or presented. YAML instead organizes values into a readable structure. A configuration file, for example, might record a service’s name, whether a setting is enabled, and a list of server addresses. Indentation and punctuation show which values belong together; the file is not primarily telling a browser how to format a paragraph.
That makes YAML useful for settings humans need to read and edit while software needs to parse. The same text can express nested relationships—such as a list of items inside a larger set of options—without requiring the writer to add presentation tags around each piece.
A name with a technical point
The acronym is playful, but it draws a boundary around YAML’s purpose. Its structure is there to make data legible and organized, not to decorate prose. When someone opens a YAML file, they are usually looking at instructions or information an application will consume, even if the file reads almost like a short outline.
