Inspirational resources and prior art

[mstade]

It's important to consider prior art in this process, not just for inspiration but also in order to learn from the successes for failures of other formats. Let this issue be a collection of links and discussions for future reference.

[mstade]

Pandoc Markdown and ReST Compared

Easily digested and useful, albeit biased, commentary on Pandoc Markdown vs. ReST.

[mstade]

http://www.wilfred.me.uk/blog/2012/07/30/why-markdown-is-not-my-favourite-language/

[mstade]

http://hiltmon.com/blog/2012/02/20/the-markdown-mindset/

[mstade]

http://fountain.io/syntax

[mstade]

https://github.com/tlamadon/markdown2deckjs

[mstade]

http://bywordapp.com/markdown/guide.html

[mstade]

https://github.com/fletcher/MultiMarkdown/wiki/MultiMarkdown-Syntax-Guide

[mstade]

https://help.github.com/articles/github-flavored-markdown

[mstade]

Consider moving this to a file within the repo.

[mstade]

There's some good stuff in YAML that might be worth looking at for inspiration. It's a well written spec with a clear structure. Particularly, I think YAML's view on data structures (that all structures it wants to model can be modelled using maps, lists or scalars) overlaps with PHML. The obvious difference being that in addition to these primitives, PHML adds hypermedia, meaning PHML can actually describe much more complex structures.

There's some obvious overlaps in syntax (lists and maps certainly) and perhaps the rules in YAML can provide useful insight in to possible gotcha's with less strict syntax. As well, it can probably provide some inspiration for useful additional primitives (such as inline list syntax, as opposed to block lists.)

[mstade]

(Actually, looks like YAML does support some hypermedia constructs.)

[mstade]

Moved to wiki instead.