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 AsciiDoc is
AsciiDoc tables are delimited by |=== and take a cols attribute describing the columns.
Antora documentation sites, and technical writing teams that outgrew Markdown.
What changes when you convert YAML to AsciiDoc
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.
The header option is set so the first row renders as a header row rather than data.
What carries over from YAML to AsciiDoc
YAML records 2 things about a table that AsciiDoc has no way to hold.
YAML distinguishes a number from the text of a number; AsciiDoc 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 AsciiDoc, so a null and an empty string in the YAML both come out blank and can no longer be told apart.
AsciiDoc 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 AsciiDoc 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 AsciiDoc file goes wrong.
The quotes around Jonah "Jo" Pryce are left as a plain quote character in the AsciiDoc.