so

Markup Standards

Volume 9, Issue 20; 29 Sep 2025

Introducing a curated, crowd-sourced (that’s you) list of markup-related standards.

What happened was, following some discussion of community outreach on the MarkupDeclaration Discord server and elsewhere, Liam Quin suggested on the XML.com Slack that we try posting markup-related things on social media on Mondays tagged #MarkupMonday.

Trouble is, I am absolutely awful at thinking of things to write about on command. So I don’t know how successful I’ll be at this over the long term. But it did occur to me last night that I had something I could write about today.

As it happens, and at least tangentially related to outreach, I recently started building a list of markup-related standards. I did this partly so that they’d be easier for me to find, but also partly so that someone interested in markup would see the breadth and depth of markup-related work. I’m taking “markup” as broadly as possible here: XML, JSON, Markdown, YAML, etc. It’s all markup.

You can find its nascent incarnation on MarkupStandards.org.

It is, as it says at the top of the page, an incomplete and idiosyncratic list. Pointers to markup-related standards that I’ve (accidentally, I swear!) overlooked, most welcome. Also suggestions for new, markup-related categories most welcome.

Keep on tagging!

#MarkupMonday

Please provide your name and email address. Your email address will not be displayed and I won’t spam you, I promise. Your name and a link to your web address, if you provide one, will be displayed.

Your name:

Your email:

Homepage:

Do you comprehend the words on this page? (Please demonstrate that you aren't a mindless, screen-scraping robot.)

What is six minus three?   (e.g. six plus two is 8)

Enter your comment in the box below. You may style your comment with the CommonMark flavor of Markdown.

All comments are moderated. I don’t promise to preserve all of your formatting and I reserve the right to remove comments for any reason.