What YAML is
YAML uses indentation instead of brackets. It is a superset of JSON, supports comments, and is meant to be edited by hand.
Kubernetes manifests, CI pipelines, Ansible playbooks and most modern config files.
What Qlik is
A Qlik load script block using LOAD INLINE, which embeds the data in the script itself.
QlikView and Qlik Sense developers.
What changes when you convert YAML to Qlik
A YAML list of maps reads as rows and columns directly. Anchors and aliases are resolved before the table is built, so a repeated block arrives expanded rather than as a reference.
Suitable for small reference tables. For anything large, load from a file instead.
What carries over from YAML to Qlik
YAML records 4 things about a table that Qlik has no way to hold.
YAML distinguishes a number from the text of a number; Qlik does not, so every value arrives as text and has to be re-parsed by whatever reads it next.
An empty cell and a missing one are the same thing in Qlik, so a null and an empty string in the YAML both come out blank and can no longer be told apart.
YAML can hold a value that is itself a list or an object. Qlik has only flat cells, so nested values are flattened into one cell rather than being spread across columns.
A line break inside a cell ends the row in Qlik, so line breaks are replaced rather than carried through.
Qlik marks header cells differently from data cells, so the keys are lifted out and written once as a marked header row rather than repeated on every row.
The identifier 007 comes out of the Qlik as 007. Reading it as a number would have made it 7, and an id that changes value is worse than one that stays text.
The role "Analyst, data" survives with its comma, in one cell rather than split across two. That is the first thing to check in any converted table, and the usual place a Qlik file goes wrong.
The quotes around Jonah "Jo" Pryce are left as a plain quote character in the Qlik.