Comment by smackfu

From the podcast linked below, my rough summary of his position: Essentially, that while a spec that cleared up some ambiguity might be useful and is a task he might undertake someday, calling one thing "true markdown" and other flavors not wouldn't be useful. If Github wants to have a version of markdown that supports code better than a blog engine needs, good for them.