What Markdown is
A Markdown table is rows of pipe-separated cells with a dashed rule under the header. Alignment is set by placing colons in that rule.
README files, GitHub issues, documentation sites, Obsidian and Notion.
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 Markdown to AsciiDoc
Leading and trailing pipes are optional and both are handled. A pipe the author escaped with a backslash is read as data rather than a column break, which is the usual reason a hand-written table parses one column too wide.
The header option is set so the first row renders as a header row rather than data.
What carries over from Markdown to AsciiDoc
AsciiDoc can express everything Markdown holds about a table, so this conversion is about shape rather than loss.
Markdown and AsciiDoc can express the same things about a table, so nothing is lost here - only rewritten. A pipe table is one row per line, so a line break inside a cell ends the row early. Cells are introduced by a pipe and may carry their own formatting or another table.
That makes this a change of notation rather than of content: the same values, the same columns, the same order, written with the markers AsciiDoc expects instead of the ones Markdown uses.
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.