This doesn't prevent forks, of course, but anyone who wants to perpetuate the 'Markdown legacy' should consider this.
Leaving any sort of ambiguity in your spec inevitably leads to different implementations resolving those ambiguities in different ways, which confuses users and causes problems with interoperability.
Is there some sort of upside to these syntactic ambiguities that I'm missing which might offset those obvious drawbacks?
Oh, but there have. For instance, code fences are not part of the original markdown spec, but are commonly supported in just about every implementation out there, and are rendered in about [7 different ways][1] depending on which converter you're using.
Play around for a little in BabelMark and you'll see why a standard is needed.
[1]: http://johnmacfarlane.net/babelmark2/?normalize=1&text=%60%6...
If something like CommonMark had existed from the beginning, we wouldn't have this issue because everyone would be following the standard.
Example:
```javascript
// JavaScript code here
```
It's used extensively on GitHub.
Also the problem with his "original specification" is that there isn't one. There's a description that demonstrates the basic syntax and a buggy implementation in Perl that isn't being maintained.
Markdown text is therefore always written for use with a specific implementation, and can't realistically be used as a text interchange format in e.g. email or any other federated system with multiple rendering implementations.