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 Protobuf Schema is
A proto3 message definition with numbered fields.
gRPC services and anything using Protocol Buffers.
What changes when you convert Markdown to Protobuf Schema
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.
Field numbers are assigned in column order starting at one. Types are inferred from the values.
What carries over from Markdown to Protobuf Schema
Markdown records 2 things about a table that Protocol Buffers has no way to hold.
Protocol Buffers wants a type for each column, and Markdown does not record one, so each column is typed from what its values look like. A column of digits that should stay text - a zip code, a phone number, a leading-zero id - is the usual thing to check afterwards.
Protocol Buffers has no header row. The column names are repeated as keys on every record instead, which is why the result is bigger on disk than the table it came from.
Anything visual in the Markdown - weight, alignment, colour, column widths - has no counterpart in Protocol Buffers and is dropped. The values are what survives.