# Commonmark document specification (For desktop readers) **URL:** \ **Category:** Extensions\ **Created:** [December 12, 2014, 3:24am UTC](https://talk.commonmark.org/t/commonmark-document-specification-for-desktop-readers/956 "2014-12-12T03:24:15Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![mofosyne](https://talk.commonmark.org/user_avatar/talk.commonmark.org/mofosyne/32/1438_2.png) [@mofosyne](https://talk.commonmark.org/u/mofosyne)\ **Post date:** [December 12, 2014, 5:11am UTC](https://talk.commonmark.org/t/commonmark-document-specification-for-desktop-readers/956/2 "2014-12-12T05:11:59Z")
> [@Support for \ and/or \](https://talk.commonmark.org/t/support-for-link-and-or-head/941/17): > > Before getting caught up on details, it would be worth coming up with some use cases for a container specification to give it some real world context and scope. Perhaps another topic should be started for brainstorming this. ##`.md` **scope: simple no frill container of text with simple markups** - Simple documentation - Simple Resumes - Application specific files - Internal text (e.g. text in a game) - Wiki (backups of wikis) - Static Site Generators (like Jekyll) ##`.mdoc`: **scope: relatively more complicated but more capable as a stand alone single document with embedded/linked stylesheet** - Stand alone resume - Invoice - Orders - Forms - email backup without attachments (or at least encoded in base 64) ## `.mdocz`: **scope: A full document container ( a website in a box ), capable of being displayed in many formats, e.g. pdf/html/mobile/etc…** - Portafolio - eBooks - Articles with images - Ezines - Instruction Manuals - Choose your adventure stories - documented codes - E.g. code documentations in research, where python snippets are stored in the /code/ folder - manpage - An email backup along with it’s attachments and metadata --- _[View the full topic](https://talk.commonmark.org/t/commonmark-document-specification-for-desktop-readers/956)._