# What should we promote as the "generic" term for Markdown/CommonMark-like markup languages?

**URL:** <https://talk.commonmark.org/t/what-should-we-promote-as-the-generic-term-for-markdown-commonmark-like-markup-languages/647>\
**Category:** Uncategorized\
**Created:** [September 19, 2014, 10:20pm UTC](https://talk.commonmark.org/t/what-should-we-promote-as-the-generic-term-for-markdown-commonmark-like-markup-languages/647 "2014-09-19T22:20:25Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![BatmanAoD](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/batmanaod/32/422_2.png) [@BatmanAoD](https://talk.commonmark.org/u/BatmanAoD)\
**Post date:** [September 19, 2014, 10:20pm UTC](https://talk.commonmark.org/t/what-should-we-promote-as-the-generic-term-for-markdown-commonmark-like-markup-languages/647/1 "2014-09-19T22:20:25Z")

</div>

I suspect this might have already been brought up somewhere, but I can’t find any threads that seem to be related, so I’m posting a new topic.

Is there a good term to use that means “simple markup language for formatting text, a la Markdown”? I.e., a term that encompasses _all_ similar markup languages? For example, if we had a term (let’s say it’s “SML” for “simple markup language”), we could say “Markdown is one of the earliest SMLs; CommonMark is a standardized and extensible SML based on Markdown.”

The word “markdown” (without the uppercase “M”) seems like it could be used in such a way; the relationship to the generic term “markup” is intuitive and self-descriptive, and I suspect there are people who already use the term in this way. Gruber, however, has made it clear that he thinks of “Markdown” as something that, in some sense, _belongs to_ him. But he also seems to be okay with the existence of “flavors” of Markdown (such as Github-flavored Markdown) that don’t actually fit his original spec, which would seem to imply that markdown _is_ a more “generic” term than it would seem at first.

One other drawback of the term “markdown” is that googling it leads to…well, Markdown, rather than an explanation of SMLs (let alone CommonMark). This is, of course, a fairly biased reason not to use the term, though.

In any case, I don’t think there’s necessarily a “right” answer to this question; I do, however, think that such a term would be a useful piece of vocab, and I think that as a community working together to create a spec for a SML that (IMO) has a good chance of becoming one of the most widely-used SMLs (if not _the_ most widely-used), we have a prime opportunity to choose a particular term to use and promote.

I can’t think of any good alternatives to “markdown,” so I’ll just spitball some bad ones to get the ball rolling:

- textmark (note that “TextMarks” is an unrelated SMS product, though…)
- marktext (because it’s “markup” text that looks like _text_)
- textup (same idea)
- SML (pronounced “simul”) (yes, it’s terrible and I hate it)
- BML (pronounced “bimul”; the B is for “basic”)
- simplemark (sounds too much like yet another M\*\*\*\*\*\*…)
- cleantext (because the text looks “clean” regardless of whether it’s rendered or in text-only form; also sounds a bit like “cleartext,” which is possibly a good thing because that is, in some ways, an analogous concept)
- easytext, easymark… these all sound too much like brand-names to me…

---

<div class="post-metadata">

**Author:** ![BatmanAoD](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/batmanaod/32/422_2.png) [@BatmanAoD](https://talk.commonmark.org/u/BatmanAoD)\
**Post date:** [September 19, 2014, 11:21pm UTC](https://talk.commonmark.org/t/what-should-we-promote-as-the-generic-term-for-markdown-commonmark-like-markup-languages/647/2 "2014-09-19T23:21:38Z")

</div>

This term would be helpful for writing a [philosophy statement](http://talk.commonmark.org/t/commonmark-should-have-a-philosophy/613?u=batmanaod).

Some more suggestions:

- quickmark
- genmark (for “generic markup (or down)”)
- GML (for “generic markup language”)

---

<div class="post-metadata">

**Author:** ![chrisalley](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/chrisalley/32/906_2.png) [@chrisalley](https://talk.commonmark.org/u/chrisalley)\
**Post date:** [September 20, 2014, 4:19am UTC](https://talk.commonmark.org/t/what-should-we-promote-as-the-generic-term-for-markdown-commonmark-like-markup-languages/647/3 "2014-09-20T04:19:17Z")

</div>

“Lightweight Markup Language”

---

<div class="post-metadata">

**Author:** ![mofosyne](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/mofosyne/32/1438_2.png) [@mofosyne](https://talk.commonmark.org/u/mofosyne)\
**Post date:** [September 20, 2014, 4:40am UTC](https://talk.commonmark.org/t/what-should-we-promote-as-the-generic-term-for-markdown-commonmark-like-markup-languages/647/4 "2014-09-20T04:40:39Z")

</div>

Could be “LiteMarkup” as shorthand for “Lightweight Markup Language”

---

<div class="post-metadata">

**Author:** ![Burt\_Harris](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/burt_harris/32/368_2.png) [@Burt\_Harris](https://talk.commonmark.org/u/Burt_Harris)\
**Post date:** [September 20, 2014, 5:00am UTC](https://talk.commonmark.org/t/what-should-we-promote-as-the-generic-term-for-markdown-commonmark-like-markup-languages/647/5 "2014-09-20T05:00:43Z")

</div>

> [@chrisalley](#):
>
> “Lightweight Markup Language”

Seconded. It already has a [Wikipedia entry](http://en.wikipedia.org/wiki/Lightweight_markup_language), so why make up new terminology.

---

<div class="post-metadata">

**Author:** ![seantek](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/seantek/32/364_2.png) [@seantek](https://talk.commonmark.org/u/seantek)\
**Post date:** [September 20, 2014, 8:50pm UTC](https://talk.commonmark.org/t/what-should-we-promote-as-the-generic-term-for-markdown-commonmark-like-markup-languages/647/6 "2014-09-20T20:50:56Z")

</div>

Yes, _lightweight markup language_.

That is the term used in [The text/markdown Media Type](https://tools.ietf.org/html/draft-ietf-appsawg-text-markdown) Internet-Draft as well.

---

<div class="post-metadata">

**Author:** ![bowerbird](https://cdn.commonmark.org/letter_avatar_proxy/v2/letter/b/ba8739/32.png) [@bowerbird](https://talk.commonmark.org/u/bowerbird)\
**Post date:** [September 23, 2014, 10:48pm UTC](https://talk.commonmark.org/t/what-should-we-promote-as-the-generic-term-for-markdown-commonmark-like-markup-languages/647/7 "2014-09-23T22:48:08Z")

</div>

there already is a generic term – “light-markup”.

(some, like wikipedia, use “lightweight”, but that  
implies that it’s deficient, incomplete, or lacking,  
which is true of _some_ variants, but not others.)

another generic, coined by one of the pioneers,  
dean allen, who did textile, is “humane markup”.

textile was the light-markup in “movable type”,  
the early blogging system that john gruber used,  
so gruber actually “borrowed” the idea from allen,  
a little nugget that he’s only rarely acknowledged.

to gruber’s credit, however, he gave _his_ version  
a new name, and thus deserves full kudos for the  
popularity that markdown has received ever since.

restructured-text is also another light-markup, and  
another one that was conceived before markdown.  
it’s been used as the official format for python docs  
since its beginning, and has served the purpose well,  
which indicates that it doesn’t have the deficiencies  
and fragmentation which markdown has suffered, so  
one wonders why it hasn’t gotten too much attention.

there is also asciidoc, which is far more widely used  
than people might suppose, given its fairly low profile;  
although it is rather _heavy_ for a “light” markup, it is  
also impressively complete, and has working versions  
of cross-platform converters to several output formats.

-bowerbird

---

<div class="post-metadata">

**Author:** ![JMelton](https://cdn.commonmark.org/letter_avatar_proxy/v2/letter/j/5fc32e/32.png) [@JMelton](https://talk.commonmark.org/u/JMelton)\
**Post date:** [September 25, 2014, 1:29pm UTC](https://talk.commonmark.org/t/what-should-we-promote-as-the-generic-term-for-markdown-commonmark-like-markup-languages/647/8 "2014-09-25T13:29:04Z")

</div>

I like Lightweight Markup Language or LML (lem-el)

Disagree that _lightweight_ in any way implies deficient or incomplete.

---

<div class="post-metadata">

**Author:** ![bowerbird](https://cdn.commonmark.org/letter_avatar_proxy/v2/letter/b/ba8739/32.png) [@bowerbird](https://talk.commonmark.org/u/bowerbird)\
**Post date:** [September 25, 2014, 3:27pm UTC](https://talk.commonmark.org/t/what-should-we-promote-as-the-generic-term-for-markdown-commonmark-like-markup-languages/647/9 "2014-09-25T15:27:12Z")

</div>

> Disagree that lightweight in any way  
> implies deficient or incomplete.

disagree all you like. :+)

but if the lightweight boxing champ  
fought the heavyweight champion,  
i don’t know which one would _win_,  
but i know which one i’d _bet_ on…

“light”, on the other hand, is often  
juxtaposed favorably with “heavy”,  
especially given the context of tech,  
where this year’s iphone is almost  
always more light (and less heavy)  
than last year’s, thanks very much.

-bowerbird

---

<div class="post-metadata">

**Author:** ![mcwumbly](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/mcwumbly/32/100_2.png) [@mcwumbly](https://talk.commonmark.org/u/mcwumbly)\
**Post date:** [September 25, 2014, 3:39pm UTC](https://talk.commonmark.org/t/what-should-we-promote-as-the-generic-term-for-markdown-commonmark-like-markup-languages/647/10 "2014-09-25T15:39:28Z")

</div>

I would interpret “markdown” (little m) as being applicable as a generic category for all the various flavors of… markdown (not sure how to avoid the circular reference).

Whereas light-markup is a somewhat broader category.
